Credentials & OAuth
Credential model
Section titled “Credential model”Junior does not preload provider access for an entire chat session. Registered plugin providers are available to sandbox commands, and sandbox HTTP requests to declared provider domains are forwarded through Junior. Junior then fetches a requester-bound lease and injects auth at the host boundary.
- Credentials are short-lived and scoped to the requester, registered provider, and current sandbox command.
- User-owned provider access is only activated for the author of the current message.
- Plugin declarations determine which credentials can be injected for matching provider domains.
- Sandbox receives placeholder env vars and proxied HTTP responses, not raw long-lived tokens.
- Credential issuance is lazy: Junior does not mint provider tokens until sandbox traffic actually reaches a declared provider domain, avoiding wasted token work for commands that never need auth.
- Junior does not guess intent from command text to pre-scope or pre-mint credentials; request-time provider/domain matching is the boundary.
- Junior rejects proxied provider requests unless the sandbox has a signed requester context for that VM session and the forwarded host matches a registered provider domain.
OAuth model
Section titled “OAuth model”OAuth-based plugins keep the visible user flow simple while preserving per-user authorization boundaries.
- Auth links are delivered privately to the requesting user.
- Token exchange occurs server-side and stores the grant per user and provider.
- OAuth completion resumes the blocked request path instead of asking the user to rerun the whole workflow.
Operational invariants
Section titled “Operational invariants”- Normal plugin workflows rely on automatic credential injection, not manual credential commands.
- Never log raw token values.
- Never place secrets in skill files.
- Credential failures must surface clear operator-visible errors.
Common failure classes
Section titled “Common failure classes”credential_unavailablewith OAuth required.- stale/insufficient provider token access (401/403 post-issuance).
- provider misconfiguration (client ID/secret/redirect URL mismatch).