Works with / Coding subscriptions

Use your coding subscription

Run a Bot on the coding CLI of a plan you already pay for, signed in with your own account.

All of these are Experimental. They haven't passed a live check with a real sign-in yet.

Which plans

  • GitHub Copilot, through its CLI.
  • Cursor, through its CLI.
  • Kimi Code, through its CLI.
  • Mistral Vibe, through its CLI.

Synapse talks to each CLI over the Agent Client Protocol, an open protocol for coding agents.

Not supported: signing in with a Claude subscription, or with a Google account for the Gemini CLI or Antigravity. For Claude, use an Anthropic API key. For Gemini, use a Gemini API key.

What works

  • Chat, replies and the CLI's own coding tools.
  • Every file read, file change and command the CLI wants goes through Synapse's safety gate first, one at a time. Synapse never tells a CLI to "always allow".
  • Files and commands run as the Bot, inside its own walls on the Bots' computer. Each Bot runs as its own account there, which new installs have from the start.
  • Coding agents, as Experimental. The same CLI works in the agent's own branch and folder, and every action it asks for goes through the same gate.

Not yet

  • Choosing the vendor's model. The CLI uses its own default.
  • Web search, images, voice calls and subagents on these Bots.
  • Actions the CLI asks for in a shape Synapse doesn't know yet. They are refused, not guessed.

Cost

Included in your plan. Synapse records these turns at $0, and they don't count against your spend budget. Your plan's own limits apply.

Privacy

  • Consent first. Nothing goes to a vendor until you allow it once. The consent says what is sent: the conversation, the files the Bot reads and the results of the commands it runs. The vendor's own terms apply.
  • Your sign-in stays with the Bot. The CLI keeps its login in the Bot's own home on the Bots' computer. Synapse never reads or stores it, and refuses any request that reaches into the CLI's login folder.
  • Only the vendor's own sign-in page. When you sign in, Synapse shows a link only if it is on the vendor's own site.
  • The same safety gate. Every action goes through Synapse's fixed rules and approvals, whatever the CLI. The safety reviewer runs on Claude when you've saved an Anthropic key, and otherwise on the provider you set up. You can pick another model for it in Settings → Rules → Safety reviewer. A reviewer on a model other than Claude asks you first until it passes the safety check.

Set up

  1. In Synapse, open Settings → Account → Coding CLIs. Click Allow next to your plan, read what it sends, and allow it.
  2. Click Install. Synapse installs a fixed version of the vendor's official npm package on the Bots' computer, and checks every file against the checksum npm publishes for it. GitHub Copilot and Kimi Code can be installed this way. Cursor and Mistral Vibe don't publish one, so they can't be installed from Synapse yet.
  3. Open a Bot's settings and pick the CLI as its model.
  4. Click Sign in with your plan, open the link, and enter the code if one is shown. For Mistral Vibe, run vibe --setup in the Bot's terminal instead.
  5. Send the Bot a message.