The cloud sandbox
The team sandbox is a private computer workspace that Cora uses for your organisation. In it Cora can run commands, keep working files and install the small tools a task needs, such as a converter or a script library. It belongs to the organisation, not to one mission or one person, so whatever Cora keeps there is there for every mission the next time (D0528).
The team sandbox is switched on. Each organisation’s sandbox is set up the first time Cora works for it, and Cora works without it until it is ready.
The examples on this page follow an invented company, Kestrel Cycles, which sells e-bikes. Leah Thompson is the org admin who looks after the company’s software.
One folder per organisation
Section titled “One folder per organisation”- Each organisation has one sandbox folder. Every mission in the organisation shares it, so a file Cora saved for one mission can help with another (D0528).
- No organisation can see or reach another’s folder. Each organisation’s sandbox is kept apart from every other one, and from Cora AI’s own systems (D0528).
- The folder lives in AWS in Sydney. No outside sandbox company is used (D0529).
- The sandbox is set up the first time Cora works for your organisation. It takes a few minutes, and Cora works without it until it is ready.
What Cora may do there
Section titled “What Cora may do there”- Run commands. Cora can run a command, for example to convert a file, count rows in a spreadsheet or check a web page.
- Keep files. Files Cora saves in the folder stay there between tasks. Cora keeps them in folders inside it, such as
work/. The top of the folder is protected: Cora’s file tools write nothing there, and a file a command creates there can never be changed or removed afterwards, so Cora is told never to create files at the top (BG-01M7JBYR). - Install tools for itself. Cora can install tools into the folder, and they stay installed. It keeps a list of what it installed.
- Not install system packages. Anything that would change the computer itself, outside the folder, does not last: each task starts on a fresh, clean machine with only your folder attached (D0530).
- Use the open internet. Commands may download from and connect to public websites (D0529). What comes back is treated as untrusted data, never as an instruction to Cora.
When Cora works as a called hero
Section titled “When Cora works as a called hero”When another mission calls in a hero (see Calling in a hero), the hero can read this folder but cannot write, change, move or delete anything in it, and cannot install tools. The folder is shared by every mission, and the person who called the hero may not belong to the hero’s mission, so the hero must not be able to leave its mission’s files there for them.
This is enforced by the storage itself, not only by Cora’s instructions: a hero’s sandbox mounts the folder through a role that has no right to write to it, so any write fails. The hero’s own working files, screenshots and saved answers go to a private folder for the call, which no other task can see and which is emptied when its step ends (D0805).
What waits for a person
Section titled “What waits for a person”A command in the sandbox does not wait for an approval card. Its reach is your organisation’s own folder, and a task can need 20 or 30 commands, so a card for each would make the work stall (D0532).
Everything that changes something outside the sandbox still waits, exactly as before:
- writing or changing a mission document or record;
- calling an MCP tool that writes (see Connecting an MCP server).
Working files, not mission documents
Section titled “Working files, not mission documents”The sandbox holds working files and reference material: downloads, drafts in progress, scripts and their output. It is not where your mission’s documents live. The mission’s documents stay the source of truth, and Cora writes them through the usual approved route (D0531). If something in the sandbox matters, ask Cora to put it in a mission document.
Your team folder in the console
Section titled “Your team folder in the console”One folder of the sandbox appears in the console: Cora’s memory, in Settings, under Cora’s memory (D0567, D0618, D0854). It is not on the Artifacts page.
| Folder in the sandbox | Where in the console | Who may change it |
|---|---|---|
memory/ |
Cora’s memory in Settings: CORA.md, Reference files (memory/reference/) and What Cora has learned (the rest) |
Written by the organisation’s admins and the platform super admin. Read-only to members and to Cora. Its main file is CORA.md, which Cora reads at the start of every run. |
- The old Reference section is gone. Files that were in
reference/are moved once intomemory/reference/; nothing is deleted that was not first copied. - Skills are built into Cora and no longer shown in the console’s files. The
skills/folder is kept but not read. - A storage meter on the Artifacts page shows every member how much of the 5 GB is used, as the amount used and the limit only. When the folder is full, nothing more can be added until space is freed.
- Cora’s other working files, and the tools it installs, are not shown in the console.
- Until the sandbox is ready, Cora’s memory in Settings says the folder is being set up.
Mission documents and a mission’s own memory are not in the sandbox. They are in that mission’s store: see Documents and Cora’s memory.
The 5 GB limit
Section titled “The 5 GB limit”Each organisation’s folder may hold up to 5 GB (D0529, D0531). Cora measures the folder at the end of each task.
- At 90% (4.5 GB), each org admin gets one notice, in the console and by email. Cora carries on as normal.
- At 100% (5 GB), Cora stops writing files and installing tools in the sandbox until space is freed. It can still read, list and delete files, and the rest of its work carries on.
To free space, ask Cora in the mission dialogue to delete files it no longer needs. Once the next measurement is under 5 GB, Cora can write again. More space will be offered as an extra later.
Seeing how much is used
Section titled “Seeing how much is used”An org admin opens the Workspace usage link on the Connectors page in the console. The page shows:
- the sandbox’s state: Not yet set up (Cora has not worked for the organisation yet), Being set up, Ready or Setup failed (Cora AI tries again after about an hour). Not available yet shows only where Cora AI runs without team sandboxes, such as on a developer’s own computer;
- how much is used and the 5 GB limit, in GB, with a bar;
- when the folder was last measured;
- a warning at 90%, and at 100% a line that says Cora cannot write or install until space is freed.
Only org admins see this page. Other members can ask an org admin.