session orchestratorv5.20.0

ENDE

Install

Your AI agent, with a plan and a memory.

Your coding tool writes the code: Claude Code, Codex, Cursor or Pi. This free plugin keeps the work in order.

Install the plugin

You type three commands along one line. /session: you say what you want, and the plan is only a dashed line. /go: nothing is built before your yes; from there the line is solid. It works in rounds, three for a feature, checked with your tests. /close: it notes what is done for next time.

/sessionSay what
you want.

/goNothing is built
before your yes.

Real run, shortenedReady to execute? Use /go to begin …

Rounds, checked with your tests.

/closeNoted for
next time.

Between your yes and done.

Each loop is one round: agents build, your tests run along the way. /close runs the full check.

Tidy up/session housekeeping

One round, done directly.

Start here

Build one thing/session feature

Three rounds.

Round 2 of the real run, and the loop back The weakness is in the tests: two of the 4 new tests do not catch real breakages, … Fix pass: done. Three tests were added, … Tests: 10 passed, 0 failed …

Something big/session deep

Four rounds, or five if it first looks around, changing nothing.

Real lines from one run on a demo project, shortened. Claude Code, plugin 5.19.0, 13 Nov 2026.

All commands

Next time picks up the thread.

Its memory is plain text in your project: what's done, what's next, and the rules you said yes to. /close leaves the thread where your next /session picks it up.

The last lines of /close

Next session
Recommended mode is feature. The natural next step is
the date filter from ISSUES.md,
together with empty cells for missing fields in the export.

ISSUES.mdafter the run

1# Backlog
2
3- Date filter for the order list (from/to)
7## Done
8
9- CSV export of orders …

A lesson becomes a rule only with your yes.In this run, no lesson came up.

  1. /evolve suggests a lesson
  2. you keep, correct or reject it
  3. /reconcile writes the rule

Same run, shortened. The date filter was on the list before; the run moved the CSV export to Done.

In the tool you already use.

The same three steps in every tool; in Codex they are skills. Claude Code and Codex run agents side by side, Cursor and Pi one after another.

You need Node.js 24 or later and a Git repository.

Claude Code

Type these two lines in the Claude Code chat, one after the other.

/plugin marketplace add Kanevry/session-orchestrator
/plugin install session-orchestrator@kanevry

Once per project: /bootstrap --fast --no-interview. Then /session gives you a plan, and nothing in your code changes until you answer /go.

Codex

In a terminal, once. Requires Codex CLI 0.160 or later.

git clone https://github.com/Kanevry/session-orchestrator.git ~/Projects/session-orchestrator
cd ~/Projects/session-orchestrator && npm install && node scripts/codex-install.mjs

Then start a fresh Codex task, type /hooks and approve the Session Orchestrator hooks. Once per project: $session-orchestrator:bootstrap --fast --no-interview.

In the Codex chat, in the app or the CLI, the commands are skills: $session-orchestrator:session, $session-orchestrator:go, $session-orchestrator:close.

Cursor

In a terminal, once:

git clone https://github.com/Kanevry/session-orchestrator.git
cd session-orchestrator && npm install
node scripts/cursor-install.mjs /absolute/path/to/your/project

Then /bootstrap once and /session in the Cursor chat.

Pi

In a terminal, once:

npm install -g --ignore-scripts @earendil-works/pi-coding-agent
pi install npm:session-orchestrator

Then /bootstrap once and /session in Pi.

The plugin is free; your coding tool has its own costs. Step by step in the guide

Several sessions at once? Add the lead.

One lead session watches them and collects every question that needs you in one Inbox.

Optional. Session Orchestrator works without it. About the lead

Made by Bernhard Götzendorfer, who uses it on his own projects.

Free · MIT licensed · No account · Runs on your machine. Where it stops: