Sign-in
Before a provider can run tools, the adapter may need you to sign in. Appenda shows that step inside the chat, not buried in Settings.
When the adapter needs identity, the chat shows Sign in with your provider brand.
Interactive provider login
When authRequired is true, the chat shows Sign in with your provider
(Claude Code, Codex, or Cursor). Appenda prefers browser or subscription login
flows advertised by the adapter.
API-key style methods stay in Settings. They do not appear as the primary composer call to action.
Appenda entitlement
Agents also require a signed-in Appenda account with paid or trial agent access.
| Gate | What you see |
|---|---|
| Sign-in required | Sign in to Appenda first |
| Upgrade required | Plan does not include agents |
The composer stays disabled until both Appenda entitlement and provider sign-in (when needed) are satisfied.
Settings → Agents
The Agents settings page shows connection status per provider and lets admins manage allowed providers, pending approval requests, and saved grants.
Use it to verify which runtimes are connected, not to replace the in-chat sign-in flow.