# session-flow

> A workflow for coding agents, with persistent work records and a generated backlog.

- Type: open source component
- Status: v3.2.0
- License: MIT
- Language: Python
- Repository: https://github.com/matshoppenbrouwers/session-flow
- Author: Mats Hoppenbrouwers (hoponthestack)
- Canonical URL: https://www.frameworkreboot.com/products/session-flow

Session workflow orchestration for Claude Code: a complete development lifecycle chain, from research through release, with dependency-aware parallelization and collaborative brainstorming at every stage.

## Writing and releases

- [What session-flow adds to plain Claude Code, and when to skip it](https://www.frameworkreboot.com/writing/session-flow-vs-plain-claude-code) (Nov 2026): What my Claude Code plugin adds over using the agent with nothing installed, and the cases where it is not worth the overhead.
- [session-flow 3.2.0: isolated workspaces and one integration owner](https://www.frameworkreboot.com/writing/session-flow-3-2-0-isolated-workspaces-and-one-integration-owner) (Oct 2026): Task sessions work in isolated source workspaces and hand off exact commits. One owner per repository integrates and releases.
- [session-flow 3.1.0: verify reuses existing evidence](https://www.frameworkreboot.com/writing/session-flow-3-1-0-verify-reuses-existing-evidence) (Oct 2026): Verify reuses evidence that still applies and runs only the checks that are missing, failing or stale. Simplify becomes an add-on, and a project can name a runbook for delivery.
- [session-flow 3.0.0: a stricter runtime contract](https://www.frameworkreboot.com/writing/session-flow-3-0-0-a-stricter-runtime-contract) (Oct 2026): 3.0.0 has breaking changes to the runtime's payloads. The runtime refuses payloads it used to accept, and claim and record-result now move tasks through their lifecycle.
- [session-flow v2: persistent work items](https://www.frameworkreboot.com/writing/session-flow-2-0-persistent-work-items) (Oct 2026): A Python runtime now manages work records and generates the backlog. The chain has sixteen skills, including a migration path for existing projects.
- [session-flow 2.0.3: only open work in the sequence](https://www.frameworkreboot.com/writing/session-flow-2-0-3-only-open-work-in-the-sequence) (Oct 2026): Deferred and cancelled work leaves SEQUENCE.md too. The generated backlog contains only open work, and retired identities stay taken.
- [session-flow 2.0.2: completed work leaves the sequence](https://www.frameworkreboot.com/writing/session-flow-2-0-2-completed-work-leaves-the-sequence) (Oct 2026): Done items leave SEQUENCE.md while their records remain available. The backlog stays shorter as work is finished.
- [session-flow 2.0.1: migration can start without a work root](https://www.frameworkreboot.com/writing/session-flow-2-0-1-migration-without-a-work-root) (Sep 2026): Repair can now survey an older backlog before its namespace or work root exists. The plan includes the setup it needs, with no writes until you approve it.
- [Why session-flow is a chain](https://www.frameworkreboot.com/writing/why-session-flow-is-a-chain) (Sep 2026): A Claude Code plugin that writes down the instructions I was otherwise retyping every session.
- [session-flow 1.7.0: reporters report, callers filter](https://www.frameworkreboot.com/writing/session-flow-1-7-0-reporters-report-callers-filter) (Sep 2026): Review agents now label every finding by confidence instead of quietly dropping the uncertain ones. Two conversational skills join the chain, one agent leaves it, and a backlog can now be shared across repos.

## Glossary

- [Evidence-based verification](https://www.frameworkreboot.com/glossary/evidence-based-verification): A pass that cites a file and line, a command's output or a test name for every claim, and treats missing evidence as failure.
- [Independent test oracle](https://www.frameworkreboot.com/glossary/independent-test-oracle): Acceptance tests written before implementation by a different agent, which the implementers must satisfy and may never edit.
- [Reporters report, callers filter](https://www.frameworkreboot.com/glossary/reporters-report-callers-filter): Review agents label every finding high, medium or low confidence instead of withholding the uncertain ones, and the skill that called them decides what to act on.
- [SEQUENCE.md](https://www.frameworkreboot.com/glossary/sequence): The generated backlog view: one line per open work item, with a stable identity and either a breakdown link or a marker that it needs one.
- [Session-sized task](https://www.frameworkreboot.com/glossary/session-sized-task): A unit of work small enough for one agent session to finish: one to five files, clear acceptance criteria, one commit.
- [Task breakdown](https://www.frameworkreboot.com/glossary/task-breakdown): The set of task records under one work item, each self-contained enough to hand to an agent on its own.
- [The chain](https://www.frameworkreboot.com/glossary/the-chain): The arrangement of session-flow's skills so that each stage produces the artifacts the next one consumes.
