Agent credential issues

Use this page when Claude Code, Codex, Cursor, OpenCode, or another agent can't authenticate, won't launch, or shows as needing setup.

Each agent reaches models through its own CLI login, one of your API keys, or the Proliferate gateway. Pick the method per agent in Settings → Agents → [agent] → Authentication.

Check:

• The agent works outside Proliferate first. If claude, codex, or the CLI you're using can't log in on its own, Proliferate can't fix that for you.
• The selected Method matches what you intend. Choosing Proliferate gateway routes the agent through Proliferate-managed model access; choosing API key uses the key bound below that card; CLI login uses the agent's native credentials on your machine. Claude, Codex, and Grok use one method at a time. OpenCode combines its native provider logins with any keys you add in its Providers section.
• The credential is scoped correctly. Personal credentials are yours alone. A teammate who shares a credential with your organization has to do that explicitly; you can't use someone else's login just because you're in the same org.
• The agent shows as ready, not "needs setup." Settings surfaces agents that still need attention in one place, with the specific missing piece (login, API key, or gateway access) called out per agent.

Cloud workspaces are coming soon, so there is no current Cloud credential troubleshooting flow. If GitHub access (cloning, PRs, pushing) is failing, that's covered separately in Git and PR issues.

For the full model behind gateway routing, BYOK, and OAuth, see agents/authentication.