OkayTeacher
EN English 한국어 日本語 中文 हिन्दी বাংলা اردو Español Português Français Deutsch Русский العربية Bahasa Indonesia Tiếng Việt ไทย Türkçe

How to enable notifications

Notifications are unavailable in this browser or on this address. Try a supported browser on the secure SONUB site.

If notifications are blocked, allow them in your browser settings.

  1. Open the site controls beside the address bar, or your browser’s site settings. Set Notifications for this site to Allow.
  2. In your device settings, allow notifications for your browser and check Do Not Disturb or Focus.
  3. Return to SONUB, reload the page, and use the bell to enable notifications.

On iPhone or iPad, add SONUB to your Home Screen, open it there, then allow notifications.

Glossary · Learn more

Sandboxing

Fencing in the files and that commands can reach. See what it is, how it works, how it is used and what to watch for, with pictures and examples.

A robot playing inside a round purple fence with one narrow gate, showing commands kept inside a set boundary.

What it is

Sandboxing puts a fence around the commands runs, and the itself guards that fence. You decide which folders the commands can write to and which domains they can reach. By default, commands can write only in the working folder, a temp folder and folders you added, and network traffic goes through a whose allowed-domain list starts empty. Because the operating system holds the fence even if a command does more than its name suggests, can run sandboxed commands without asking you each time. It works on , and WSL2, and it is off until you turn it on.

How it works

  1. Run /sandbox in a session
  2. Pick auto-allow or regular
  3. Commands run inside the fence
  4. Approve new network domains when asked

How to use it

  1. /sandbox

    opens the sandbox panel with Mode, Overrides and Config tabs.

  2. sandbox.enabled set to true in ~/.claude/settings.json

    turns the sandbox on for all your projects.

  3. sandbox.network.allowedDomains

    the domains Bash commands may reach. sandbox.filesystem.allowWrite adds folders they may write to.

  4. "allowUnsandboxedCommands": false

    strict sandbox mode. Claude can no longer retry a failed command outside the sandbox.

Watch out

The sandbox covers shell commands only. Claude's Read, Edit and WebFetch tools, and hooks run outside it and follow permission rules instead, which are a separate layer. It is also not the same as auto mode, and it is not a complete wall — allowing a broad like github.com can open a path for to leak, and if the sandbox can't start, commands run unsandboxed unless you set sandbox.failIfUnavailable.

Original and official docs

This page explains the term in plain words. The original is the authority: if they differ, follow the original.