All pages

Lesson 7.2 · Beyond the Mac · 12 min

The cloud workspace

A Linux box at trmnly.dev, billed by the minute.

Listen

After this lesson, you can open your own Linux box at trmnly.dev and run shells and a coding agent in it. You can also preview a dev server from any browser, and move a session there from your Mac when you need to leave.

Time: 12 minutes · Works on: cloud workspace

What it is

Every account with workspace access gets one Linux sandbox. It has a real shell, your checkouts, a browser and most of the tools the Mac app's agent has. It runs whether or not your Mac is awake, so it is where work goes when you're on a phone or away from your desk.

It is billed by the minute against your credits. One credit is one minute, counted only while a terminal is attached. At the base pack rate that is $0.50 an hour. Models run on your own keys, so tokens aren't billed here. New accounts start with 100 credits.

Open it

  1. Sign in at trmnly.dev. Your dashboard opens.
  2. Press Open cloud workspace. If you don't see the button, your account doesn't have workspace access yet.
  3. On the Workspace page, press Open full TRMNLY → for the whole interface. Just a terminal gives you a single shell instead.
  4. Wait for the box. A cold start takes about a minute. After that it stays up while you use it.

The box stops on its own about 10 minutes after your last activity. It also stops when your credits run out, and a start is refused on an empty balance. A tab left open in the background keeps a running box alive, but it won't start a stopped one.

Find your way around

Shells run down the left side, one row each, with a title, a status dot and any flags a pane has raised. The bell collects events such as a finished job or an approval that's waiting.

The panel on the right has tabs: Files, Projects, Git, Ports, Search, Prompts, Queue, Tasks, Plans, Jobs, Background, Agent, Chat, Notes, Keys, SSH, Flows, Activity, Remote, Web and Help.

A few keys help. Use ⌘K for the command palette and ⌘B to show or hide the right panel. ⌘\ splits the focused shell and ⌘⇧F finds text in its scrollback. Off macOS, use Ctrl in place of ⌘.

Preview a dev server

  1. In a shell, clone a project and start its dev server on one of the ports listed in the Ports tab.
  2. Open Ports. A port with something listening on it shows a public URL.
  3. Open that URL from any browser, including your phone.

The Web tab is different. It runs Chromium on the box itself, so it can load a localhost server your laptop can't reach.

Run the agent in the box

The Agent tab runs Claude Code or Codex inside the workspace and streams the turn into a transcript.

  1. Open Keys. The Agents in this workspace card at the top is where you sign Claude Code or Codex in. For Claude, paste the output of claude setup-token. Codex uses an OPENAI_API_KEY stored in the vault.
  2. Open Agent and pick a mode:
    • Plan is read-only. The agent proposes a plan and changes nothing.
    • Ask runs the agent, but stops for any tool call your rules don't already allow.
    • Auto runs commands and edits files without asking.
  3. Set the folder field to the directory the agent should work in, under ~/workspace.
  4. Send a task. In Ask mode a call waits as a card with Allow, Always allow and Deny. Always allow writes a rule, and the Rules panel is where you read and edit rules.

Tip: A rule for a command covers exactly that command. Anything chained, piped or redirected is asked about every time, so allowing git status never allows git status; curl … | sh.

You can attach up to six images or files to a message. History lists past conversations to reopen.

Move a session from your Mac

A pane on your Mac can hand its work to the box, so you can close the laptop and carry on from the browser or your phone. This needs a paired Mac. Pair it in Settings → AI Agent, under Remote Control (trmnly.dev). The repository's origin must be on GitHub, and Claude Code must be signed in on the workspace's Agents card.

  1. In the Mac pane, find the strip that shows the pane's folder and branch. Press its + button and choose Move to Cloud….
  2. Read the sheet. It lists what will be pushed and which untracked files are left out because they look like secrets.
  3. Press Move to Cloud. Your work is pushed to a temporary branch, and the box clones it with your changes still uncommitted. If Claude Code was running in the pane, the same conversation resumes in a cloud pane named claude (from Mac).
  4. Press Open in Browser.

Your branch and files on the Mac are not changed. The temporary branch is deleted from GitHub once the box has cloned it.

Check yourself

  • Open the workspace, run uname -a in a shell, and confirm it's Linux.
  • Start a server on a listed port and open its URL from your phone.
  • Send the agent a task in Ask mode and answer one approval card.
  • Check the credit balance on your trmnly.dev dashboard before and after a session.

Go further