Security model.
Security boundaries for OAuth credentials, memory access, and auditability in production integrations.
Credential handling
Store client secrets and refresh tokens in dedicated secret stores, never source control. Prefer short-lived access tokens and rotate long-lived credentials when ownership changes.
Authorization: Bearer <short-lived-access-token>Authorization
Enforce scoped OAuth permissions and reject malformed or expired bearer tokens. Workspace selection scopes memory, but it does not grant a user access they do not already have.
Audit posture
Log memory read/write/delete events without logging token values or private memory contents. Retain operational traces for incident response and review high-impact writes.
Common mistake: An API key in a shell history, CI log, or committed config is a credential leak—not a safe fallback.
Last updated: May 21, 2026