Sandbox and internet access
Admin → Sandbox
What the sandbox is
Section titled “What the sandbox is”When Lucy runs code to analyse data or build a file, it does so in a sandbox: a short-lived virtual machine with its own kernel, one per conversation. It has no route to your network, other tenants or other conversations, and no secrets are placed in it. This is your strongest guard against a misbehaving prompt or a malicious file.
Internet access
Section titled “Internet access”| Option | What code may reach | Choose it when |
|---|---|---|
| No internet | Nothing outside the sandbox | Confidential data, strictest policy. Lucy still analyses and builds files from what you provide. |
| Only some domains | Only the domains you list (wildcards allowed, for example *.example.org) |
Lucy needs a package index or one data source |
| The internet | Anything public | Research and prototyping where data is not sensitive |
Why it matters. Network access is how data can leave. With No internet, code run for a person cannot send their data anywhere, even if instructed to by a malicious document.
Resting
Section titled “Resting”When a sandbox rests sets how many idle minutes (1 to 120, default 5) before the sandbox is paused. Its workspace is saved and the machine is stopped, which frees resources. The next message restores it.
- Shorter: less idle compute, less time anything stays running.
- Longer: faster return to a long-running job.
Saved data
Section titled “Saved data”The same page sets retention for saved workspaces and published pages.
Entitlement
Section titled “Entitlement”Running code is part of your contract (sandbox). If it is not in your plan, Lucy still chats and reads documents but cannot run code.
Examples
Section titled “Examples”Confidential client data
Section titled “Confidential client data”Situation: Analysts process client portfolios that must not leave the platform. Setup: No internet, saved workspace 7 days. Result: Lucy still reads files, runs analysis and builds documents. Code run for a person cannot send data anywhere.
An analysis that needs one data source
Section titled “An analysis that needs one data source”Situation: The team needs a public rates feed. Setup: Only some domains with the one host. Result: Code can fetch the feed. Everything else stays blocked.
Idle time
Section titled “Idle time”Situation: Heavy users complain that the sandbox keeps restarting. Finance asks about idle compute. Setup: Idle time 15 minutes instead of 5. Result: Fewer restarts for people who step away briefly, with a bounded cost.