Hierarchical multi-agent orchestration for Claude Code. Plans, delegates to parallel workers, reviews with Codex, and traces user flows across code boundaries. Think of it as a software engineering department in your terminal: a director plans the work, managers coordinate, and engineers (headless Claude Code sessions) execute.
active 2026-02-24 → 2026-03-14 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 19 days from 2026-02-24 to 2026-03-14. Pushes: 9 total, peak 2 in a day. Pull requests: 2 total, peak 2 in a day. Issues: 54 total, peak 42 in a day. Comments: 10 total, peak 10 in a day. Stars: 0 total, peak 0 in a day.
- Pushes
- Pull requests
- Issues
- Comments
- Stars
Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.
Top contributors
Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity
| Contributor | Contributions | Pushes | PRs | Comments |
|---|---|---|---|---|
| clpotvin | 75 | 9 | 2 | 10 |
Recent activity
Latest issues, pull requests and releases
- Issue comment#26clpotvin2026-03-10 22:42Collection of low-severity issues: clock skew, event log rotation, retry decay, logging
- Issue#31clpotvin2026-03-10 22:42[INFO] validateFileName URL decoding catches up to 3 levels
- Issue comment#32clpotvin2026-03-10 22:42[INFO] Planner MCP tool path constraint is properly implemented
- Issue#24clpotvin2026-03-10 22:42Stale orchestrator messages persist across cycles and resumes
- Issue#21clpotvin2026-03-10 22:42Worker security constitution missing HTTPS/TLS, crypto, and data classification guidance
- Issue#15clpotvin2026-03-10 22:41SECURITY: Sensitive files written world-readable (0o666) — state, logs, sessions
- Issue comment#16clpotvin2026-03-10 22:41SECURITY: No size limits on MCP tool string inputs — DoS via large payloads
- Issue comment#15clpotvin2026-03-10 22:41SECURITY: Sensitive files written world-readable (0o666) — state, logs, sessions
- Issue#14clpotvin2026-03-10 22:41SECURITY: Path traversal via unvalidated task/contract/session IDs in MCP tools
- Issue comment#14clpotvin2026-03-10 22:41SECURITY: Path traversal via unvalidated task/contract/session IDs in MCP tools
- Issue#13clpotvin2026-03-10 22:41BUG: Promise.all timing measures both durations from same start — wrong metrics
- Issue comment#13clpotvin2026-03-10 22:41BUG: Promise.all timing measures both durations from same start — wrong metrics
- Issue#11clpotvin2026-03-10 22:41BUG: Codex worker stream buffers can grow unbounded — OOM risk
- Issue#12clpotvin2026-03-10 22:41BUG: Flow tracer has no overall timeout — can hang cycle indefinitely
- Issue comment#12clpotvin2026-03-10 22:41BUG: Flow tracer has no overall timeout — can hang cycle indefinitely
- Issue#10clpotvin2026-03-10 22:41BUG: No guard against concurrent CLI invocations on same project
- Issue comment#11clpotvin2026-03-10 22:41BUG: Codex worker stream buffers can grow unbounded — OOM risk
- Issue comment#10clpotvin2026-03-10 22:41BUG: No guard against concurrent CLI invocations on same project
- Issue#8clpotvin2026-03-10 22:40BUG: Orphaned task reset races with claim_task — task can be claimed twice
- Issue#5clpotvin2026-03-10 22:40BUG: Task claiming TOCTOU race — multiple workers can claim same task
- Issue#3clpotvin2026-03-10 22:40BUG: State not persisted after cycle increment — causes infinite loops on resume
- Issue comment#5clpotvin2026-03-10 22:40BUG: Task claiming TOCTOU race — multiple workers can claim same task
- Pull request#33clpotvin2026-03-07 20:37
- Pull request#33clpotvin2026-03-07 20:37
- Issue#32clpotvin2026-03-07 06:28[INFO] Planner MCP tool path constraint is properly implemented
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 0 stars here means stars gained during the window, not the repo's star count.