session-orchestrator

Session Orchestrator

Your coding agents get an agreed plan, a check after each round of changes and a handover to the next session.

A free, MIT-licensed workflow plugin for people running Claude Code, Codex CLI, Cursor IDE or Pi on a git repository. It runs on your machine and writes plain text into your repository: no account, no server.

Website (Deutsch) · Commands · User guide · Changelog

Beta: 15 free seats in the agenticbuilders Pass for Session Orchestrator users. You learn to get real work done with Claude Code and agents. In return you tell me for 14 days what helped. Want a seat? agenticbuilders.at/so

Install

You need Node.js 24 or later and a git repository. In Claude Code:

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

Codex CLI, Cursor IDE, Pi, upgrade and uninstall: docs/install.md.

How it works

• /session reads your repository, your open issues and the last session, proposes what to work on, and waits for your correction. Nothing changes in your code until you agree.
• /go runs the agreed work in waves: rounds of parallel agents, each with its own list of files. Your tests and typecheck run after each wave; failures become fix tasks for the next one.
• /close runs the full test, typecheck and lint gate, checks every planned item against what happened, commits, and files the rest as GitLab or GitHub issues.

First session

1. Run /bootstrap --fast --no-interview once in your project. It adds a short config block to your instruction file (CLAUDE.md or AGENTS.md).
2. Set the three gate commands in that block to what your project uses, for example test-command: npm test, typecheck-command: npm run typecheck, lint-command: npm run lint. Every other key is optional (reference).
3. Run /session feature and describe the task. Correct the proposed scope, then run /go and, when the work is done, /close.

On Codex and in headless Claude Code (claude -p) some command names differ: Codex · headless.

What do you want to do?

All 31 commands, by situation: session-orchestrator.com/commands

It learns, with your yes

/evolve suggests lessons from your own session records; /reconcile turns the ones you approve into rule files that later sessions load. It never trains a model and never changes itself without your approval (how it works).

Add-on: lead-session-orchestrator

Running three or four sessions side by side? lead-session-orchestrator adds one lead session above them that decides which one goes next and puts their questions into one queue for you. It is a separate npm package; details and caveats: docs/install.md.

User guide · Install · Components · Telemetry (off unless you turn it on) · Contributing · Security · Issues · MIT · Privacy · npm · All docs

Provided as-is: a community project with best-effort maintenance and no SLA. Independent, and not affiliated with or endorsed by Anthropic, OpenAI or Cursor. The method is taught at agenticbuilders.at; the plugin is free and does not need the courses.