Unclear It is not confirmed whether these launch settings or your own settings file win when they disagree.
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 switchtengu_bridge_rc_child_auto_compactis on. Its built-in fallback is on; nothing has been read about it. - That role now grants
autoCompact, next todefaultMode: "auto"in the settings generated for the child. - When a session is launched, the
--settingsJSON now passesautoCompactalongsideautoOverSettingsandautoModeEnvironment, and includesautoCompactEnabled: truewhen 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.
tengu_bridge_rc_child_auto_compact Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.282: 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.
Read once, for one account on one subscription tier, against v2.1.282. It isn't a statement about your account. What a flag value here can and cannot tell you
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.
<div><code>claude agents</code> gained dispatch flags (`--add-dir`, `--settings`, `--mcp-config`, `--plugin-dir`, `--permission-mode`, `--model`, `--effort`, `--dangerously-skip-permissions`) to configure background sessions, and `claude a…whats-new/2026-w20 see the edit
| [`autoCompactEnabled`](#autocompactenabled) | Turn [automatic compaction](/docs/en/context-window) off or on | Memory and context | Any file |settings-reference see the edit
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
It is not confirmed whether these launch settings or your own settings file win when they disagree.
Anthropic's documentation has since written up --settings, on Manage multiple agents with agent view.
Changed sandbox.excludedCommands to ignore project and local settings entries when managed settings or --settings set…
New in this build: tengu_bridge_rc_child_auto_compact