Adding memory to Continue
no hook fires yet, so recall is a tool it reaches for — and is told about
Continue writes every session to ~/.continue/sessions — one JSON document each, in VS Code, JetBrains and the cn CLI alike. A new session reads none of them, and none of the sessions the other agents on this machine wrote either, including the one where the problem was already solved.
Adding recall
deja install continue
Three things, in the two places Continue reads:
- The MCP server, as an item under
mcpServers:in~/.continue/config.yaml. Continue keys that list bynamerather than by a key, so deja's entry is found again by its own name, and everything else in the file is left where it was. The CLI's header lists it underMCP Servers. - The
deja-historyskill in~/.continue/skills. Continue names every skill it finds in theSkillstool's own description, so the reason to look at history is in front of the model on every turn rather than only when someone asks. - A
/dejacommand, as aprompts:entry in the same config.
Why there is no session-start injection yet
Continue's CLI carries a hooks system shaped exactly like Claude Code's — the same event names, the same additionalContext, settings read from ~/.continue/settings.json — and in the published release nothing fires it. Measured on @continuedev/cli 1.5.47 against a recording endpoint: hooks written for every event were loaded (its own log says Hooks loaded: 8 handler(s) across 8 event type(s)) and not one handler ran, while the same run's tool call went through. The day a release fires them, deja's Claude-shaped wiring works here unchanged.
What it costs
From the recorded requests on that version: deja's tool schema is 3,112 bytes of the 10 KB of tools Continue sends with every request, the skill adds 700 bytes to the Skills tool's description, and a recall that answers adds 1,384 bytes to the turn that asked for it. A recall with no answer adds nothing.
The part that is not about this harness
The index covers every agent's transcripts on the machine — twenty-five of them, each in its own format — so a fix found in Claude Code answers a question asked in Continue, including sessions from before any of this was installed. Nothing here writes memories, so there is nothing to hallucinate into your history; indexing and search are local, and credentials are stripped as the index is built (privacy).
Getting started · Switching between agents · The Continue session format