Let your agent read its own traces: AgentsView + history tool debugging workflow
dbreunig · x · 2026-10-23
dbreunig shares an agent debugging workflow: point the agent at the AgentsView CLI and ask it to inspect traces and figure out what went wrong — remarkably effective. It builds on badlogic's history tool approach of letting agents read their own run history for root-cause analysis.
More from coding & agent
- Vercel ships 'vercel deploy --temporary' for ephemeral agent-built deployments — cramforce · 2026-10-23
- Running multiple agents out of one Notion workspace as a shared task board — nbaschez · 2026-10-23
- We tested 12 LLM classifiers — the new classifier hype is LARP — KlausCodes · 2026-10-23
- Dev builds ESP32 desk display showing Claude Code and Codex agent status via local Go helper — tonylook · 2026-10-23
- YC-backed Mireye launches land search API + MCP with 160M parcels for AI agents — ycombinator · 2026-10-23
- Testing 12 decision systems: the new LARP hype around classifiers — KlausCodes · 2026-10-23