Sweep 19 Sep 2026 · 02:36Z Build v2.1.278 500 read Stable v2.1.267 Latest v2.1.278 Next v2.1.278 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.260 ·

Unreadable-settings error now covers sandbox settings too, and points to /status

Unreadable-settings warnings now cover sandbox settings and point to /status.

TierYou'll noticehow much it should matter to you
Useful1my rating, 1 to 5
Signal1worth watching, 1 to 5
AreaSettingswhat it touches
KindImprovementsin v2.1.260,
You'll notice

Unreadable-settings warnings now cover sandbox settings and point to /status.

The warning shown when a settings file has errors during a teleport/cloud-session bundle now also covers sandbox settings, not just Read rules, and lists which specific settings files could not be read.

Read from
Names in the bundle/status
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.

Added since A small documentation edit on Recommend your plugin from your CLI touched a line naming /status after this was published. * `CLAUDE_CODE_CHILD_SESSION`: set only in subprocesses Claude Code itself spawns, such as tool calls, hook commands, and [status line](/docs/en/statusline) commands, so the tag does not normally reach a human terminal. A long-lived proces… plugin-hints see the edit
Confirmed since Anthropic's documentation has since written up /status, on Claude Code on Amazon Bedrock. Run `/status` to see the resolved region. When the region came from your AWS config files or the default fallback, Claude Code also notes the source in the `/status` output. amazon-bedrock see the edit
How sure we are
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up /status, on Claude Code on Amazon Bedrock.
Anthropic's release notes agreeFixed /status listing a signed-in claude.ai account and a configured API key as if both were in effect; the credential not in use is now…

See this entry in the whole of v2.1.260 →