Practice

Your YesChef support agent loop occasionally never returns to the user — it keeps calling tools in circles when a chef's availability tool returns ambiguous data. A teammate proposes capping the loop at 5 iterations and returning whatever text the model last produced. Why is this the wrong primary fix?

In a single response, Claude returns two tool_use blocks: lookup_order and get_customer. What must your loop do before the next API call?

You run your research system on 'caring for columnar cacti in cold climates.' Every subagent succeeds, yet the final report covers only watering and ignores cold-hardiness, soil, and light. The coordinator log shows it decomposed the topic into 'watering frequency,' 'watering amount,' and 'overwatering signs.' What is the most likely root cause?

Your coordinator delegates to a synthesis subagent, but the synthesis output keeps inventing which source a statistic came from. The search subagent definitely found correct, attributed data. What is the most direct fix?

Production data shows your YesChef agent skips get_customer in 12% of cases and issues refunds against a customer's stated name, sometimes refunding the wrong account. Which change most effectively fixes this?

Your booking tools return dates inconsistently: get_yeschef_booking gives a Unix epoch, lookup_chef_availability gives ISO 8601, and a legacy tool returns a numeric status code. The agent keeps miscomparing dates. Which hook and why?

A PR touches 14 files in your Music League data pipeline. Your single-pass review gives deep feedback on some files, shallow on others, misses obvious bugs, and even flags a pattern in one file while approving identical code in another. Best restructuring?

You analyzed the YesChef codebase in a session yesterday, then refactored three files. Today you want the agent to continue, but its prior tool results now describe code that no longer exists. Best approach?