העמוד הזה עוד לא תורגם; מוצגת הגרסה באנגלית.

בטא בקרוב. הפיצ׳ר עדיין בפיתוח, ולכן שמות ופרטים עשויים להשתנות לפני השחרור.

Sandbox & approvals

Decide how far an agent may go on its own. A sandbox sets what the agent may do without asking (read only, write in the project, or anything), and an approvals setting decides what happens when it wants to go further: ask you, refuse, or let a cheap model check the risk first.

Pick a preset

Click the pill in the composer bar, next to the model (it reads Workspace · Ask by default), or run Agents: Agent Sandbox and Approvals… (⌘⌥⇧S, Ctrl+Alt+Shift+S).

Sandbox

PresetInside the sandboxLeaves the sandbox
Read-onlyreading the projectedits, commands that change files, the network
Workspace write (default)edits and commands in the projectwrites outside the project, the network
Full accessany file, any command, the networknothing (changes to the policy file still ask)

With Workspace write, the Network access checkbox lets commands download and call remote hosts without asking. It is off by default.

Approvals

PresetWhen something leaves the sandbox
Ask (default)it waits for Run on an approval card
Never askit is refused, and the agent is told why so it can work inside the sandbox
Auto-reviewa cheap model checks the risk first: low risk runs, the rest asks you

The choice is saved for the project in .ingot/policy.json:

{
  "preset": { "sandbox": "workspace-write", "approvals": "auto-review", "network": false }
}

What leaves the sandbox

Ingot checks every tool call before it runs:

The agent wants to…Examples
change filesan edit, rm, mv, mkdir, > redirects, git commit
write outside the projectcp build ~/Desktop, sudo …, a working folder outside the project
use the networkcurl, npm install, git push, pip install, docker pull, web search, opening a non-local page
change the sandbox policyediting .ingot/policy.json

Read-only commands such as ls, cat, grep, git status or git diff never leave the sandbox. Writes to /tmp don't count as outside the project.

An action that leaves the sandbox shows the reason on its approval card, for example Outside the sandbox: uses the network, with Run and Skip only (no Always Run).

Auto-review

With Auto-review, each action that would need your OK is sent to a small, cheap model first. It answers low or high risk:

  • Low risk (reads, builds, tests, installing well-known packages, writing inside the project) runs, with a note in the chat: Auto-review: low risk, running: npm test.
  • High risk (deleting or overwriting data outside the project, sending code or secrets to remote hosts, installing unknown software, force-pushing, anything hard to undo) asks you.
  • If the model is unsure, unreachable, or the chat has used its 20 checks, you're asked.

The reviewer is the model in the ingot.agent.reviewModel setting, or else a cheap connected model such as Ingot Fast. Set it in settings.json.

Network off

With the network off, Ingot starts commands with proxy variables that point nowhere and npm_config_offline=true, so package managers and most tools fail fast instead of reaching out. Programs that ignore proxy settings aren't stopped by this; for a hard block on macOS and Linux, see the network rules in Agent policy & audit log and the Agent Sandbox.

Tools from MCP servers aren't checked by the preset; they keep their own approval cards. With Never ask they run without a card, so remove MCP servers you don't trust.