[BUG] No sandbox warning in terminal

Open 💬 0 comments Opened Jun 16, 2026 by rdeago

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

When claude starts with the sandbox enabled (either via configuration, command-line parameters, or a previous /sandbox command), Claude Code no longer displays a warning/notice at startup indicating that the sandbox is active.

Up to and including v2.1.175, a warning was shown whenever the sandbox was enabled. As of v2.1.178, this warning is gone.

This removes the only user-visible signal that the sandbox is in effect.

What Should Happen?

When the sandbox is enabled (regardless of how — CLI flags, settings, or managed config), Claude Code should surface a clear indication that the sandbox is active, as it did up to v2.1.175.

Error Messages/Logs

Steps to Reproduce

  1. Launch Claude Code with the sandbox enabled via command-line parameters:

``bash
claude --settings='{"sandbox":{"enabled":true}}'
``

  1. Observe the startup output:
  • v2.1.175 and earlier: a warning indicating the sandbox is enabled is displayed.
  • v2.1.178: no such warning appears.

Claude Model

Not sure / Multiple models

Is this a regression?

Yes, this worked in a previous version

Last Working Version

2.1.175

Claude Code Version

2.1.178

Platform

Anthropic API

Operating System

Ubuntu/Debian Linux

Terminal/Shell

WSL (Windows Subsystem for Linux)

Additional Information

<img width="2098" height="999" alt="Image" src="https://github.com/user-attachments/assets/c52098bf-0e7d-4d57-9178-e2b21bb875af" />

View original on GitHub ↗