Skip to Content
Introduction

Introduction

Your AI agent stopped. The next one picks up exactly where it left off.

PCS (Project Continuity System) is a local-first command line tool and MCP server that hands work from one AI coding agent to the next. When an agent hits a token limit, you start a new chat, or you switch from Claude to Cursor, PCS rebuilds what actually happened in the project from git and recorded evidence, and gives the next agent a brief it can trust.

Never trust an agent’s “done”. PCS keeps what it saw itself apart from what an agent claimed.

Why PCS

Agents lose context when a session ends. The usual fix is a summary written by the agent that just ran out of room, which is exactly the part you cannot trust: it may say tests pass when they never ran, or forget the file it was halfway through editing.

PCS records facts with their source, so the next agent knows which lines are solid:

LevelMeaningExample
verifiedPCS observed it itselfgit state, file hashes, a test run PCS executed with its exit code
reportedA person or agent claimed it“task done”, “next step is X”
inferredDerived from other facts“the session was interrupted”

A task counts as verified only when a passing test run that PCS executed is linked to it, and only while the code still matches the state that run saw.

What you get

  • Handoffs you can trust. Original task, completed work (verified, passing-but-code-changed, or reported only), work in progress, files touched, test results with the output of failing runs, open problems, next steps and do-not-touch notes.
  • Tamper-evident history. Events are stored in an append-only SHA-256 hash chain. pcs verify detects edits, deletions and reordering. A signed anchor kept outside the project also detects truncation and rewrites.
  • Audit export. pcs export writes the log as JSON or Markdown that can be checked without PCS.
  • Secrets stay out. Redaction runs before anything is stored. Files flagged sensitive (keys, .env) are listed by name and never read.
  • Works with your agents. An MCP server for any MCP client, Claude Code hooks, and instruction blocks for CLAUDE.md, AGENTS.md and Cursor rules.
  • Always on, if you want. A background watcher snapshots the repo as files change and flags stalled sessions.
  • Many repos. pcs workspace lists all your projects; each keeps its own log.
  • Read-only dashboard. pcs dashboard shows sessions, tasks with their evidence, notes, test runs and the event timeline on 127.0.0.1.

PCS is local only: no network access and no telemetry. Data lives in .pcs/ inside your project.

Where to go next

Last updated on