Progress changedspecification/2025-11-25/basic/utilities/progress
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+1added
Lines−1removed
From line
62
where the diff opens
First seen
26 Aug 2026
this site's first read of the page
Recorded edits3to this page, all time
The whole hunk
from line 62, old and new numbered
/
from line 62
6262 * Send notifications at whatever frequency they deem appropriate
6363 * Omit the total value if unknown
6464
653. For [task-augmented requests](./tasks), the `progressToken` provided in the original request **MUST** continue to be used for progress notifications throughout the task's lifetime, even after the `CreateTaskResult` has been returned. The progress token remains valid and associated with the task until the task reaches a terminal status.
653. For [task-augmented requests](/specification/2025-11-25/basic/utilities/tasks.md), the `progressToken` provided in the original request **MUST** continue to be used for progress notifications throughout the task's lifetime, even after the `CreateTaskResult` has been returned. The progress token remains valid and associated with the task until the task reaches a terminal status.
6666 * Progress notifications for tasks **MUST** use the same `progressToken` that was provided in the initial task-augmented request
6767 * Progress notifications for tasks **MUST** stop after the task reaches a terminal status (`completed`, `failed`, or `cancelled`)
6868
No line in this hunk matches that.