Skip to content
Arugula

Run your agent in the cloud

A Cloud workspace is a machine of a project’s in the cloud. An agent there keeps going with your laptop shut, and everyone in the project sees the same terminals and agents. Cloud workspaces are in a limited beta: if your account isn’t in it, the platform page says so.

You need to be an owner or editor of the project.

1. Make the workspace

Section titled “1. Make the workspace”

On the platform page, open the project, then Workspaces in the bar, and choose Create a cloud workspace. Give it a name and a size: small (2 vCPU, 2 GiB) or large (8 vCPU, 8 GiB, enough for a Rust build). Then give it a repository from a terminal and rebuild it:

Terminal window
arugula cloud edit dev --repo https://github.com/acme/app --setup setup.sh --project acme
arugula cloud rebuild dev --project acme

Or do it all from a terminal in one go:

Terminal window
arugula cloud create dev --repo https://github.com/acme/app --setup setup.sh --project acme --wait

The box clones the repository and runs the setup script in a session called setup. arugula cloud ls says how it went. A linked GitHub repo needs no token; see Cloud workspaces for private repositories and secrets.

2. Give it a key

Section titled “2. Give it a key”

Agents there run on the project’s own Anthropic or OpenAI key. An owner of the project sets it once:

Terminal window
arugula cloud key set anthropic --project acme   # reads the key from stdin

Anthropic’s may be a Claude subscription’s token from claude setup-token. The key never enters the box: see Inference keys.

3. Start an agent

Section titled “3. Start an agent”

Any of these:

  • From the workspace’s page: choose + Agent ↗. Control’s page opens on the workspace’s machine and asks for the agent’s task, as Start an agent does on your own machine.
  • From a thread: write @arugula and the task in one of the project’s channels, or choose Agent on this on an issue. That starts an agent session on a workspace with the repository, with a card in the thread. See Hand an issue to an agent.
  • From an agent on your machine: Arugula’s MCP tools take cloud_workspace: "dev" to start an agent there, prompt it and read its output. See MCP: Cloud workspaces.

4. Watch it and answer it

Section titled “4. Watch it and answer it”
  • Its terminals and agent blocks are live on control’s page, with the project’s other machines; Open them ↗ on the workspace’s page goes there.
  • When it asks something, the card shows on the rail, in the swarm and on your phone, as any agent’s does. See Watch your agent from your phone.
  • An agent session’s card, in its thread, says what it’s doing; reply in the thread to give it its next turn.
  • The box pauses itself about 10 minutes after it goes idle, never in the middle of an agent’s turn, and opening it wakes it. A closed agent’s transcript stays on the workspace’s page.

Next steps

Section titled “Next steps”