Answer: Match your goal to the table row: for unattended runs with `--dangerously-skip-permissions` or auto mode, start with the preconfigured dev container, any container or VM, or the sandbox runtime; to isolate MCP servers and hooks as well as Bash without Docker, use the sandbox runtime; and to reduce permission prompts during everyday work on your own machine, use the sandboxed Bash tool in auto-allow mode configured with `/sandbox`. Status: Confirmed Entry: tool/claude-code/permissions-and-security/choose-sandbox-for-threat-model Revision: 3 Digest: sha256:7781cd4692024cb0 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:05:32Z Last changed: 2026-11-20T12:24:33Z (native Windows host: — → A container or VM, or run the Bash sandbox inside WSL2) Last verified: 2026-11-20T12:24:33Z Next check: 2026-11-21T12:24:33Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of isolate MCP servers and hooks | The sandbox runtime | [1] | 2026-11-20 everyday work on own machine | The [sandboxed Bash tool](https://code.claude.com/docs/en/sandboxing.md) in auto-allow mode, configured with `/sandbox` | [1] | 2026-11-20 team standardization | The preconfigured [dev container](https://code.claude.com/docs/en/devcontainer.md), copied into your repository | [1] | 2026-11-20 no local setup | A [cloud session](https://code.claude.com/docs/en/claude-code-on-the-web.md), which requires a Claude subscription, and a connected GitHub account to clone a GitHub repository | [1] | 2026-11-20 organization-wide isolation | [Enforce isolation across an organization](#enforce-isolation-across-an-organization) | [1] | 2026-11-20 native Windows host | A container or VM, or run the Bash sandbox inside WSL2 | [1] | 2026-11-20 Sources: [1] Anthropic. "Choose a sandbox environment". https://code.claude.com/docs/en/sandbox-environments.md Role: primary. Accessed: 2026-11-20T12:24:33Z Quote: "Isolate MCP servers and hooks as well as Bash, without Docker | The sandbox runtime" (Supports: isolate MCP servers and hooks) Quote: "Reduce permission prompts during everyday work on your own machine | The [sandboxed Bash tool](https://code.claude.com/docs/en/sandboxing.md) in auto-allow mode, configured with `/sandbox`" (Supports: everyday work on own machine) Quote: "Standardize a sandboxed environment across a team | The preconfigured [dev container](https://code.claude.com/docs/en/devcontainer.md), copied into your repository" (Supports: team standardization) Quote: "Use Claude Code from a device with no local setup | A [cloud session](https://code.claude.com/docs/en/claude-code-on-the-web.md), which requires a Claude subscription, and a connected GitHub account to clone a GitHub repository" (Supports: no local setup) Quote: "Require isolation for every developer in your organization | [Enforce isolation across an organization](#enforce-isolation-across-an-organization)" (Supports: organization-wide isolation) Quote: "Work on a native Windows host | A container or VM, or run the Bash sandbox inside WSL2" (Supports: native Windows host) Published: 2026-11-20T03:41:01Z Snapshot SHA-256: f3c482d1ba678403dfa26c1595e08c9a380a880d27dcb50e583d0f201e579aff (captured 2026-11-20T12:24:32Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. Cross-check: not-available at 2026-11-20T12:24:33Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:24:33Z Last attempt: 2026-11-20T12:24:33Z Notes and limitations: Extracted automatically from a single official source (section "Choose an approach"). Related: https://latestn.com/tool/claude-code/permissions-and-security/cloud-network-access-levels What network access levels can I choose for a Claude Code cloud environment and how do I allow specific domains? https://latestn.com/tool/claude-code/permissions-and-security/compare-sandbox-approaches Which sandbox environment options does Claude Code offer and how do they compare? https://latestn.com/tool/claude-code/permissions-and-security/configure-proxy-for-credentials How do I configure Claude Code to use a proxy for credential management? https://latestn.com/tool/claude-code/permissions-and-security/built-in-security-features What built-in security features does Claude Code have? https://latestn.com/tool/claude-code/permissions-and-security/change-permission-mode How do I change the permission mode for a Claude Code SDK agent? https://latestn.com/tool/claude-code/permissions-and-security/change-permission-mode-2 How do I change the permission mode in Claude Code? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-20T12:24:33Z | changed | native Windows host: — → A container or VM, or run the Bash sandbox inside WSL2 | [1] 2026-11-20T12:24:33Z | changed | organization-wide isolation: — → [Enforce isolation across an organization](#enforce-isolation-across-an-organization) | [1] 2026-11-20T12:24:33Z | changed | no local setup: — → A [cloud session](https://code.claude.com/docs/en/claude-code-on-the-web.md), which requires a Claude subscription, and a connected GitHub account to clone a GitHub repository | [1] 2026-11-20T12:24:33Z | changed | team standardization: — → The preconfigured [dev container](https://code.claude.com/docs/en/devcontainer.md), copied into your repository | [1] 2026-11-20T12:24:33Z | changed | everyday work on own machine: — → The [sandboxed Bash tool](https://code.claude.com/docs/en/sandboxing.md) in auto-allow mode, configured with `/sandbox` | [1] 2026-11-20T12:24:33Z | changed | isolate MCP servers and hooks: — → The sandbox runtime | [1] 2026-11-20T12:24:33Z | changed | Bash tool limitation: constrains only shell commands → — | [1] 2026-11-20T12:24:33Z | changed | Native Windows host: A container or VM, or run the Bash sandbox inside WSL2 → — | [1] 2026-11-20T12:24:33Z | changed | No local setup: A [cloud session](https://code.claude.com/docs/en/claude-code-on-the-web.md), which requires a Claude subscription, and a connected GitHub account to clone a GitHub repository → — | [1] 2026-11-20T12:24:33Z | changed | Team standardization: The preconfigured [dev container](https://code.claude.com/docs/en/devcontainer.md), copied into your repository → — | [1] 2026-11-20T12:24:33Z | changed | Everyday permission prompts: The [sandboxed Bash tool](https://code.claude.com/docs/en/sandboxing.md) in auto-allow mode, configured with `/sandbox` → — | [1] 2026-11-20T12:24:33Z | changed | Isolate MCP servers and hooks: The sandbox runtime → — | [1] 2026-11-15T12:24:49Z | changed | Bash tool limitation: — → constrains only shell commands | [1] 2026-11-15T12:24:49Z | changed | Everyday permission prompts: — → The [sandboxed Bash tool](https://code.claude.com/docs/en/sandboxing.md) in auto-allow mode, configured with `/sandbox` | [1] 2026-11-15T12:24:49Z | changed | Isolate MCP servers and hooks: — → The sandbox runtime | [1] 2026-11-15T12:24:49Z | changed | Organization-wide isolation: [Enforce isolation across an organization](#enforce-isolation-across-an-organization) → — | [1] 2026-11-15T12:24:49Z | changed | Isolate MCP servers and hooks without Docker: The sandbox runtime → — | [1] 2026-11-15T12:24:49Z | changed | Unattended runs: The preconfigured [dev container](https://code.claude.com/docs/en/devcontainer.md), any container or VM, or the [sandbox runtime](#sandbox-runtime) → — | [1] 2026-11-13T03:05:32Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/claude-code/permissions-and-security/choose-sandbox-for-threat-model/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/claude-code/permissions-and-security/choose-sandbox-for-threat-model POST: https://latestn.com/dispute/tool/claude-code/permissions-and-security/choose-sandbox-for-threat-model with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/claude-code/permissions-and-security/choose-sandbox-for-threat-model?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I choose the right sandbox environment for my threat model in Claude Code? Revision 3, last verified 2026-11-20T12:24:33Z. https://latestn.com/tool/claude-code/permissions-and-security/choose-sandbox-for-threat-model (accessed 2026-11-21T10:07:54Z). @misc{LatestN_tool_claude_code_permissions_and_security_choose_sandbox_for_threat_model_r3, title = {How do I choose the right sandbox environment for my threat model in Claude Code?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/claude-code/permissions-and-security/choose-sandbox-for-threat-model}}, note = {Revision 3; digest sha256:7781cd4692024cb0; last verified 2026-11-20T12:24:33Z; accessed 2026-11-21T10:07:54Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/claude-code/permissions-and-security/choose-sandbox-for-threat-model