Run Coding Agents From Your Phone: Keep AI Working While You’re Away

Coding agents take minutes or hours, and they stop when they need you. How to keep agents running on your own computer and check on them, or answer them, from your phone.

Here’s a familiar scene. You give a coding agent a meaty task, watch it get going, and step away. Forty minutes later you come back to find it stopped after three minutes, politely waiting for you to approve a command. Agents are fast; waiting for a human is slow. This guide covers how to keep agents productive when you’re not at your desk.

Why agents stall

  • Permission prompts. Good agents ask before running risky commands, deleting files or installing packages. That’s a feature — but it pauses everything.
  • Questions. “Should the reset link expire after 15 minutes or 24 hours?” The agent can’t guess your product decisions.
  • Closed terminals. Close the laptop, lose Wi-Fi, or quit the terminal app, and the session — and the agent inside it — may be gone.

Option 1: terminal multiplexers

Tools like tmux and screen keep a session alive after you disconnect, and you can reattach over SSH. They’re powerful and free. The catch on a phone is ergonomics: setting up SSH keys, typing Ctrl-b sequences on a touch keyboard, and getting no notification when an agent needs you.

Option 2: cloud agents

Some agents can run in a hosted sandbox instead of your machine, which keeps going when you leave. That works well for self-contained repos, but your local setup — databases, private services, environment files, the dev server you’re testing against — usually isn’t there.

Option 3: keep it local, reach it remotely

The third approach — the one I built Sync Log around — keeps agents running on your computer, with your files and tools, and gives you a proper mobile view of them:

  1. Sessions in a background service. Terminals belong to a small service, not to a window, so closing the app or restarting it doesn’t end them.
  2. A real phone client. The same terminal on your phone, with Esc, Tab, Ctrl and arrow keys above the keyboard, plus voice dictation.
  3. Notifications that need you. When an agent asks something, your phone shows it, and on Android you can answer straight from the notification.
  4. You choose the network path. Your home Wi-Fi, Tailscale, or a Cloudflare tunnel. Each device pairs with a one-time code.

A workflow that works

  1. Start the agent on your computer with a clear task and a workspace: synclog new --agent claude --task "add password reset with tests".
  2. Head out. The session keeps running.
  3. When it needs a decision, answer from your phone in a few seconds.
  4. Check its progress whenever you like: scroll back through the output, peek at the diff, open the dev server preview.
  5. Back at your desk, review the finished change properly before merging — see how to review AI-written code.

Safety when your agents are reachable

  • Keep remote access off until you need it, and prefer private networks (your LAN or Tailscale) over public tunnels.
  • Revoke devices you no longer use. Lost phone? Remove it from the paired devices list.
  • Don’t loosen agent permissions just to avoid prompts. Answering from your phone is faster than cleaning up after an agent that ran something it shouldn’t have.

If this sounds like your week, download Sync Log — it’s free for Android, iPhone, macOS and Linux.

Keep reading

More from the blog

What Are AI Coding Tools? A Plain-English Guide

AI coding tools use large language models to suggest, write, explain and test code. Here’s what they are, how they work, what they’re good at and where they still need you.

Autocomplete, Chat or Agent? The Three Kinds of AI Coding Tools

AI coding tools come in three flavours: inline autocomplete, chat assistants and autonomous coding agents. How each works, what each is best at, and how to pick.