Two Tools I Installed Instantly for Claude Code & Codex
š¤ Curiosity: The Question
When I use Claude Code or Codex for frontend work, two things keep slowing me down:
1) āWhere exactly should the agent change?ā
2) āWhat did the agent actually do after the session ends?ā
I can live with imperfect models. I canāt live with vague feedback and invisible history.
Thatās why I installed two tools the moment I saw them.
š Retrieve: The Knowledge
1) Agentation ā precise UI feedback for agents
Agentation turns visual feedback into structured data.
Click the UI element ā get CSS selector + position + notes.
Instead of: āthe blue button in the sidebarā¦ā
You can pass: .sidebar > button.primary
Why it matters: Most UI fixes fail because the agent never edits the right spot.
What stood out:
npm i agentation(React 18+, dropāin component)- 4 output modes: Compact ā Forensic
- MCP Agent Sync for realātime feedback loops
- 170K npm downloads + viral tweet traction
āFrontend bottleneck isnāt model intelligence ā itās feedback precision.ā
2) Readout ā replay Claude Code sessions like video
Readout is a macOS native app that shows your agent environment and session history in one place.
Most impressive feature: session replay.
You can scrub through the timeline and see prompts, tool calls, and file diffs unfold.
What stood out:
- Free download, localāonly (no account)
- Playback speed control + stepābyāstep navigation
- Codex support already shipped
flowchart LR
A[UI feedback] --> B[Agentation selector]
B --> C[Claude/Codex edit]
C --> D[Readout session replay]
D --> E[Iterate]
3) Why these spread fast
Both tools were built by Benji Taylor (Coinbase Base design head).
Heās not āfullātime dev tooling,ā yet he solved the most painful UX issues first.
That pattern matters: the best tools often come from practitioners, not vendors.
š” Innovation: The Insight
How Iād use this in production
Pipeline for UI work:
- Isolate components in Storybook
- Use Agentation to click + annotate UI issues
- Pass selectors + notes to Claude Code
- Use Readout to audit and replay the changes
This turns frontāend tuning into a repeatable loop instead of fuzzy instructions.
Key Takeaways
| Insight | Implication | Next Step |
|---|---|---|
| UI feedback is the true bottleneck | Better feedback beats bigger models | Standardize selectors |
| Session replay enables trust | Debugging becomes systematic | Make replay part of review |
| Practitioners build sharper tools | UX pain ā product | Encourage internal toolmaking |
New Questions This Raises
- Whatās the minimum UI context an agent needs to edit correctly?
- Could we autoāgenerate UI diffs from Agentation + Readout logs?
- What other āinvisible bottlenecksā are hiding in agent workflows?
References
- Agentation: https://agentation.dev
- Readout: https://readout.org
- Demo post: https://lnkd.in/guKPyq_8
