Cancellation changedspecification/2026-07-28/basic/patterns/cancellation
Nearest release: v2.1.305, published under an hour before upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 20 Oct 2026 20:02 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 22 Oct 2026 20:37 UTC.
Upstream edited
Recorded here
Lines+2added
Lines−2removed
From line
54
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits3to this page, all time
The whole hunk
from line 54, old and new numbered
/
from line 54
5454per-request basis.
5555
5656Implementations **MAY** choose to reset the timeout clock when receiving a
57[progress notification](/specification/2026-07-28/basic/patterns/progress) corresponding to
57[progress notification](/specification/2026-07-28/basic/patterns/progress.md) corresponding to
5858the request, as this implies that work is actually happening. However, implementations
5959**SHOULD** always enforce a maximum timeout, regardless of progress notifications, to
6060limit the impact of a misbehaving client or server.
from line 115
115115This maintains the "fire and forget" nature of notifications while allowing for race
116116conditions in asynchronous communication.
117117
118[subscriptions]: /specification/2026-07-28/basic/patterns/subscriptions
118[subscriptions]: /specification/2026-07-28/basic/patterns/subscriptions.md
119119
No line in this hunk matches that.