Continue

Continue uses Comity through an MCP server block and a project rule. Continue doesn't document agent hooks, so nothing is automatic: no briefings, no recorded edits and no blocks. See What works without hooks.

Set up

cd your-repo
comity init --tools continue
git add .continue/mcpServers/comity.yaml .continue/rules/comity.md
git commit -m "Set up Comity for Continue"

Then reload the window. No token is written anywhere: the server runs the stdio bridge, so comity login is enough.

What init writes

.continue/mcpServers/comity.yaml

name: Comity
version: 0.0.1
schema: v1
mcpServers:
  - name: comity
    type: stdio
    command: "node"
    args:
      - "-e"
      - "const c=require('child_process').spawn('comity '+process.argv.slice(1).join(' '),{stdio:'inherit',shell:true});c.on('error',()=>process.exit(1));c.on('exit',(k)=>process.exit(k===null?1:k))"
      - "mcp"

See Continue MCP. The node -e launcher runs comity mcp through the shell, so the file is the same on every OS and for every teammate. Node must be on PATH, which the CLI needs anyway.

.continue/rules/comity.md

An alwaysApply: true rule with Comity's coordination instructions.

Verify

comity doctor

Expect continue mcp .continue/mcpServers/comity.yaml and continue rule .continue/rules/comity.md. In Continue, switch to Agent mode (MCP tools only run there) and check that the comity tools are listed.

Limits

• No hooks: no automatic briefings, conflict warnings or blocks, and the agent's edits aren't recorded.
• MCP tools are only available in Agent mode.
• The continuedev/continue repository is now read-only, so expect no new Continue features.