Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial

stampThreadState

setting never mined JSON

A Claude Code settings key, read out of the shipped bundle. No mined inventory carries it: everything below comes from what this site has written about it.

Cron-triggered prompts can now stamp thread state onto the resulting agent turn

Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.265.

First seen — never in a mined build
Last seen — never in a mined build
Builds0 / 161on this box, as of v2.1.322
Written about v2.1.265 first named in a changelog, 8 Sep 2026

In the changelogs

4

Releases whose published page names stampThreadState.

  1. v2.1.265
    Prompt submission can now stamp thread state on cron-fired agent turns

    Cron-triggered prompts can now stamp thread state onto the resulting agent turn

    found in this entry's text

  2. v2.1.265
    Incoming user messages in Projects threads can be stamped with thread state

    User messages in Projects threads can now be tagged with the thread's state

    named in this entry, found in this entry's text

  3. v2.1.265
    "thread_state" added as a recognized prefix-delta/context category

    New "thread_state" category joins prefix_delta and diagnostics in context tracking, with a related stampThreadState flag

    named in this entry, found in this entry's text

  4. v2.1.265
    "thread_state" content-block type recognized in message/prefix-delta pipelines

    Claude Code's context system now recognizes a new "thread_state" content type alongside prefix_delta and diagnostics

    found in this entry's text

First cited

3

The earliest release whose published evidence quoted stampThreadState was v2.1.265, 8 Sep 2026. That is the oldest release this project wrote about it, so it is a floor on the name's age and not the release that introduced it. It is not a presence reading: which builds carried the name is the table below.

ReleaseDateThe span that was quoted
v2.1.2658 Sep 2026...(bs && { stampThreadState: !0 })
v2.1.2658 Sep 2026stampThreadState
v2.1.2658 Sep 2026stampThreadState: !0

Presence across releases

0

The miner has never read a build containing this name. It is here because a changelog entry of ours names it, which is evidence that it existed and not evidence of which releases carried it. The inventory starts at v2.1.138 and everything older than that was never mined.

Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the settings key does. All settings keys.

Feedback