Collection · 4 entries
Observability for AI coding agents
Tools that show you what your coding agents are actually doing: token spend, session state, tool calls, and parallel execution.
Coding agents are still mostly black boxes if you don't instrument them. The tools below give you visibility at different scales: per-session token cost (codeburn), live runtime state (abtop, lazyagent), session-graph visualization (agent-flow), and side-by-side comparison across engines (parallel-code). Pick by the question you're trying to answer - 'where is the spend going' is different from 'what is this agent doing right now'.
Codeburn - token cost TUI for Claude Code & Codex
Interactive terminal dashboard that breaks down where your AI coding tokens actually go. Surfaces the chat-vs-tool-use split most users get wrong.
abtop - htop for AI coding agents
Rust TUI that monitors Claude Code and Codex sessions: token spend, context window, rate limits, and ports in real time. Like btop but for agent runtimes.
lazyagent - terminal observability for coding agents
Watch your Claude Code, Codex, and OpenCode sessions from a tiny Go TUI. Shows what each agent is doing, no SaaS dashboard needed.
agent-flow - real-time Claude Code orchestration view
Watch your Claude Code agents think, branch, and coordinate as they run. Live visualization of subagent trees and tool calls in the browser.
Related collections
Claude Code tools, plugins, and integrations
The best tools, MCP servers, and harnesses for getting more out of Claude Code - orchestration, observability, telemetry, and remote control.
Terminal UIs (TUIs) for daily workflows
Polished terminal UIs for git, tasks, observability, and agent control - the tools that make the terminal feel like a real surface again.
Multi-agent frameworks and orchestration
Frameworks, harnesses, and DSLs for coordinating multiple AI agents across handoffs, parallel waves, and tool use.