Coincide Get Coincide

Guide

Agent accounts and API keys

Each agent in Coincide starts with one account: its command-line tool’s own sign-in, exactly as you set it up in Terminal. You can add more, such as a second subscription login or an API key, and choose which one each thread uses.

Updated

The default account

Coincide runs each agent’s own tool with your login shell’s environment, so the default account is whatever that tool is signed in to: your Claude subscription in ~/.claude, your ChatGPT login in ~/.codex, and so on. If your shell exports an API key the tool reads, such as ANTHROPIC_API_KEY, the default account uses it the way the tool would in Terminal. Nothing about it changes when you add other accounts. For signing in to each agent the first time, see the agent pages.

Adding an account

  1. Open Settings and choose the agent under Providers in the sidebar.
  2. In Accounts, add an account, name it, and pick how it signs in: a login or an API key.
  3. For a login, Coincide opens a terminal that runs that agent’s sign-in for this account only, in a folder of its own. For an API key, paste the key; Coincide saves it in the Keychain and can check it (“Key not accepted” means the service refused it).

When an agent has more than one account, the model picker shows an Account row under the agent’s tab, and the thread uses the account you pick. Removing an account deletes its key and sign-in from this Mac; threads that used it continue with the agent’s default account.

What each agent supports

AgentAdded loginsAPI keys
Claude CodeYes: each gets its own CLAUDE_CONFIG_DIR and signs in with claude auth loginAnthropic API key, passed as ANTHROPIC_API_KEY
CodexYes: each gets its own CODEX_HOME and signs in with codex loginOpenAI API key, stored in that account’s own CODEX_HOME with codex login --with-api-key
CursorNo: Cursor keeps one login, in the macOS KeychainCursor API key, passed as CURSOR_API_KEY
Grok BuildYes: each gets its own GROK_HOME and signs in with grok loginxAI API key, passed as XAI_API_KEY
OpenCodeYes: each gets its own XDG_DATA_HOME and signs in with opencode auth login --standaloneA key for OpenCode Zen (OPENCODE_API_KEY), Anthropic, OpenAI, OpenRouter, Google Gemini, xAI, Groq, DeepSeek or Mistral, each in that service’s own variable, in a folder of its own
AntigravityNo: the Google sign-in belongs to Coincide’s one managed Antigravity profileGemini API key (GEMINI_API_KEY), in a profile of its own

An added account’s folder is providers/agent/account ID/ inside Coincide’s data folder, so two logins of one agent never overwrite each other.

Antigravity and Google accounts. Google’s Antigravity terms treat using the service through third-party software as a breach, and Google has suspended accounts for it. Coincide shows this notice and asks you to acknowledge it once. Gemini API keys from Google AI Studio or Gemini Enterprise aren’t affected. Details on the Antigravity page.

Where keys are kept

Usage and Admin keys

Settings › Usage shows plan limits per account where the provider reports them; most providers report no plan limits for API keys. An Anthropic API-key account can also take an optional Admin API key, which gives read-only access to your organization’s usage and cost reports. It’s kept in the Keychain beside the account’s key and sent only to Anthropic. See Usage dashboard.

Other settings per agent

Each agent’s page in Settings also has Environment Variables, added to the agent’s environment on top of your login shell’s, for example a custom base URL, and a Custom path for its executable. These apply to every account of that agent.