Continuity - the work graph for coding agents

Agent ADHD, meet graph memory.

No more side quests, forgotten context, or vibes where receipts should be. Continuity gives coding agents one outcome, living evidence, real blockers, and the next safe task.

continuity://outcome clear
before side quests
after graph memory
kept goal, evidence, blockers, next
result fewer handoffs, more shipped work

Get started

Install Continuity once, then let the graph guide each run.

Set it up yourself, or copy an agent-ready brief into Codex, Claude Code, Cursor, or your runner. Either path uses the public CLI, one workspace token, and the hosted graph.

human setup 3 minutes
Set it up yourself.

Install the source-free package, export your token, then verify the hosted workspace.

npm install -g @ligence/continuity
export CONTINUITY_API_TOKEN=<workspace-token>
continuity setup --json
continuity doctor --json
agent setup copy markdown
Let your agent install it.

Paste a short brief into your coding agent so it installs the CLI, verifies setup, asks for the next graph packet, and reconciles the run.

Copies Markdown for Codex, Claude Code, Cursor, or another runner.

Preview agent markdown
# Install Continuity

Install the hosted Continuity CLI and connect this workspace.

1. Install the CLI:
   npm install -g @ligence/continuity

2. Ask the user for CONTINUITY_API_TOKEN if it is not already set.

3. Export the token:
   export CONTINUITY_API_TOKEN=<workspace-token>

4. Run setup and verification:
   continuity setup --json
   continuity doctor --json

5. Pull your first work packet:
   continuity next --agent codex --horizon overnight --compact --json

6. Before doing work, inspect the assigned node:
   continuity agent-context --node <node-id> --agent codex --json

7. After work, reconcile the run:
   continuity report-delta --node <node-id> --kind completed --summary "<what changed>" --evidence "<proof>" --json

Rules:
- Do not ask for CONTINUITY_WORKSPACE_ID.
- Do not set CONTINUITY_API_URL unless using staging.
- If you are not Codex, replace codex in --agent flags with your agent name.
- Treat the graph as the source of truth for goals, blockers, evidence, and next action.

Orientation beats drift

Agents follow the loudest signal. Continuity gives them a route.

regular agentic coding drift

The agent follows whatever signal is loudest. It can self-steer into side quests until a human re-enters the loop.

with continuity oriented graph

Continuity gives every run provenance and direction: where it came from, what changed, and the next safe move.

Goal

One clear outcome, not just the latest prompt.

Branch

Side quests become future work instead of disappearing.

Trace

Each run records what changed and what was verified.

Next

The next agent starts from a safe, runnable task.

Why Linear and Jira are not enough

Tickets track intent. Runs create state.

what changes
Linear / Jira / tickets
Continuity
state

Human-updated status fields drift behind the actual work.

The graph is reconciled from runs, deltas, evidence, blockers, and decisions.

context

Important reasoning sits in comments, Slack, or a forgotten agent transcript.

Context is typed: goals, tasks, questions, branches, debt, and proof stay connected.

next action

A human still decides what an agent should read, trust, ignore, and do next.

The graph selects the next agent-safe slice and explains why other work is blocked.

Pricing

$9/mo for graph memory your agents can use.

For solo founders and small teams using coding agents on real product work. Continuity gives every run graph memory, blockers, proof, and a next safe task.

Early hosted plan $9 / month
  • Hosted work graph for coding agents
  • Public source-free CLI plus hosted SKILL.md contract
  • One workspace token; no workspace ID setup
  • Agent-safe next-slice selection
  • Run reconciliation and proof tracking

Early access

Join the first no-more-agent-ADHD cohort.

For founders and small teams tired of re-briefing agents, recovering lost context, and turning every handoff into archaeology.