PRODUCTION SCENARIO
A support-ticket agent makes dozens of file-read and log-search tool calls per session and is approaching the context limit. The team has already turned on the context management beta, and the agent must keep the result of its get_account_profile call for the whole session while dropping stale search output.
Which context editing configuration meets this need?
Answering here is anonymous. Nothing is saved unless you sign in.
Show answer and explanation
Answer: clear_tool_uses_20250919 with exclude_tools set to ["get_account_profile"] and keep 3
exclude_tools lists the tools whose uses and results are never cleared, the only setting that pins one result while the rest of the tool output recycles. clear_thinking_20251015 governs thinking blocks and protects no tool result. clear_tool_inputs is a single boolean for the whole strategy and strips the recorded call parameters as well, which clears more context rather than preserving the profile. A higher trigger only postpones clearing, and the profile result is the oldest thing in the transcript, so it goes first when clearing does begin.