agent-flow vs agent-orchestration-standard
Live node-graph visualization of Claude Code and Codex sessions — watch agents think, branch into subagents and call tools in real time. VS Code extension or npx web app. Apache-2.0. — versus — Read-only live monitor for Claude Code: a streaming graph of sessions, subagents, tokens, cost, file conflicts and alerts, as plugin, TUI and MCP server. Ships the AOS-1 spec.
Both visualize live Claude Code sessions as a node graph. AOS adds tokens, cost, file-conflict alerts and replay.
| agent-flow | agent-orchestration-standard | |
|---|---|---|
| Stars | 1.8k | 103 |
| Forks | 217 | 22 |
| Language | TypeScript | JavaScript |
| License | Apache-2.0 | MIT |
| Last activity | 8 days ago | 2 days ago |
| Topics | coding | orchestration, coding |
| Curated connections | 4 | 3 |
agent-flow — the curator's take
The black-box opener: hooks stream Claude Code events (Codex via rollout-file tailing) onto an interactive canvas where you watch a session branch into subagents, spot the slow tool call, trace the decision chain that went wrong, and replay any JSONL log. Zero-friction start — `npx agent-flow-app` and go — and it earns its keep two ways: debugging orchestration, and building prompt intuition by literally watching how the agent interprets you. Born inside a real product (CraftMyGame), not a demo. NOT analytics — no cost aggregation or history (that's claude-code-karma's job). Note the npx binary ships opt-out telemetry: aggregate-only, documented field-by-field, honors DO_NOT_TRACK; dev and extension builds send nothing.
agent-orchestration-standard — the curator's take
Use it to watch what parallel Claude Code sessions and subagents are doing right now, with replay and alerts, at no install cost (no dependencies). Despite the name, it does not orchestrate anything: that is a separate experimental repo. Active development has moved to Fenceline, so this repo may go stale. Claude Code only.