Sandbox mode is switched off through the Cursor CLI's interactive sandbox menu to get one stubborn build working. What state is that setting in the next time the CLI starts?

Easycursorcursor-clisandboxsecurity

Last reviewed 21 Aug 2026

It is still off for that project directory, while any other directory starts each new session fully sandboxed again.
It returns to the sandboxed default, since the menu applies to the current session only and resets on exit.
It is still off, but network access is restored to its safe default, because those two toggles are stored separately.
It is still off, because the sandbox and network choices made in that menu persist across sessions until changed.Correct answer

Show answer & explanation

Correct answer: D. It is still off, because the sandbox and network choices made in that menu persist across sessions until changed.

Explanation

The principle — The CLI's sandbox controls are a persistent setting, rather than a per-session choice.

Why the key is correct — The sandbox menu toggles sandboxing on or off and controls network access, and those settings persist across sessions. Turning it off once to get a build through leaves it off for every later session, so commands keep running unsandboxed until someone switches it back.

Why the others are wrong — There is no automatic reset to a safe default on exit, and that assumption is what makes this dangerous. The setting is also not scoped to one project directory. And the sandbox toggle and the network toggle are not restored independently at the next start, because both stay where you left them.

Remember this — If you disable the sandbox for one stubborn command, turn it back on straight afterwards.

Sources — Cursor's CLI overview documentation.

Sources

Primary sourceCursor CLI — Cursor · accessed 19 Aug 2026
“Toggle sandbox mode on or off and control network access through an interactive menu.”

Practise 10 questions on this topic

Take Cursor Basics — Timed Test 1 (10 questions) — scored instantly, explanation for every question, no login.

Start the test

Sandbox mode is switched off through the Cursor CLI's interactive sandbox menu to get one stubborn build working. What state is that setting in the next time the CLI starts?

Easycursorcursor-clisandboxsecurity

Last reviewed 21 Aug 2026

It is still off for that project directory, while any other directory starts each new session fully sandboxed again.
It returns to the sandboxed default, since the menu applies to the current session only and resets on exit.
It is still off, but network access is restored to its safe default, because those two toggles are stored separately.
It is still off, because the sandbox and network choices made in that menu persist across sessions until changed.Correct answer

Show answer & explanation

Correct answer: D. It is still off, because the sandbox and network choices made in that menu persist across sessions until changed.

Explanation

The principle — The CLI's sandbox controls are a persistent setting, rather than a per-session choice.

Remember this — If you disable the sandbox for one stubborn command, turn it back on straight afterwards.

Sources — Cursor's CLI overview documentation.

Sources

Primary sourceCursor CLI — Cursor · accessed 19 Aug 2026
“Toggle sandbox mode on or off and control network access through an interactive menu.”

Practise 10 questions on this topic

Take Cursor Basics — Timed Test 1 (10 questions) — scored instantly, explanation for every question, no login.

Start the test

Sandbox mode is switched off through the Cursor CLI's interactive sandbox menu to get one stubborn build working. What state is that setting in the next time the CLI starts?

Related questions

Sandbox mode is switched off through the Cursor CLI's interactive sandbox menu to get one stubborn build working. What state is that setting in the next time the CLI starts?

Related questions