Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.308 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.281 ·

Requests and compaction gain advisorStripPlan, reminderFold and declaredToolNames

Advisor tool output can now be stripped from selected messages only, and main requests and compaction share reminder-folding and tool-name options

Group of 5 Under the hood Internal Changes
JSON All of v2.1.281
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
CompactionArea: what it touches
Internal ChangesKind: in v2.1.281,
Internal ChangesSection of the release

Unclear The finding does not say what advisorStripPlan removes or when it applies.

What

Before each request to the model, Claude Code rebuilds the conversation into the format the API expects. That step gains three new options:

  • advisorStripPlan: removing advisor tool blocks (advisor_tool_result and advisor server_tool_use) can now be limited to a chosen set of assistant messages. Before, they were removed from every assistant message. A message left empty still gets the text "[Advisor response]". This works like the existing thinkingStripPlan.
  • reminderFold: a setting for how reminder messages are folded into turns, now passed into this rebuilding step.
  • declaredToolNames: added next to keptToolNames to the set of tool names whose tool_reference blocks are kept.

Compaction, which summarises a long conversation to free up room, now uses the same options. Compact and reactive-compact runs pass advisorStripPlan next to thinkingStripPlan. The compact summariser also computes a reminder fold and passes advisorStripPlan and reminderFold into the request. Its fallback, refusal and credit handling is unchanged. Reuse of the existing prompt during compaction is still controlled by a separate server flag.

Why

Advisor output can now be kept for some turns and dropped for others, instead of all or nothing. Compaction requests are now shaped the same way as normal requests, so the conversation being summarised is prepared by the same rules.

Read from
Feature flag
tengu_compact_cache_prefix Off in both readings

The flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.

This account: off · anonymous baseline: off · compiled default in v2.1.281: on

These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.

tengu_wild_tome Off by default, switched on for this account

The shipped code defaults this off, and the flag server returned on for the one account this site reads on this version. That is the reading that makes the entry above worth a second look, and it still says nothing about your account.

This account: on · anonymous baseline: on · compiled default in v2.1.281: off

These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.

Read once, for one account on one subscription tier, against v2.1.281. It isn't a statement about your account. What a flag value here can and cannot tell you

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtThe finding does not say what `advisorStripPlan` removes or when it applies.

See this entry in the whole of v2.1.281 →

Feedback