Environments
Keep using CloudThinker in your browser, on a laptop or a phone. Frontier Investigation Agents run in CloudThinker Cloud, and an environment runs their files and shell commands in a folder you pick.
The worker process asks CloudThinker for work over HTTPS. Nothing connects in to your machine. There is no listener to run and no port to open.
You keep using CloudThinker on the web, on a laptop or a phone. The worker process does the local part, and it only needs the cloudthinker CLI.
CloudThinker in a browser
On a laptop or a phone. Pick the environment under Run in.
CloudThinker Cloud
Where the agent runs. The model, Connections like AWS or Kubernetes, and their credentials stay here.
Your environment
A folder on your machine. It reads and edits files, runs shell commands, and follows your AGENTS.md and Skills.
Your laptop, a server, or a CI runner.
Create an environment
Open Admin Settings, then Environments, and give the environment a name, like my-laptop.
Run one command in your folder
CloudThinker shows the command. The worker process 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 Environment. CloudThinker now works in that folder.
In CloudThinker Cloud. The worker process runs the file and shell work in your folder and sends the results back.
No. The worker process only makes outbound HTTPS requests to CloudThinker. Nothing connects in to your machine.
Yes. Connection commands run in the CloudThinker managed sandbox, and their credentials stay there. They never reach the environment.
The picker marks it Offline and the run tells you. CloudThinker never moves the work to the cloud on its own.
A personal environment serves only you. A shared environment is available to authorized workspace members, and automations can run in it.
By default, shell commands run with the access of the OS account that starts the worker process. Use a dedicated account or machine when you need a boundary.
Create an environment in Admin Settings, then Environments. Keep its worker process running, and select it from any chat.