You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Agents ViewArea: what it touches
ImprovementsKind: in v2.1.299,
ImprovementsSection of the release
Unclear It is not clear what turns safe mode on.
What
--safe-mode is a flag (an option added when starting Claude Code) that starts it with your customizations switched off, which helps when a broken setting is causing trouble. Several things about it changed:
Agent list footer: the footer of the agents list now shows "safe mode" and "customizations are off" next to the waiting line. Before, only the waiting text appeared.
Restarts: --safe-mode is now one of the flags carried over when a background job or session restarts. The warning about flags dropped on restart now reads "stripped respawnFlags token(s) that a restart does not re-apply" instead of calling them "non-allowlisted", and the saved flags go through an extra clean-up step.
Exit hint: the hint telling you how to leave safe mode is now produced on the fly instead of always being the fixed text "restart without --safe-mode". Claude Code checks whether --safe-mode was on the command line, and the evidence includes the text "unset CLAUDE_CODE_SAFE_MODE", so the hint can point to the CLAUDE_CODE_SAFE_MODE environment variable as well. The matching hint for bare mode, which used to be the fixed text "restart without --bare", is built the same way.
Why
You can now see at a glance that a session is in safe mode, a background job started in safe mode stays in safe mode after it restarts, and the exit hint can reflect how safe mode was actually turned on.
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 doubtIt is not clear what turns safe mode on.
Anthropic's release notes agreeAdded a "safe mode" line to the agents view peek panel for background sessions started with --safe-mode