A fix started from the phone, not redone at the laptop

Many agents, one playbookDeveloper who starts tasks from the phone while away

On a train we started a fix from the phone, driving a Claude Code session running on the home laptop. That worked and was recorded. Another day we used a cloud-hosted session from the phone instead, and the laptop's agent later knew nothing about it.

How do I stop my laptop's agent redoing a task I started from my phone?

With ArcRoom, run mobile work on a Claude Code session on your own machine, using the phone as a remote control. Its steps are recorded like any session, so the laptop's next agent reuses them instead of starting again, and it gets the last-run note. Sessions in a vendor's cloud sandbox are not connected today, so nothing from them is recorded.

Also asked as: My laptop agent knows nothing about the task I ran from my phone. Why? · How do I keep context between phone and laptop AI agent sessions? · Can a cloud-hosted agent session share memory with my local agent?

The work

ArcRoom runs where the agent runs.

ArcRoom keeps
  • Last-run note
The next agent gets

[laptop] Last session in this project (claude, 2 h ago, started remotely) stopped mid-way.

Step by step

  1. ArcRoom runs where the agent runs.
  2. If the phone is a remote control for a session on your own machine, every step is recorded as usual and the laptop's next session gets the last-run note.
  3. If the session runs in a vendor's cloud sandbox, ArcRoom is not installed there today, so nothing is recorded.
  4. Rule of thumb: start mobile work on a session that runs on your machine.

What the agent sees

[laptop] Last session in this project (claude, 2 h ago, started remotely) stopped mid-way.
Asked: "fix the date filter on the orders page"

Compared with today's tools

Commit and push from the cloud session

Have the cloud session push a branch with a clear commit message, then read it on the laptop.

Setup
none
Ongoing
write a handover in the commit, ~3 min

ArcRoom

Every agent reads the team playbook before it works and writes to it when it finishes. Nothing to update by hand.

Setup
2 min (npx arcroom init), local sessions only
Ongoing
None

For cloud sessions the git branch is the only handover today, and it works; ArcRoom only helps when the session ran on your machine.

Where it stops

Cloud-hosted agent sessions are not connected. Only sessions on a machine where arcroom init ran are recorded.

Try it in your project

Works with the agents your team already uses, and any agent over MCP or the HTTP API.

More in many agents, one playbook