# How do I give every employee their own AI agent computer? > Build one team template with a network policy and secret proxies, then start one persistent Sanbox Computer per person with a stable external run ID. Enterprise adds SSO. - Source: Sanbox knowledge base, by Sanlabs GmbH - URL: https://sanbox.cloud/kb/teams/agent-computer-for-every-employee/ - Type: how-to - Section: Agents for teams - Language: en - Published: 2026-11-06 - Updated: 2026-11-06 Create one Sanbox template per team, with the agent, the model, a network policy and secret proxies for company APIs. Then start one Computer per person from it, each with a stable external run ID, so every employee gets a persistent machine with the same tools and the same limits. People use their Computer from the Sanbox console or the CLI, and stopping it overnight keeps their files and installed packages. The general alternative is a VM or VPS per person, which you then patch, firewall and back up yourself. ## Run this with your agent ```text Read https://sanbox.cloud/kb/teams/agent-computer-for-every-employee.md and follow it to create a team template and one Computer per person. If the Sanbox CLI is missing, install it with `npm install -g @sanlabs/sanbox-cli@latest` and sign in with `sanbox login`. Show me each command before you create, stop or delete a Computer. ``` ## What does the setup look like? - **One template per team or role.** It fixes the Computer type, the model, which hosts the agent may reach, and which company APIs it may call. - **One Computer per person.** Each is a Firecracker microVM with its own kernel and its own persistent disk. - **Keys stay outside.** Secret proxies add company API credentials to outgoing requests, so no employee's agent ever holds the key. - **One contract.** Sanbox processes data in EU data centres under an Article 28 GDPR data processing agreement with Sanlabs GmbH. Creating templates and secret proxies needs the organisation's owner or admin role. Starting and using Computers needs the Developer role or higher. ## 1. Pick the Computer type - **`opencode-computer`** for general work: OpenCode, plus Python, LibreOffice Writer and Calc, and document libraries. - **`browser-computer`** for work in websites: OpenCode with a managed browser that people can watch and take over. - **`hermes-computer`** for a personal assistant with memory, skills, an email inbox and Telegram. - **`docker-computer`** for engineers who need Docker and Compose. It has no agent. ## 2. Write the team's network policy Outbound traffic is denied unless a rule allows it. List only what the team needs: ```json { "default_action": "deny", "rules": [ { "destination": "api.github.com", "ports": [{ "from": 443, "to": 443 }] }, { "destination": "registry.npmjs.org", "ports": [{ "from": 443, "to": 443 }] } ] } ``` Save it as `policy.json`. The template's model provider is reached without a rule of your own. ## 3. Put company API keys in secret proxies Save the proxy settings, without the key, as `proxy.json`: ```json { "name": "crm-api", "host": "api.crm.example.com", "authentication": { "type": "bearer" }, "attach_run_id": false } ``` Then pass the key on stdin from a private file outside the repository: ```bash sanbox secret-proxies create --file proxy.json --secret-stdin --all-paths --json < /private/path/crm-token ``` Use `--path /accounts` (repeatable) instead of `--all-paths` to limit the key to parts of the API. When the key changes, replace it with `sanbox secret-proxies rotate crm-api --secret-stdin --json < /private/path/new-token`. ## 4. Create the team template ```bash sanbox model-providers list --json sanbox templates create --name "Sales team" --type opencode-computer \ --model-provider --model \ --network-policy policy.json \ --secret-proxy crm-api --add-network-access --json sanbox templates validate --json ``` `--add-network-access` adds an HTTPS rule for the proxy's host. To give everyone a larger disk, up to 8 GB: ```bash sanbox templates storage set --gb 8 --json ``` ## 5. Start one Computer per person Give each person's Computer an external run ID that names them. Running the same command again returns the existing Computer instead of creating a second one: ```bash for person in anna ben chiara; do sanbox run --template --external-run-id "sales-$person" --json done ``` List the team's Computers with `sanbox runs list --limit 50 --json`. ## How do people reach their Computer? - **The console.** At [console.sanbox.cloud](https://console.sanbox.cloud), people open their Computer, chat with the agent and use the browser terminal. - **The CLI.** After `sanbox login`, `sanbox ssh ` opens a private shell, and `sanbox cp` copies files in and out. - **Their own coding agent.** `sanbox skill --write` saves the agent guide to `.sanbox/agent.md`, so Claude Code or Codex on a laptop can drive the CLI. ## What happens when someone stops their Computer? Computers stay on until someone stops them; nothing puts them to sleep. Stopping saves the disk, including `/workspace` and installed packages, and ends compute. Resuming boots the Computer fresh with that disk: ```bash sanbox runs stop --wait --json sanbox runs resume --wait --json ``` Running programs and open connections don't survive a stop, so ask people to save their work first. ## Snapshot it Set one Computer up the way the team likes it: tools installed, settings in place. Stop it and make it the starting point for everyone: ```bash sanbox snapshots create --run --name sales-base --wait sanbox templates create --name "Sales team v2" --snapshot sales-base \ --network-policy policy.json --secret-proxy crm-api --add-network-access --json ``` Every new Computer from that template starts as a copy of the snapshot. To roll out a newer setup, snapshot again and point the template at it with `sanbox templates update --snapshot `. Existing Computers keep what they started with. ## How do we get started? Sanbox is priced per organisation. Enterprise plans include SSO and custom identity integrations, and deployment in your VPCs. Our [forward-deployed engineers](https://sanbox.cloud/kb/teams/forward-deployed-engineering/) can set up the team template, connect your company systems and build the first use cases with your team. [Talk to us](mailto:sales@sanlabs.ai?subject=Sanbox%20for%20teams). For your vendor review, the data processing agreement, the sub-processor list and the technical and organisational measures are available from support@sanlabs.ai. ## What this doesn't do - **Privacy between colleagues.** Templates separate tools and settings, not people. For Computers that colleagues mustn't open, talk to us about how to separate them. - **Per-team spend caps.** These are enabled on request. See [See and cap what each AI agent spends](https://sanbox.cloud/kb/teams/spend-caps-per-computer-and-team/). - **Slack or Teams.** Triggers from Slack, Microsoft Teams and WhatsApp are enabled on request. See [Trigger an AI agent from Slack, Microsoft Teams or WhatsApp](https://sanbox.cloud/kb/teams/trigger-an-agent-from-slack-teams-or-whatsapp/). - **Windows or GPUs.** Computers run Linux on CPUs. - **Big disks.** Each Computer has 1 to 8 GB of disk. - **Models.** You bring your own model provider and key. Sanbox doesn't sell models. ## Related - [How do I give an AI agent API keys without exposing them?](https://sanbox.cloud/kb/security/api-keys-your-agent-cannot-see/) - [How do I restrict which domains an AI agent can reach?](https://sanbox.cloud/kb/security/restrict-which-domains-an-agent-can-reach/) - [Can an AI agent create Word, Excel and PDF files in the cloud?](https://sanbox.cloud/kb/teams/agents-that-write-word-excel-and-pdf/) - [Trigger an AI agent from Slack, Microsoft Teams or WhatsApp](https://sanbox.cloud/kb/teams/trigger-an-agent-from-slack-teams-or-whatsapp/) - [Do I need a DPA for AI agents?](https://sanbox.cloud/kb/eu/dpa-for-ai-agents/) ## Next step Talk to us at sales@sanlabs.ai. Sanlabs' forward-deployed engineers build agent use cases with your team, with experience in aviation, pharmaceuticals, supply chain and logistics, and internal admin workflows. How we work: https://sanbox.cloud/kb/teams/forward-deployed-engineering.md Existing customers can use Sanbox from a coding agent: install the CLI with `npm install -g @sanlabs/sanbox-cli@latest`, sign in with `sanbox login`, then run `sanbox skill` for the full agent guide.