Show HN: Lazyagent – Preserve what your AI agents doing and analyze usage
TL;DR
Once subagents start spawning other subagents, basic questions get hard to answer: what is running right now, what tool did it just call, did the child agent actually do what the parent asked. I wanted a way to verify that each agent is doing the work that fits its role, and to spot when a run goes off track. Lazyagent is a terminal TUI that collects events from Claude Code, Codex, and OpenCode and shows them in one place. It groups sessions from different runtimes by working directory, so Claude and Codex runs on the same repo appear under the same project. Features: - Filter events by type: tool calls, user prompts, session lifecycle, system events, or code changes only. - See which agent or subagent is responsible for each action. The agent tree shows parent-child relationships, so you can trace exactly what a spawned subagent did vs what the parent delegated. - View code diffs at a g.
Nauti's Take
Observability for AI agents is a genuine blind spot — anyone who has debugged complex multi-agent workflows knows how quickly things get opaque. Lazyagent tackles this head-on with a pragmatic terminal UI.
The tool is early-stage, so keeping pace with rapidly evolving agent runtimes is the real challenge, but the core idea is exactly what the ecosystem needs.
Summary
Once subagents start spawning other subagents, basic questions get hard to answer: what is running right now, what tool did it just call, did the child agent actually do what the parent asked. I wanted a way to verify that each agent is doing the work that fits its role, and to spot when a run goes off track.
Lazyagent is a terminal TUI that collects events from Claude Code, Codex, and OpenCode and shows them in one place. It groups sessions from different runtimes by working directory, so Claude and Codex runs on the same repo appear under the same project.
Features: - Filter events by type: tool calls, user prompts, session lifecycle, system events, or code changes only. - See which agent or subagent is responsible for each action.
The agent tree shows parent-child relationships, so you can trace exactly what a spawned subagent did vs what the parent delegated. - View code diffs at a g
Sources