Continue

One-line config

Continue isn’t auto-detected by setup, but it’s a spec-compliant MCP client — so it’s one config block away.

Config

sigil register --print

Add the inner sigil object to ~/.continue/config.json:

~/.continue/config.json

{
  "mcpServers": {
    "sigil": {
      "command": "/Users/you/.sigil/bin/sigil-mcp",
      "args": []
    }
  }
}

Use the path register --print outputs — it points at the stable shim in ~/.sigil/bin/, which is what keeps the integration working across Node version switches and reinstalls.

Restart Continue. The thirteen Sigil tools appear in its tool list.

Make it get used

Add to Continue’s system message:

You have access to Sigil, a persistent memory shared across every AI agent
on this machine. Call `prime` at the start of a session. Before answering
about this project, past decisions, or the user's preferences, call `search`.
When the user shares a preference, decision, or constraint, call `remember`.

Without something like this, the tools are available but idle.

Verify

sigil doctor --deep     # round-trips the MCP server
sigil status            # confirms the brain has content

Then ask Continue something it could only know from memory:

What did we decide about event delivery?

Troubleshooting

Tools don’t appear. Restart Continue — it reads config.json at startup. Check the JSON is valid.

The server errors on launch. The shim path is stale:

sigil connect

Tools appear but are never called. Strengthen the system message. This is the common case, and it’s a prompting problem rather than an integration one.