← All IntelClip / AI AgentsInterrogate the agent when a run goes wrong or runs long
From I made Claude smarter by writing it a letter · ≈23:18
A debugging loop for agent behavior: ask why it made a decision and what it spent time on, which often surfaces stale lines in your own agents file or a bad early inference that stuck in context.
What’s in it
- A debugging loop for agent behavior: ask why it made a decision and what it spent time on, which often surfaces stale lines in your own agents file or a bad early inference that stuck in context.
Clip transcript
through all of that yourself and really think about it. And getting stats on what the failure cases are and getting your agents to give you the feedback on what happened is super helpful. And if you notice certain threads that just didn't go how you want, you should work with the agent to fix that. You should ask it why did you make this decision? What gave you indication that this was the right direction? It might be something that's outdated in your cloud MD or agents MD. It might be something that it read incorrectly early and then followed along once it was in context that didn't actually make sense. Think about these failure modes, notice them when they happen, and ask the agent questions. Another really common one is if you ask for what you think will be a simple change and the agent takes 30 minutes or more when you thought it would take five. Ask the agent why it took longer. What did it spend its time on? Ask it to categorize all of the tool calls it made into different groups and try to determine which ones were and weren't helpful so that you can make adjustments to help the model make better decisions in the future. And I guess with that there's no better time
Comments
Sign in to comment.
Loading comments…