← All work

Continuity

Python

Every new coding-agent session starts with no memory of the last one, so the same decisions, constraints and open tasks get re-explained. Continuity keeps that memory as plain Markdown in a .continuity/ folder inside the project, hands each new session a short summary of it, and has the agent save new notes as it works. It runs as a plugin in Claude Code, Codex (beta) and Cursor.

PythonClaude CodeCodexCursorMarkdownApache-2.0
At a glance
  • Works in Claude Code, Codex (beta) and Cursor, from one GitHub marketplace.
  • Recall at session start, capped at 200 lines or 10 KB, active tasks first.
  • Writes in a detached process, never through an LLM call, and fails open.
  • Plain Markdown store committed with the repo, so teammates share the memory.
  • Python standard library only: no server, database, network call or pip install.

Problem

A coding agent forgets everything when a session ends. The next session starts cold, so the developer re-explains the same decisions, constraints and open tasks, and the agent re-discovers what the last one already learned. Memory services exist, but they add a server, a database or a cloud account to what should be a local tool, and they keep the project's memory somewhere other than the project.

Approach

Keep memory where the code is, in a format a person can read and review. Continuity stores it as plain Markdown in .continuity/ and commits it with the repository by default, so a teammate's session inherits the same context. The agent decides what is worth keeping and stages a short note; Continuity never composes memory with a model, it only consolidates what was staged. Two rules govern everything else: never block the agent, and never break its session.

Solution

Hooks fire at session start, after real edits and commits, at the end of a turn, at session end and on a manual checkpoint. An adapter detects which agent is calling and converts its event into one common shape, so the rest of the plugin is shared across Claude Code, Codex and Cursor. At session start a recall builder returns a bounded, labelled summary with active tasks first. After real changes a detached background writer takes a store lock, secret-scans each note, writes atomically, records a session handoff and prunes old ones. If a turn changed files and saved no note, the agent is asked once to save one. Every failure is skipped and logged to errors.log.

Impact

Continuity gives coding agents a working memory that lives in the repository, is readable in a pull request and travels with the code. A new session picks up the project's decisions, tasks and learnings without a re-briefing, across three agents, with nothing to install or run beyond the plugin itself.