All pages
Agentic pipelines · Lesson 2.2 · 12 min
The cloud and your phone
Hand work to a cloud box and approve it from the iPhone app.
After this lesson you can decide whether a piece of work should stay on your Mac with your phone as the approver, or move to a cloud box that runs with the Mac shut, and you can hand work to the box and keep an eye on it from your iPhone.
Time: 12 minutes · Works on: macOS app, cloud workspace and iPhone.
Work that outlives your desk
Agent work doesn't fit neatly into the hours you're at your desk. A refactor is half done at six. A test suite takes forty minutes. A dependency upgrade can run overnight. The question isn't whether the agent can keep going without you. It's where it keeps going, and how you stay in the loop.
There are two answers, and they fit different situations:
| The Mac, with your phone | The cloud box | |
|---|---|---|
| Where it runs | Your Mac, which must stay awake and online | A Linux box at trmnly.dev |
| What it can reach | Everything on the Mac: panes, the browser, local services, your saved hosts | A clone of your repository, its own browser and shells |
| What it costs | Nothing extra | Credits, one a minute while the box runs |
| Your phone does | Approves, watches panes, types replies | The same, plus runs the cloud agent itself |
| Choose it when | The work needs your Mac's environment | The Mac will be closed, or you're away for long |
The rule of thumb: if the work needs your Mac, keep it there and take the approvals with you. If it needs only the repository, send it to the box.
Hand off through git, not through memory
Moving work to another machine only works if everything the agent needs travels with it. Anything that lives only in your head, an uncommitted file, or a shell variable you set this afternoon stays behind.
Before you hand off, make the work self-describing:
- The goal is written down. A card on the board or a spec file in the repository, not just the conversation you've been having.
- The state is in git. Committed, or at least on a branch that can be pushed. TRMNLY's Move to Cloud pushes your uncommitted work for you, but it leaves out untracked files that look like secrets.
- Secrets are in a vault, not in files. The box gets keys from its own Keys
tab. Your Mac's
.envdoesn't follow. - The stop condition is clear. "Finish the refactor until the tests pass, then open a draft PR" ends. "Keep improving it" doesn't.
Approve from a distance, carefully
Your phone turns approvals from "wait until I'm back" into "answer in ten seconds". That's the point, and it's also the risk: a card read on a lock screen gets less attention than one read at your desk.
Keep two habits. Read the badge before you read anything else. A Read-only or Writes card is usually safe to answer quickly. A Dangerous one, such as a shell command or a file write, deserves the full arguments or the diff, which the card shows. And use Allow for 15 min for a burst of similar, safe calls, never as a way to stop being asked. TRMNLY won't offer it for a dangerous tool anyway.
A worked example: the six o'clock hand-off
It's six. Claude Code has been working in a pane on a refactor of the billing module. Half the tests pass. You want it to keep going while you go home.
- You check that the card describes the goal and the finish line: "All billing tests pass; open a draft PR."
- From the pane, you move the session to the cloud. Your work is pushed to a temporary branch, the box clones it with your changes still uncommitted, and the same Claude Code conversation resumes in a cloud pane named claude (from Mac).
- On the train, you switch the phone app to Cloud and open the pane in Terminal. Claude Code is asking whether it may run a migration script. You read the command and answer in the pane.
- At nine you check the pane from the phone: draft PR open, tests green. You review it in the morning at your desk.
Your Mac was never involved after step 2. The branch and files on the Mac are unchanged.
Do it in TRMNLY
Pair the phone for Mac work
- On the Mac, press
⌘,, open AI Agent and scroll to Remote Control (trmnly.dev). Turn on Enabled, then press Start pairing under Pair this Mac. The iPhone remote lesson walks through signing in on the phone. - In the same section, set Push sidebar approvals to the phone. When away, the default, sends the sidebar agent's cards to the phone once the Mac has had no input for two minutes or its screen is locked. Cards from MCP clients such as Claude Code always go to the phone.
- Ask the agent on the Mac to write a file, walk away from the keyboard, and answer the card on the phone's Now tab. Choose Approve or Deny. The Mac waits two minutes for an answer, then denies.
- On the phone, open Terminal, point it at a pane running a long command and tap the 🔔. You get one notification when the pane goes quiet or its command finishes. A watch lapses after 24 hours.
- On Now, use Keep awake to hold the Mac awake for 1 or 4 hours while you're away. It doesn't stop a closed lid from sleeping the Mac.
Hand a session to the cloud
- Pair the Mac (step 1), make sure the repository's
originis on GitHub, and sign Claude Code in on the workspace's Keys tab, in the Agents in this workspace card. For Claude, paste the output ofclaude setup-token. - In the Mac pane, find the strip that shows the pane's folder and branch. Press its + button and choose Move to Cloud…. Read the sheet: it lists what will be pushed and which untracked files are left out because they look like secrets. Press Move to Cloud, then Open in Browser.
Drive the box from Claude Code
Without a browser at all, an MCP client can drive the box. On any machine with Claude Code:
claude mcp add --transport http trmnly-cloud https://trmnly.dev/mcpThe name is
trmnly-cloudso it doesn't hide the Mac'strmnlyserver. The first connection opens a trmnly.dev page in your browser; press Allow. Connecting costs nothing. The first tool call that needs the box starts it.Ask Claude Code to start an agent in the box: it calls
agent_startwithagent: "claude", apromptand acwdunder~/workspace. It checks progress withagent_read, which can wait for the agent to finish, and follows up withagent_send. Ifagent_startsays the agent isn't signed in, finish step 6.
Watch and approve the cloud agent
- In the cloud workspace's Agent tab, pick Ask mode for anything you haven't run before. Each tool call your rules don't already allow waits as a card with Allow, Always allow and Deny. The iPhone app's Cloud agent screen is the same agent, with the same modes and cards, so you can answer from the phone.
- Use Plan to have the agent propose a change without making it, and Auto only for work you'd let run with nobody watching.
- Remember the meter. The box stops on its own about 10 minutes after your last activity, and a start is refused on an empty balance. Check your credits on the trmnly.dev dashboard before a long run.
For work that should start on a timer with no one there, use a cloud job instead. Schedules and unattended runs covers when to choose one.
Check yourself
- You answered an approval from the Mac's agent on your phone.
- A 🔔 watch on a pane notified you when its command finished.
- You can say which of your current tasks belong on the Mac and which in the box.
- A cloud agent in Ask mode stopped for a card, and you answered it.
Go further
- The cloud workspace — the box's window, ports and preview URLs
- Cloud workspace — every tab, rules in Ask mode, and saving a workspace
- Remote control — scopes, the trusted phone, and what can never be done remotely
- MCP server — the cloud endpoint,
agent_startand what it costs - Lock the Mac and walk away — the Mac half of stepping away