pause_turn handling

Definition

pause_turn is the stop reason returned when a server-tool loop hits its iteration cap; you continue by resending the conversation unmodified rather than by executing a tool.

Key points

• Occurs with server-executed tools (e.g. web_search, code_execution) where Anthropic runs the tool loop internally and pauses at a cap.
• Recovery: resend the returned conversation as-is to let Claude continue the long-running server-side operation.
• Unlike tool_use, there is no tool_result for you to build — server tools never require you to construct one.
• It exits the client-side Agentic loop like every non-tool_use reason, but the correct response is "resend to continue," not "we're done."

Why it matters for the exam

• Distractors will suggest treating pause_turn as a failure, or as needing a tool_result. The right action is simply resending the conversation.

Common gotchas

• Don't confuse with max_tokens (truncation) or end_turn (finished) — pause_turn means "more server-side work pending, resend."
• Applies to server-executed tools, not client tools.

See also

• Stop reasons
• Agentic loop
• Tool execution types (client vs server)

Sources

• netlight-study-guide