Unclear Which variables cannot be passed into the sandbox is not stated.
On Windows, commands run inside the sandbox (a walled-off space that limits what a command can reach) now receive the environment variables you set in your settings or with /env. Environment variables are named values a program reads when it starts. Any that cannot be passed are logged with the message "these variables from settings or /env are not passed to the sandboxed command".
If setting up the sandbox for a command is cancelled, the command now stops before it starts, and Claude Code logs tengu_shell_abort_before_spawn.
If you use the sandbox on Windows, variables from your settings may now reach your sandboxed commands where they did not before, and some may still be left out. Check the log if a command is missing one.
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.
Descriptions and instructions from some of the MCP servers that Anthropic hosts at `api.anthropic.com` reach Claude in full. To change the limits for the other MCP servers in your session, set [`CLAUDE_CODE_MAX_MCP_DESCRIPTION_LENGTH`](/do…mcp see the edit
| `POST` | `/v1/environments` | `CreateEnvironment` | Data |api/claude-platform-on-aws-iam-actions see the edit
Which variables cannot be passed into the sandbox is not stated.
Anthropic's documentation has since written up /env, on claude-platform-on-aws-iam-actions.