Continuity is a local continuity layer. It keeps project identity, memory,
provenance and structured handoffs stable while agents and sessions change.
Git and your project files stay the source of truth.
The local Dashboard with a demo project. No hosted service, account or model key.
Why Continuity
You switch from Claude Code to Codex, start a fresh session, or hand work to
another agent. The agent changes. The project does not.
Without a shared layer, every new session rediscovers the same rules, repeats the
same decisions and loses what the last agent was halfway through. Continuity keeps
that state with the project, not with a chat:
Claude Code ──┐ ┌──▶ Codex
▼ │
┌────────────────────────────┴───┐
│ Continuity │
│ identity · memory · handoffs │
│ provenance · context audit │
└────────────────────────────────┘
▲ │
CLI / MCP ────┘ └──▶ the next session
| Continuity is | Continuity is not |
|---|
| Local project continuity across agents and sessions | Another coding agent or an IDE |
| Durable project memory with provenance and conflict quarantine | A chat archive or transcript store |
| Structured handoffs between agents | A replacement for Git |
| Project and workspace isolation | A cloud memory service |
| A CLI, MCP server and loopback API | A replacement for native Read, Grep or Git tools |
What it keeps
| |
|---|
| Project identity | A local ID bound to the canonical project directory, independent of display name, agent or session. |
| Workspaces | Git worktrees share one project identity but keep separate current sources. |
| Memory | Source-backed facts and attributed agent lessons, each with its origin and trust level. |
| Handoffs | Goal, completed and remaining work, decisions, risks, changed files and the next action. |
| Provenance | Source paths, SHA-256 versions and capture times behind every context item. |
| Context audit | Which sources and memories were selected for a context bundle, and why others were excluded. |
How it works
continuity init registers a project. continuity sync builds a bounded,
hashed index of its current text sources.- Agents connect through MCP, the CLI or the local API. The host fixes the
project, so an agent can read and write only that project's state.
- Agents propose memories and leave handoffs. Core policy decides what becomes
durable, at which trust level, and what is quarantined.
- Context requests return a byte-budgeted bundle with provenance and an
explanation. Changed or deleted sources can no longer support old claims.
Memory model
- Source-backed facts are checked against the current file and keep its path and hash.
- Attributed agent lessons activate automatically at a lower
agent_observation trust.
- Conflicts are quarantined instead of resolved by whichever write came last.
- Current sources outrank agent observations. Routine execution noise is rejected.
- Human review is optional: an explicit override, not a queue you must work through.
See the memory model. Automatic memory is included in
v0.2.0; explicit human review remains available.
Quickstart
Requirements: Node.js 24.13 or newer on the Node 24 line, and Git.
See stability boundaries and upgrade steps before replacing a local installation.
Continuity is not published to the npm registry. Do not install an unrelated
package named continuity.
Latest release (v0.2.0). Download continuity-local-0.2.0.tgz from the
release page, then:
npm install --global ./continuity-local-0.2.0.tgz
From source (for contributors). Requires pnpm 10.30.1:
git clone https://github.com/cubiix3/continuity.git
cd continuity
pnpm install --frozen-lockfile
pnpm check
pnpm link --global
If pnpm's global bin directory is not configured, run pnpm setup and open a new
terminal. Without linking, pnpm continuity --project <path> init works from the checkout.
Then, inside your project:
continuity init
continuity sync
continuity dashboard
Open http://127.0.0.1:4783. The browser does not open automatically.
On Windows, v0.2.0 can keep the Dashboard running and sync projects
automatically after sign-in: continuity startup install, then continuity runtime start
to start it now. It runs as the current user, without administrator rights. See the
background runtime for limits and removal.
Leave a handoff and pick it up in another agent's session:
continuity handoff create --file handoff.json
# later, from another agent in the same project:
continuity handoff latest
The runnable example covers memory and handoff inputs.
To give every new agent session this context automatically, install a provider
hook once: continuity integrate claude install or
continuity integrate codex install. See agent bootstrap.
In interactive Claude Code and Codex sessions, the same hooks ask the agent, after a
turn that edited files, whether anything is worth keeping or a handoff is finished; it
never reads chats. Scripted claude -p and codex exec answers stay unchanged. See
agent lifecycle.
This is the beginning of the README. Read the rest at the original. Read the full README ↗
