Claude Code /sandbox: Safely Test Risky Commands in an Isolated Space

Have you ever frozen up thinking "if I run this command wrong, won't something get deleted or broken?" /sandbox is a command that turns isolated execution mode on and off. It lets you try potentially risky work in a safe space separated from your real environment.

Definition (what it is)

/sandbox is a command that toggles (switches on and off) sandbox (isolated execution) mode. Note that it only works in environments that support this feature.

A sandbox is an isolated space, like a literal sandbox, separated from your real system. When you run a command inside it, whatever happens has no effect on the real files or system outside. That lets you freely test commands that could be troublesome if they go wrong. Because it deals with safety and permissions, it's classified as intermediate or above.

How to use it (by level)

Basic — Turn isolated execution on and off

Type this in the input box.

/sandbox

This command is a toggle, so typing it once turns it on and typing it again turns it off. While it's on, execution happens in the isolated space, protecting your real environment.

Common pitfalls

• It only works in "supported environments." If your environment doesn't support a sandbox, it may not turn on.
• The isolated space being separated from the real environment is both a strength and a limitation. Results created inside the sandbox may not remain in the real environment as-is, so distinguish between work you truly want reflected and work you're only testing.
• Because it's a toggle, it's easy to lose track of whether it's currently on or off. Build the habit of checking the current state before you work.

Real-world example

It fits well when testing a command you're using for the first time, or work that might delete files or touch the system. Isolate it with /sandbox and run it; even if a mistake happens, the real environment stays intact, so you can check the result with peace of mind.

Taking it further

It's also useful when reviewing an unfamiliar script or a command someone handed you. Running it in the sandbox first to observe what happens, before running it in the real environment, lets you move on to the actual work with confidence. Pairing it with permission-setting features as a safety net makes it even more reassuring.

Wrap-up

/sandbox is a command that turns isolated execution mode on and off (in supported environments only). It's reassuring that you can test potentially risky work in a safe space separated from the real environment. Since it's a toggle, it's best to use it while checking whether it's currently on or off.

Based on Claude Code v2.1.154 (2026.05)