Alternatives
Products that do what ViewDoctor does
SwiftUI checks for agents in multi-module repos
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11
- 12
- 13
- 14
- 15
- 16
- 17
- 18PA
Hi HN! We’re Theodore and Louis, founders of Armature (YC P26). We reconstruct the entire session behind the MCP tool calls you receive, including what the user asked their agent to do and what the agent thought. You wrap your MCP in 3 lines of code (our SDK is available in Typescript, Python and Go) and start seeing in your dashboard: - All sessions reconstructed: it’s like reading the real conversation the user had inside Claude or ChatGPT! - A ranking of your MCP most popular use cases, built from sessions clustering - The most frequent issues your users’ agents encounter so you can fix…
Aug 2026 · armature.tech
- 19LA
Hi HN, I made tui observerbility tool for ai agents. 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. Also it can show your token usage information about the sessions. Features: Filter events by type: tool calls, user…
Apr 2026 · github.com
- 20
A fast, native app for local coding agents. Amp, Claude Code, Codex, Cursor, OpenCode, Grok, and Pi — one timeline, entirely on your machine.
21d ago · waku.sh
- 21LA
Lazyagent a simple way to see what your coding agents were actually doing across Claude, Codex, and OpenCode. Once you have more than 1 agent running, its really hard to answer the simple question: what is it doing right now and why? It is a local terminal UI that collects your agents runtime events and shows their activity in one place. You can inspect: - agents and subagents - tool calls - prompts - outputs - status changes Sessions and projects are there to give that activity some context, so it is easier to follow what happened over time and which run belongs to which repo. And make it…
Apr 2026 · github.com
- 2212
Jul 2026 · nibware.dev
- 23LT
Running multiple coding agents could make user losing track of what they were doing. 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. 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. From there you can: - Filter events by type: tool calls, user…
Apr 2026 · github.com
- 24
Ranked by how close each launch is in meaning, then by votes. Refine with a description →