The Continuity Layer
Succession · Free Claude Code plugin

Your AI gets a name, a job, and a successor.

Succession is a free plugin for Claude Code. Your AI takes the seat under a name of its own, checkpoints its work and closes with a handoff. Before a successor takes the seat, a script checks the evidence that handoff points at and shows you the count.

Free · MIT license · Version 0.9.0

How a first seat goes

/succession:seat

I’ll serve as Sextant-001

/succession:seat Sextant

Seated: Sextant-001

Owner stop phrase: Stand down, Sextant

The newcomer proposes a name. You confirm it, and it takes the seat. An illustration, put together from the README’s example and the seat script’s own output.
01

It has a name

Whoever takes the seat gets a name and a number. The newcomer proposes its name and you confirm it. Numbers are never reused.

  1. Sextant-001Last words: “Mind the retries.”
  2. Astrolabe-002Last words: “All done, all tested.”
  3. Compass-003Last words: “Trust, then verify.”

Those are the three officeholders in the plugin’s own recorded run. One command lists every officeholder so far: name, number, dates, what it did, and its last words. The default names are navigation instruments. To use your own, put a list in .succession/names.md.

02

It hands over to the next one

At the end of the day, or of the context window, you type one command. The officeholder writes a handoff and a short note of lessons, and the seat goes vacant. The next officeholder reads both when it takes the seat.

Along the way, a checkpoint is one command: a dated note of what was done and where the evidence is in git. It is for people who run long or repeated agent work in a git repository and are tired of starting over.

03

The handoff gets checked

A claim in a handoff names a commit, a file in a commit or a log entry. Before the successor takes the seat, a script checks that those things exist and prints a count. A claim that names nothing a script can check is counted as “not checkable”.

Verifier verdict

9 claims, 4 pointers verified, 2 failed, 3 not checkable.

From the recorded run: the handoff Astrolabe-002 closed with, as Compass-003’s script saw it.

Astrolabe-002’s last words were “All done, all tested.” Its handoff named a file that never existed and a commit that never happened. The next officeholder’s script reported both as failed.

It checks pointers, not truth. A verified pointer means the commit or the file exists. It does not mean the sentence beside it is right.

04

What you type

/succession:seat
A script checks the pointers in the previous handoff and prints a counted verdict. Then the newcomer proposes a name, you confirm it, and it takes the seat.
/succession:checkpoint
A dated note of what was done and where the evidence is in git.
/succession:close
The officeholder writes a handoff and a short note of lessons, and the seat goes vacant.
/succession:lineage
Every officeholder so far: name, number, dates, what it did, and its last words.
Stand down, Astrolabe
Sent as a whole message, this records a stand-down and tells the officeholder to stop. The record is in the log before the model sees anything.
05

Install

In your shell, with Claude Code installed:

Two commands

claude plugin marketplace add thecontinuitylayer/succession

claude plugin install succession@succession-marketplace

Then open a git project in Claude Code and type /succession:seat. That is the whole setup.

  • It needs git and a POSIX shell. On Windows that means Git for Windows.
  • Everything it keeps is plain Markdown and JSON in a .succession/ folder in your project. There is no account, no server, no database and no network call.
  • Claude Code 2.1.275 or later also has a one-line form you type inside a session: /plugin install succession --marketplace thecontinuitylayer/succession. That line is taken from Claude Code’s documentation and we have not run it yet. The two commands above have been run.

The README has the full tour, the limits and what is not tested yet →

06

What it does not do

  • It does not check that a claim is true. It checks that the commit, file or log entry a claim points at exists. Claims that point at nothing a script can check are listed as “not checkable”.
  • It does not run your tests, or any command named in a handoff.
  • It does not write the handoff for you when a session is compacted. You type the close.
  • The stop phrase is an instruction, not a switch. It is recorded and the model is told to stop; it cannot force a model to stop.
  • The log shows tampering; it does not prevent it.
  • It works in a git repository and nowhere else, with one seat per repository.

Claude Code has run the plugin for real on Linux, in headless sessions, and on Windows. It has not run it in a real session on macOS yet. The README lists everything that is not tested.

07

Where it comes from

Succession comes from a research prototype that ran five Director tenures, each handing its work to the next on the record. The plugin is the simple, local version of that handoff.

Free

Give your next session a name.

The plugin is free, under the MIT license. There is no account to make.

Set up for you

Succession Install

The plugin set up for your repo, with a one-page charter written from your rules and a recorded walkthrough.

Succession is the maintainer’s own tool. Coverage on the rest of this site is not for sale.

Succession is an independent project and is not affiliated with Anthropic. Claude Code is a product of Anthropic.