Under the hood
Artifacts and session-context data can now carry an optional deadline field
What
The internal option builders for artifacts and session context (data Claude Code uses to track what's happening in a session) can now include a deadline field when one is set. The schema helper for session context was also updated to accept a deadline alongside the existing label field.
Why
This lays groundwork for artifacts or session context to carry timing information, though the finding does not say what feature consumes it yet.
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Added since
A small documentation edit on Environment variables touched a line naming deadline after this was published.
| `CLAUDE_CODE_WEBFETCH_DEADLINE_MS` | Upper bound in milliseconds on how long [WebFetch](/docs/en/tools-reference#webfetch-tool-behavior) waits for a page to download, including any redirects it follows. A download that hasn't completed b…env-vars see the edit
Confirmed since
Anthropic's documentation has since written up deadline, on Claude Code changelog.
* Fixed WebFetch hanging indefinitely on a server that keeps the response open without finishing; a fetch now fails after 300 seconds. Set `CLAUDE_CODE_WEBFETCH_DEADLINE_MS` to override the deadline (0 turns it off)changelog see the edit
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
It's unclear what feature or UI actually uses this deadline field once set.
Anthropic's documentation agrees
Anthropic's documentation has since written up deadline, on Claude Code changelog.