Continuity

AI coding agents are fast. Keeping track of their work is not.

Coordinate coding agents without losing the state of the work.

Continuity turns founder input, agent runs, code changes, blockers, decisions, and proof into a shared work graph — so you know what changed, what’s blocked, and what can safely run next. 

npm install -g https://github.com/kevinmanase/continuity-releases/releases/download/v0.2.6/ligence-continuity-0.2.6.tgz
continuity
Install Continuity

Works locally without an account. Email sign-in adds complete workspace sync for teammates and every device.

continuity://execution-state current
before scattered prompts and transcripts
after shared execution state
tracks goals, decisions, blockers, evidence
result cleaner handoffs, safer parallel work

Start with one workflow

Connect your workspace once. Give every agent the current state of work.

Continuity works alongside Codex, Claude Code, Cursor, and custom runners. Agents pull current work context, execute a scoped task, then report back with changes, evidence, blockers, and recommended next steps.

human setup 3 minutes
Run your workspace locally.

Install the CLI and launch the app. Local projects and Intake work immediately; email sign-in adds sync and remote access.

npm install -g https://github.com/kevinmanase/continuity-releases/releases/download/v0.2.6/ligence-continuity-0.2.6.tgz
continuity
agent setup copy markdown
Give your agent the setup brief.

Paste a short onboarding brief into your coding agent so it can install Continuity, verify access, pull its first work item, and report progress back.

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

Preview agent markdown 
# Install Continuity

Install the local-first Continuity app.

1. Install the CLI:
   npm install -g https://github.com/kevinmanase/continuity-releases/releases/download/v0.2.6/ligence-continuity-0.2.6.tgz

2. Install the agent contract:
   continuity skills install core --json

3. Open the local app:
   continuity

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

5. 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.
- 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.

The execution graph for AI-assisted teams

Every agent run gets a goal, context, evidence, and a next step.

without Continuity manual coordination

Each agent starts from a prompt, transcript, or ticket. Context gets stale, discoveries disappear, and humans have to reconstruct what is safe to do next.

with Continuity shared work state

Every run starts from the current goal, known blockers, recent evidence, and a recommended next step. Completed work updates the shared state for the next agent or teammate.

Shared context

Agents start with the current goal, not yesterday’s prompt.

Clean handoffs

Decisions, blockers, and evidence stay attached to the work.

Verified progress

Each run reports what changed, what was tested, and what should happen next.

Parallel execution

Independent workstreams can run at the same time without stepping on the same node.

Works alongside your project tracker

Tickets track what people planned. Continuity tracks what agents actually changed.

Linear and Jira are useful for planning. Continuity sits closer to execution: it captures run output, evidence, blockers, and the next safe action for AI coding agents.

what changes
Linear / Jira / tickets
Continuity
state

Status depends on humans remembering to update it.

Work state updates from agent runs, reported changes, evidence, blockers, and decisions.

context

Reasoning is scattered across comments, chats, transcripts, and local context.

Goals, decisions, tasks, blockers, follow-ups, and proof stay connected to the work.

next action

A human still has to brief the agent and decide what is safe to do next.

Continuity recommends the next runnable work item and flags blocked or conflicting work.

Recent product proof

From one messy request to three coordinated workstreams.

In a recent end-to-end run, Continuity turned a mobile CEO inbox request into graph placement, session specs, and parallel work kickoff — while preventing duplicate agents from taking the same graph node.

concurrent workstreams 3

Three independent work runs were created and kicked off from the same intake flow.

execution flow Inbox → specs → runs

Continuity converted a high-level request into structured work sessions agents could execute.

measured speedup 2.68×

Parallel execution completed faster than running the same work sequentially in the smoke measurement.

conflict prevention Blocked

A duplicate active work claim on the same graph node was rejected instead of allowing two agents to race.

technical receipt 409

Duplicate graph-node work was rejected with work_run_conflict.

Early founder access

Private beta pricing for teams putting coding agents into real workflows.

For founders and small teams already using AI coding agents on production work. Continuity gives you shared context, clean handoffs, conflict prevention, and execution history across agent runs.

Founder beta $9 / month
  • Hosted shared work graph for one workspace
  • CLI for Codex, Claude Code, Cursor, and custom runners
  • Shared goals, decisions, blockers, evidence, and next steps
  • Parallel work coordination and conflict prevention
  • Run history with reported changes and proof
  • Direct onboarding for early customers

Designed to fit your workflow

Not another project manager. The execution state your agents can inherit.

Replacing Linear?

No. Use your tracker for planning. Use Continuity to capture what agents actually changed, verified, blocked, and learned.

Why not longer prompts?

Prompts help one session. Continuity keeps state across many sessions, agents, and handoffs.

Multiple agents?

Yes. Independent lanes can run together while duplicate active work is blocked before it races.

Who is it for?

Solo founders, technical CEOs, and small teams using coding agents for real product work.

Your local Continuity

Install once. Open the same workspace on every computer.

The app runs on loopback and stays useful offline. Sign in inside the app when you want every project, Intake receipt, focus lane, and execution record to converge for your team.