Coincide Get Coincide

Agent · Anysphere

Cursor logo

Cursor in Coincide

Coincide works with Cursor’s command-line agent, cursor-agent, rather than the Cursor editor. You sign in once with Cursor’s CLI, and your Cursor models, plan mode and usage limits show up next to your other agents in one Mac window.

How Coincide runs Cursor

Coincide starts cursor-agent acp, which speaks the Agent Client Protocol (ACP), an open protocol for connecting agents to apps. The Cursor CLI does the work and talks to Cursor’s service under your account; Coincide only shows the conversation, the tool calls and the changes, and answers Cursor’s requests for permission.

The Cursor editor isn’t needed and isn’t involved. If you use both, they share your Cursor account, and Coincide is careful not to change your CLI’s default model: when you pick a model in Coincide, it puts back the model settings in Cursor’s cli-config.json.

Set it up

  1. Install the Cursor CLI (see the official Cursor CLI page):
    curl https://cursor.com/install -fsS | bash
  2. Sign in:
    cursor-agent login
  3. Open Settings › Cursor and choose Check Again. Coincide checks cursor-agent status and shows your account. If cursor-agent lives outside your PATH, set a custom path there.
  4. Pick a Cursor model in the composer, or type /cursor to hand the current thread to Cursor.

Instead of signing in, you can set CURSOR_API_KEY. Cursor keeps its login in the macOS Keychain and allows only one, so additional Cursor accounts in Coincide use API keys, which Coincide stores in your Keychain. Agent accounts has the details.

Models

Coincide asks the Cursor CLI which models you can use (through Cursor’s ACP extension, or cursor-agent models). A Default entry uses whatever model your Cursor CLI is set to. Where Cursor offers them for a model, Coincide shows its thinking levels as reasoning effort and its context sizes as options. Cursor models don’t have a separate fast mode in Coincide.

What works with Cursor

In CoincideWith Cursor
Plan modeCursor’s own plan mode, switched over ACP, with Cursor’s plan captured in the thread.
Approvals and full accessAsk for approval shows Cursor’s own choices for each request, plus Cancel. Full access runs cursor-agent --force; switching between the two restarts Cursor’s process and reloads the chat.
QuestionsCursor’s questions are answered inline.
Follow-upsMessages sent while Cursor works are queued for the next turn; Cursor can’t take a message in the middle of a turn, so there’s no steering.
AttachmentsImages are sent to Cursor when it accepts them, and otherwise mentioned by path.
ResumingEach thread reloads its Cursor chat. If Cursor can’t load it, Coincide starts a new chat with a recap and says so.
StoppingStop cancels the turn and gives Cursor five seconds to finish.
Usage limitsYour monthly usage (overall, Cursor models and other models) and included and on-demand spend, read from Cursor. Off until you turn on Show account usage in Settings › Cursor, because it reads Cursor’s sign-in from your Keychain.

Cursor and your other agents

Because every agent in Coincide shares the thread, you can start a task with Cursor and continue it with Claude Code or Codex, or the other way round. The next agent gets a recap of the turns it missed. How switching works.

Limitations