Self-hosted sandboxes
CloudThinker, on your own machine.
Keep using CloudThinker in your browser, on a laptop or a phone. Frontier Investigation Agents run in CloudThinker Cloud, and a Worker runs their files and shell commands in a folder you pick.
The Worker only connects out.
The Worker asks CloudThinker for work over HTTPS. Nothing connects in to your machine. There is no listener to run and no port to open.
Ask from anywhere. The work runs in your folder.
You keep using CloudThinker on the web, on a laptop or a phone. The Worker does the local part, and it only needs the cloudthinker CLI.
CloudThinker in a browser
On a laptop or a phone. Pick the Worker under Run in.
CloudThinker Cloud
Where the agent runs. The model, Connections like AWS or Kubernetes, and their credentials stay here.
Your Worker
A folder on your machine. It reads and edits files, runs shell commands, and follows your AGENTS.md and Skills.
Three steps, then pick it under Run in.
Your laptop, a server, or a CI runner.
Create a Worker
Open Admin settings, then Sandboxes, and give the Worker a name, like my-laptop.
Run one command in your folder
CloudThinker shows the command. The Worker passes its file, shell, cancellation, and artifact checks, then goes Online.
Pick it under Run in
In any chat, open +, choose Run in, and pick your Worker. CloudThinker now works in that folder.
Questions, answered.
Where does the agent run?
In CloudThinker Cloud. The Worker runs the file and shell work in its folder and sends the results back.
Do I need to open a port?
No. The Worker only makes outbound HTTPS requests to CloudThinker. Nothing connects in to your machine.
Can it still use my AWS or Kubernetes Connections?
Yes. Connection commands run in the CloudThinker managed sandbox, and their credentials stay there. They never reach the Worker.
What happens if the Worker goes offline?
The picker marks it Offline and the run tells you. CloudThinker never moves the work to the cloud on its own.
Can my team use my Worker?
A personal Worker serves only you. A workspace Worker is visible to the members you allow, and automations can run on it.
Does the Worker isolate my machine?
No. A shell command runs with the full access of the OS account that runs the Worker. Use a dedicated account or machine when you need a boundary.
Explore the platform.
- Platform OverviewOne unified layer under every agent.
- AI-DLCAI writes the code. Agents run it in production.
- Connections100+ secure connections give every agent the full picture.
- Auto ModeSafe autonomy for cloud operations, on your terms.
- Skills FrameworkTurn operational knowledge into safe agent action.
- Security & ComplianceSecurity by design, at every layer.
Put CloudThinker on your own machine.
Create a Worker in Admin settings, then Sandboxes. Leave it running, and pick it from any chat.