Coincide Get Coincide

Agent · xAI

Grok logo

Grok Build in Coincide

Coincide runs xAI’s grok command-line agent over the Agent Client Protocol, signed in with your Grok account or an xAI API key, and keeps its threads, plans and changes next to your other agents.

How Coincide runs Grok Build

Coincide starts grok agent stdio and talks to it over the Agent Client Protocol (ACP). In approval mode it adds --permission-mode default; with full access it adds --always-approve. Grok Build does the work and talks to xAI under your account. Coincide finds grok on your shell’s PATH, in ~/.grok/bin and in the usual install folders, or at a custom path you set in Settings › Grok Build.

Set it up

  1. Install Grok Build by following xAI’s instructions on the Grok CLI page.
  2. Sign in:
    grok login
  3. Open Settings › Grok Build and choose Check Again. Coincide runs grok --version and grok models to see whether you’re signed in, and shows your account’s email from ~/.grok/auth.json.
  4. Pick a Grok model in the composer, or type /grok to continue the current thread with Grok Build.

You can also use an xAI API key (XAI_API_KEY), and add more Grok login accounts: each gets its own GROK_HOME folder and its own grok login. See Agent accounts.

Models and reasoning effort

Coincide reads your models from grok models, with names, reasoning efforts and context windows from Grok’s own model cache, and puts a Grok Build default entry first. Once a session is running, Grok reports the efforts each model supports, and Coincide applies your choice of model and effort over ACP. There’s no separate fast mode for Grok models.

What works with Grok Build

In CoincideWith Grok Build
Plan modeGrok has no plan mode over ACP, so Coincide asks for a plan in the prompt instead. When Grok finishes planning, its plan is captured in the thread.
ApprovalsFor each request you can Approve, Allow all edits this session, Decline or Cancel. Reading and searching files is always allowed.
Full accessRuns Grok with --always-approve. Switching between approvals and full access restarts Grok’s process.
QuestionsGrok’s questions are answered inline.
Follow-upsQueued until the current turn ends; Grok can’t be steered in the middle of a turn.
AttachmentsPNG, JPEG, GIF and WebP images up to 10 MB are sent to Grok.
StoppingStop ends Grok’s process; the next turn reopens the same session.
ResumingEach thread reloads its own Grok session.
Usage limitsYour Grok subscription’s weekly or monthly credit window, read from xAI with your Grok sign-in. Not shown for API keys.

Grok Build and your other agents

Hand a thread to Grok Build with /grok and it gets a recap of what the other agents did, in the same folder. Hand it back and the earlier agent resumes its own session. This works the same way for every agent; see switching agents mid-thread.

Limitations