Skip to content
Arugula

The platform page

The platform page, at app.arugula.io, is where your projects in Arugula control live: their issues, runs, Cloud workspaces, deploys and chat, and an Inbox of what wants you. Your machines, terminals and devices stay on control’s page; Projects ↗ there opens this page, and Control in its bar goes back.

Everyone has a personal project, and each team has one. The bar’s project name switches between them; the Arugula / Projects wordmark lists them all.

A project’s home

Section titled “A project’s home”

Project in the bar is the project’s home. It shows its chat channels and direct messages, its newest issues and Docs, its last runs, its linked repos and environments, its Cloud workspaces and, for a team’s project, who’s in the team (changing that stays on control’s page, under Teams…).

A section with nothing in it says what it’s for and offers the next step:

  • Link a repo: a linked GitHub repo brings its pull requests and issues into the project, and its pushes and events can start runs. Owners and editors link them. See Linked GitHub repositories.
  • Make an environment: where the project deploys to. Owners make them.
  • Start a run, or Create a cloud workspace first when there’s none to run on.
  • Turn on chat, for a team’s owner, or Ask an owner, which copies a note asking one to turn it on.

Project settings, under the project’s name, holds its linked repos, where new issues go, environments, runs’ standing grant, workspace size, the finish step and model for agent sessions, its agent tokens and its Claude spend.

Issues

Section titled “Issues”

Issues lists the project’s own issues, and opens and changes them. See Native issues.

Runs

Section titled “Runs”

Runs lists the project’s runs, newest first, narrowed by state, by what started it (by hand, a deploy, a schedule or an event) and by run spec. A run is a command on one of the project’s Cloud workspaces.

  • Owners and editors start one by hand: a run spec, or a command on a workspace they pick. They also keep the run specs, each with schedules (+ Schedule) and rules for events from a linked repo.
  • A run’s page says who or what started it and the exact command, shows its pane while it runs (on control’s page), then its log, its timeline and its thread.
  • A run that failed goes to your Inbox.

From a terminal: arugula runs (see the CLI).

Cloud workspaces

Section titled “Cloud workspaces”

Workspaces in the bar lists the project’s Cloud workspaces, for accounts in the beta. A Cloud workspace is a machine of the project’s in the cloud: its terminals and agents keep going with your computer off, and everyone in the project reaches them.

  • Create a cloud workspace asks for a name and a size: small (2 vCPU, 2 GiB) or large (8 vCPU, 8 GiB), with its price an hour while it runs. Its repos, packages and setup script come after, with arugula cloud edit. A team’s owners and editors make them.
  • A workspace’s page shows its state (ready, paused, waking, failed), its size and machine, and the transcripts of its closed agents. + Agent ↗ opens control’s page on its machine and starts an agent there; Open them ↗ shows its terminals and agent blocks.
  • A changed spec shows Wants a rebuild, with the command to run.

Deploys

Section titled “Deploys”

Deploys lists every environment’s deploys, newest first: each one’s state, environment, source, who planned it and when. A deploy puts a commit on one of the project’s environments, once an owner approves it.

  1. An owner makes an environment under Environments in Project settings: the driver that applies a deploy, its settings and its secrets. A secret’s value is never shown again.
  2. An owner or editor (or their agent, with plan_deploy) chooses Deploy…, picks the environment, the commit and the repo, and chooses Plan. The plan’s text is what an owner approves.
  3. Ask for approval sends each of the project’s owners a card.
  4. An owner approves or denies on control’s page, on their phone or in a browser, with a passkey.

From a terminal: arugula deploys (see the CLI).

The Inbox

Section titled “The Inbox”

Inbox collects what wants something of you across your projects:

  • deploys waiting for your approval, first;
  • reviews requested of you, changes requested, checks that failed, runs that failed, mentions and issues assigned to you, and pull requests ready, merged or closed, on your linked repos and native issues;
  • New in threads: issues’ and runs’ threads with posts you haven’t read;
  • Drafts waiting for you: comments, reviews and issues your agents drafted, for you to send.

Seen marks an entry seen; Dismiss takes it out while its reason holds. arugula forge inbox lists the same from a terminal.

Chat and settings

Section titled “Chat and settings”
  • Chat opens the project’s channels and direct messages. See Chat and threads.
  • Settings is the project’s settings inside a project, else your account’s: appearance, chat notifications and quiet hours, what the agents on each of your machines may do in each project, your agent tokens, and your plan where you have one. The account menu has Account settings, Appearance… and Open Control.

Next steps

Section titled “Next steps”