Feature Request: Team, agent, and memory-level access control
Observed in vectorize-io/hindsight · Python · MIT
What the reporter described: Summary I would like to request a discussion around a more detailed permission and sharing model for the open-source Hindsight server. The current OSS authorization model seems intentionally simple: : one shared API key mapped to the configured schema. : one Supabase user JWT mapped to a schema derived from that…
Related friction appears in 4 independent repositories. This is stronger than one backlog item, but still requires direct user validation.