Tip: ask your agent to create a /debug page

Have been using this "trick" more and more frequently.

When you're running into trouble articulating what's going right or wrong when working with a coding assistant/agent, consider asking it to build a /debug page.

Doesn’t need to be fancy. Just a simple live and visual canvas that shows:

• what the agent thinks it’s doing
  


• what inputs it’s working with
  


• what tools are firing (or not)
  


• any recent errors or outputs

There are other ways to do this sort of thing (browser/server logs, MCP with tighter feedback loops, etc), but this has been a quick/dirty trick that has saved me some frustrating debugging sessions.

Especially good when something’s almost working and you can’t quite tell why.