Dev prompts agent to add traces everywhere and self-diagnose his slow CLI
DanielLockyer · x · 2026-10-17
Developer @chronark shared a clever workflow: when his CLI felt slow but he couldn't tell why, he simply prompted an agent to add traces everywhere and self-diagnose, then push the traces to Axiom for human inspection.
The flame-graph screenshot shows a single run with 76 spans totaling 1.2s, with SLOW segments clearly flagged: 180ms in discovery, several test.execute spans at 400-600ms each, and cache.enumerate costing hundreds of ms. As he puts it: not faster yet, but at least he knows where it's slow.
More from coding & agent
- StackOne ships Tool Policies: fine-grained guardrails for MCP tool calls — afp-media · 2026-10-17
- Huntley: developers displaced by AI 'failed a curiosity test' — rseroter · 2026-10-17
- RAX open-sources everything: zero demos, all experiment sessions included — du_yilun · 2026-10-17
- RAX separates the coding agent workspace from the robot stack for multi-embodiment — du_yilun · 2026-10-17
- shadcn reflects: it's only been a year since Claude Skills launched — shadcn · 2026-10-17
- ClinOpsBench: 15 AI agents tested on 4-month simulated clinical trial oversight — ycombinator · 2026-10-17