Execution Environment
Keep Panda inside your project folder, so it cannot read the rest of your computer.
Feature Updated 20 Nov 2026Applies to new chats
A change here takes effect in the next chat you start. Chats that are already open keep the environment they started with.
What the Execution Environment is
Panda works through an engine, such as Claude Code, Codex or OpenCode, that runs on your computer. By default that engine can reach every file your user account can. The Limited environment fences it in: it sees your project and the folders you allow, and nothing else. Turn it on for a project you do not fully trust, or to keep Panda away from things like your mail, browser profiles and keys.
Where to find it
Open Settings and pick Execution Environment. Turn on Limited environment. The rest of the options appear once it is on.
Which folders it can reach
Always Allowed lists what Panda can always reach, because it needs these to work. They are your project folder, the PandaOS app data in ~/.pandaos, and each engine's own settings (~/.claude, ~/.claude.json, ~/.opencode, ~/.config/opencode, ~/.codex). The temporary folders /tmp and /private/tmp are there too.
Access Presets add folders that common tools need. The first three are on from the start.
| Preset | Needed for |
|---|---|
| Git SSH Keys | git push and pull over SSH |
| npm / Node Cache | npm install, npx |
| Homebrew | Homebrew-installed tools |
| AWS Credentials | AWS CLI and SDK |
| GPG Keys | Signed git commits |
| Docker Config | Docker commands |
| Python / pip Cache | pip install, virtual environments |
| Rust / Cargo | Rust builds |
Custom Paths adds any other folder. Panda can read and write it.
What app tools it can use
A fence around your files would not help if Panda could export a secret through a connected app. MCP capability tier limits the app tools a Limited chat gets. MCP is the standard way apps hand Panda their tools.
| Tier | What it allows |
|---|---|
| Project-scoped | Blocks tools that dump credentials or platform secrets. This is where it starts. |
| Read-only | Only tools that read or search |
| Full | All app tools. Not recommended together with a Limited environment. |
The built-in browser is off in a Limited chat, because it could reach files the fence keeps out.
Network
Network decides what Panda can reach on the internet: Full (default), Localhost only or Off. Localhost only can break npm install and calls to online services. On Windows, Localhost only still allows the full network.
How each system enforces it
Where the operating system can lock a program in, PandaOS uses that. Where it cannot, PandaOS still checks every path and still limits the app tools.
| System | How it is enforced |
|---|---|
| macOS | The system sandbox (sandbox-exec) wraps the engine |
| Linux | bubblewrap when it is installed, otherwise PandaOS's own path checks |
| Windows | The Windows sandbox once you press Set up elevated sandbox under Platform, otherwise PandaOS's own path checks |
Automations always run Limited
An automation started by a schedule or a webhook runs in the Limited environment even when the switch is off. Its app tools are capped at Project-scoped. A run nobody is watching cannot reach your whole computer. See Unattended runs.
Limits
- The setting is the same for every project. A per-project setting is not available.
- Your project folder stays fully open, including its
.envfiles. To decide which secrets Panda may read, use Credentials.