Remote-control Claude Code from your phone with Cowork

The setup

Cowork gives me a chat interface on my phone for dispatching Claude Code tasks to my machine. That machine already has authenticated tools, Git aliases, opusplan as the default model, and deployment webhooks. I can send an instruction from anywhere, and the agent runs it against the real checkout at home.

What I sent, and what the agent did

I sent one line from my phone:

for my imsj front page project, change the appbusleh.imsj.dev to
busleh.imsj.dev and use gg to commit and push

Cowork Dispatch chat on a phone dispatching a Claude Code task — Dispatching a code task from the phone — Cowork knows the local workspaces and runs the change on the machine.

It did not recognise “imsj”, so it asked for the repository instead of guessing:

Don’t see an “imsj” project among your known Claude Code workspaces… What’s the path to the imsj front page repo?

I replied imsj-frontpage. It found the repo, swapped the domain, and committed and pushed with my gg alias:

Starting a code task in /Users/jason/workspace/code/imsj-frontpage — swapping the domain and pushing via gg now.

I typed one instruction and answered one question. The agent edited the file, committed the change, and pushed it using the tools and Git configuration on my machine.

Because I was not at the keyboard, I set clear limits: make the requested change, leave unrelated code alone, ask if anything is unclear, and report the result. I cover this in making Claude Code smarter. With opusplan, Opus planned the task and Sonnet made the change.

I couldn’t watch it — the webhook told me it worked

From my phone, I could read the agent’s summary but could not watch it work. The real confirmation came from the deployment pipeline triggered by the push, which notified Discord when it finished:

Discord notification from GitHub Actions showing a successful deployment of adjscent/imsj-frontpage on the main branch — The deploy webhook firing in Discord — a green Success on `main`, the commit, and a link to the run. This, not the chat summary, is how I knew the remote task actually landed.

The notification showed a successful deployment from main, the commit, and a link to the run. Because I could not watch the work, I used CI, deployment notifications, and health checks to confirm that it worked. I also kept a rollback ready.

Cowork is not available on every plan, so I tested it on my personal codebases. Before relying on it, I made sure my tests, deployment checks, and rollback process worked.