Session Orchestrator plugin
An agreed plan, a check after each wave of edits and a handover to the next session for Claude Code and Codex.
- 53 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Subagents and hooks run tests, lint and commits in your repository.
- To file issues the plugin uses `gh` or `glab` with your permissions.
Install
- Works in
Manual install
/plugin marketplace add Kanevry/session-orchestratorFirst command, then `/plugin install session-orchestrator@kanevry`.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Subagents and hooks run tests, lint and commits in your repository.
- To file issues the plugin uses `gh` or `glab` with your permissions.
This is third-party code. Review the repository files before installing.
What it does
Session Orchestrator guides agent work in three steps. `/session` reads the repository, open issues and the last session, drafts what to work on and waits for your correction: nothing in your code changes until you agree. `/go` runs the agreed work in waves: parallel agents each get their own file list, overlaps are rejected, tests and typecheck run after each wave and failures become tasks for the next one. `/close` runs tests, types and lint, checks the plan against what happened, commits and files leftovers as GitLab or GitHub issues. There are 31 commands in all: `/plan new` prepares research, a PRD and issues, `/plan retro` reviews a phase, and `/evolve` with `/reconcile` turn lessons you approve into rule files. Progress is written down after each wave, so a crash does not lose the plan.
Who it is for. Developers who run several agents on a git repository and want a plan agreed before edits and a check at the end.
Good fit when
- A large feature needs a plan with acceptance criteria rather than code right away.
- Two agents edit the project in parallel and their files must not overlap.
- A session broke off and the next one should resume from where it stopped.
- The same mistakes keep returning and you want lessons saved as rules.
Not a fit when
- The project is not in a git repository.
- The task fits one short edit.
- The host is not Claude Code, Codex, Cursor or Pi.
Example request
Run /session feature: we need CSV report export, propose the scope and wait for my correction.Limitations
You need Node.js 24 or newer, a git repository and one of Claude Code, Codex CLI 0.160 or later, Cursor IDE or Pi. Filing issues in GitLab or GitHub needs `glab` or `gh`. The plugin writes plain text files into the repository and needs no account, and by default it only asks npm about updates, which can be turned off. On Codex and in `claude -p` mode some commands are named differently. Hooks and subagents run commands on your machine, so tests and lint must be safe to run.
How to disable. Remove the plugin through `/plugin` in Claude Code. Delete the `.orchestrator` files and the Session Config block in `CLAUDE.md` or `AGENTS.md` by hand.
FAQ
How do I install Session Orchestrator in Claude Code?
With `/plugin marketplace add Kanevry/session-orchestrator` and `/plugin install session-orchestrator@kanevry`. Steps for Codex, Cursor and Pi are in `docs/install.md`.
How do I start the first session?
Run `/bootstrap --fast --no-interview` once, set `test-command`, `typecheck-command` and `lint-command` in the Session Config block and run `/session feature`.
Does the plugin change code without consent?
No. `/session` only drafts the scope and nothing changes until you agree.
How does the plugin learn?
`/evolve` drafts lessons from your session records and `/reconcile` turns approved ones into rule files. It does not train a model and never changes itself without your approval.
Does it need an account or server?
No. It is free under MIT, writes text into the repository and has no server of its own.
Discussion
No questions or reviews yet.
Related
PluginsA plugin for Codex and Claude Code that runs a task through a chain of roles from planning to an independent audit
Plans, decisions and verification results live in Git: another agent or a teammate resumes the task with ~go
Xylocopa is a visual orchestrator for Claude Code agents: GTD tasks, parallel agents in git worktrees, phone approvals.
A plugin for Claude Code and Codex with xdo, xdel and xflow modes: a main agent plans, a coder builds, an evaluator checks.
A workflow template for Claude Code and five more agents: a backlog task, a diff review and a commit.
OpenCode plugin that turns a session into a team of agents led by an architect and runs the work through plan phases
README in short
The project describes a three command loop, 31 commands by situation and learning from your sessions. For Claude Code the main install goes through the plugin marketplace.