Context editing is currently in beta with support for tool result clearing. To enable it, use the beta header
context-management-2025-06-27
in your API requests. Additional context editing strategies will be added in future releases.Please reach out through our feedback form to share your feedback on this feature.How it works
Theclear_tool_uses_20250919
strategy clears tool results when conversation context grows beyond your configured threshold. When activated, the API automatically clears the oldest tool results in chronological order, replacing them with placeholder text to let Claude know the tool result was removed. By default, only tool results are cleared. You can optionally clear both tool results and tool calls (the tool use parameters) by setting clear_tool_inputs
to true.
Context editing invalidates cached prompt prefixes because clearing content modifies the prompt structure, breaking the match requirement for cache hits. To account for this, we recommend clearing enough tokens to make the cache invalidation worthwhile. Use the clear_at_least
parameter to ensure a minimum number of tokens is cleared each time. When using prompt caching with context editing, you’ll incur cache write costs each time content is cleared, but subsequent requests can reuse the newly cached prefix.
Supported models
Context editing is available on:- Claude Opus 4.1 (
claude-opus-4-1-20250805
) - Claude Opus 4 (
claude-opus-4-20250514
) - Claude Sonnet 4.5 (
claude-sonnet-4-5-20250929
) - Claude Sonnet 4 (
claude-sonnet-4-20250514
)
Basic usage
The simplest way to enable context editing is to specify only the strategy type, as all other configuration options will use their default values:Advanced configuration
You can customize the context editing behavior with additional parameters:Configuration options
Configuration option | Default | Description |
---|---|---|
trigger | 100,000 input tokens | Defines when the context editing strategy activates. Once the prompt exceeds this threshold, clearing will begin. You can specify this value in either input_tokens or tool_uses . |
keep | 3 tool uses | Defines how many recent tool use/result pairs to keep after clearing occurs. The API removes the oldest tool interactions first, preserving the most recent ones. |
clear_at_least | None | Ensures a minimum number of tokens is cleared each time the strategy activates. If the API can’t clear at least the specified amount, the strategy will not be applied. This helps determine if context clearing is worth breaking your prompt cache. |
exclude_tools | None | List of tool names whose tool uses and results should never be cleared. Useful for preserving important context. |
clear_tool_inputs | false | Controls whether the tool call parameters are cleared along with the tool results. By default, only the tool results are cleared while keeping Claude’s original tool calls visible. |
Response format
You can see which context edits were applied to your request using thecontext_management
response field, along with helpful statistics about the content and input tokens cleared.
Response
message_delta
event:
Streaming Response
Token counting
The /v1/messages/count_tokens endpoint supports context management, allowing you to preview how many tokens your prompt will use after context editing is applied.Response
input_tokens
) and the original token count before any clearing occurred (original_input_tokens
).