context-editing changedbuild-with-claude/context-editing
Nearest release: v2.1.310, published 11 hours after this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Recorded here
Lines+5added
Lines−5removed
From line
1,334
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits21to this page, all time
The whole hunk
from line 1334, old and new numbered
/
from line 1334
13341334You can use both thinking block clearing and tool result clearing together:
13351335
13361336<Note>
1337 When using multiple strategies, the `clear_thinking_20251015` strategy must be listed first in the `edits` array.
1337 When using multiple strategies, you must list the `clear_thinking_20251015` strategy first in the `edits` array.
13381338</Note>
13391339
13401340<CodeGroup>
from line 1735
17351735
17361736You can see which context edits were applied to your request using the `context_management` response field, along with helpful statistics about the content and input tokens cleared.
17371737
1738```text Output wrap
1738```json Output
17391739{
17401740 "id": "msg_013Zva2CMHLNnXjNJJKqJ2EF",
17411741 "type": "message",
from line 1767
17671767
17681768For streaming responses, the context edits are included in the final `message_delta` event:
17691769
1770```text Streaming Response wrap
1770```json Streaming Response
17711771{
17721772 "type": "message_delta",
17731773 "delta": {
from line 2069
20692069 ```
20702070</CodeGroup>
20712071
2072```text Output wrap
2072```json Output
20732073{
20742074 "input_tokens": 25000,
20752075 "context_management": {
from line 2798
27982798
27992799For example, after a web search operation, the API response might show:
28002800
2801```text Output wrap
2801```json Output
28022802{
28032803 "usage": {
28042804 "input_tokens": 63000,
No line in this hunk matches that.