Follow Discord
Sweep 25 Sep 2026 · 19:33Z Build v2.1.283 504 read Stable v2.1.274 Latest v2.1.283 Next v2.1.283 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.282 ·

Remote Control project-thread child sessions start with auto-compact on

Child sessions Remote Control starts for a project thread now get autoCompactEnabled turned on, behind a new switch that falls back to on

Group of 3 You'll notice Improvements
JSON All of v2.1.282
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
ElsewhereArea: what it touches
ImprovementsKind: in v2.1.282,
ImprovementsSection of the release

What

Child sessions that Remote Control starts for a project thread now get automatic compaction turned on. Automatic compaction (autoCompactEnabled) summarises older parts of a conversation when it nears the context limit, the most text the model can hold at once.

  • This applies to child sessions tagged "hearth-rc-child" (role projectThreadChild), and only when the new switch tengu_bridge_rc_child_auto_compact is on. Its built-in fallback is on; nothing has been read about it.
  • That role now grants autoCompact, next to defaultMode: "auto" in the settings generated for the child.
  • When a session is launched, the --settings JSON now passes autoCompact alongside autoOverSettings and autoModeEnvironment, and includes autoCompactEnabled: true when it is granted.
  • At attach, if flag settings do not already set autoCompactEnabled, it is set to true and listed in the reported granted settings; on detach it is removed again.

Why

Long-running project-thread children can compact on their own instead of running into the context limit. Because values passed with --settings override the same keys in your settings files, such a child can run with auto-compact on even if you turned it off in your own settings; it is left alone only when flag settings already set autoCompactEnabled.

Read from
Names in the bundleautoCompact--settings
What the documentation says
Since it was published

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.

Confirmed since Anthropic's documentation has since written up --settings, on Manage multiple agents with agent view. Agent view accepts the same configuration flags as `claude` for loading settings, plugins, MCP servers, and additional directories. Agent view applies `--settings`, `--setting-sources`, and `--plugin-dir` to itself and passes every configu… agent-view see the edit
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 doubtWhich kind of launched session this applies to (remote, teleported or background) is not confirmed.
Anthropic's documentation agreesAnthropic's documentation has since written up --settings, on Manage multiple agents with agent view.
Anthropic's release notes agreeChanged sandbox.excludedCommands to ignore project and local settings entries when managed settings or --settings set…

See this entry in the whole of v2.1.282 →

Feedback