session-ops
The multi-repo operations layer: the feed, the clock, and the portfolio view across repos. It triages and drafts; it never implements and never publishes.
- Status
- v0.3.0
- License
- MIT
- Language
- Python
What is session-ops?
A multi-repo operations layer for Claude Code and a companion to session-flow. session-flow owns routing and judgement inside a repo; session-ops owns the feed, the clock, and metrics across repos, plus the multi-repo portfolio, the one thing session-flow structurally cannot see.
Glossary
An item the automation refuses to decide, written to a numbered file and surfaced for approval on the unit's pinned dashboard.
The cross-repo status rollup: backlog progress, inbox depth, open escalations, last release and activity, run quota and failure streak, for every managed unit.
The scheduled triage and sweep workflows on an enrolled unit, plus the guard that caps their cost and the heartbeat that reports their failure.
A repository that session-ops manages: one with a backlog, direction documents and an entry in the registry.