Skip to Content
Chat from your phone

Chat from your phone

Agent Ping tells you a session finished or needs you. To answer from your phone instead of walking back to your computer, give the session a remote link: a claude.ai/code address that opens the same conversation on your phone.

Claude Code makes that link through its Remote Control  feature. Agent Ping picks it up and adds it to every alert from that session.

The session keeps running on your computer, with your files and tools. Your phone is just another window onto it, so your computer has to stay awake and online, and the claude process has to keep running.

What you need

  • Agent Ping installed on the computer.
  • A Claude Pro, Max, Ultra, Team or Enterprise plan, signed in to Claude Code with /login. API keys don’t work, and neither do Bedrock, Google Cloud, Microsoft Foundry or an LLM gateway.
  • On Team and Enterprise, an Owner has to turn on Remote Control in the admin settings . It’s off by default there.
  • The Claude app on your phone, signed in to the same account, or a browser that can open claude.ai/code.

Set it up

Start the session with Remote Control on

In your project folder, run:

claude --remote-control "My project"

The name is optional. It’s how you’ll recognize the session in the list on your phone. In a new folder, Claude Code asks you to trust it first. When it’s ready, it shows /remote-control is active and the session’s address.

Already in a session? Run /remote-control there and choose Enable Remote Control.

Make it the default (optional)

To stop typing the flag, turn it on for every session. In Claude Code, open /config and set Enable Remote Control for all sessions to true, or add this to ~/.claude/settings.json:

{
  "remoteControlAtStartup": true
}

Send yourself a test

Give the session something that takes more than 30 seconds, and let it finish. You should get an alert with a link to the session. Turns shorter than that don’t send a “finished” alert, so a quick question won’t test anything.

Open it on your phone

Tap the alert, then tap Open session on its page. Alert emails have the same button. You can also find the session yourself: open the Code tab in the Claude app or go to claude.ai/code. A session that’s online shows a computer icon with a green dot.

Type a reply there and it runs on your computer. The conversation stays in sync in both places.

An alert only gets the link if Remote Control was on when the alert was sent. If you turn it on partway through a session, alerts have the link from the next turn on. If your alerts have no link:

  • Look for /rc active at the bottom of the session. If it isn’t there, run /remote-control.
  • Run agentping config. If session-link is set, it replaces the Remote Control link on every alert from this computer. Remove it with agentping config unset session-link.
  • Run agentping doctor to check that the hooks are installed.
SessionLink in the alert
Claude Code with Remote Control onhttps://claude.ai/code/session_…, opens anywhere
Claude Code cloud sessionhttps://claude.ai/code/session_…, opens anywhere
Claude desktop app session, Remote Control offclaude://code/continue?…, opens only on that computer
Claude Code in a terminal, Remote Control offNone
CodexNone, unless you set your own link

When the connection drops

  • The computer sleeps or loses network: an interactive session reconnects by itself when it’s back.
  • You close the terminal: Remote Control stops with the claude process. Over SSH, run it inside tmux or screen so it survives the connection closing.
  • Your phone can’t see the session: check you’re signed in to the same account on both, then run /remote-control in the session to connect again.

Several sessions at once

Each interactive session has its own remote link. To start new sessions from your phone, run Claude Code’s server mode in the project folder instead:

claude remote-control --name "My project"

Press the spacebar to show a QR code for your phone. Server mode exits after about 10 minutes without a connection, so restart it after a long outage. The Remote Control docs  list its other options.

What goes where

Remote Control is separate from Agent Ping, and it has a different privacy footprint:

  • Agent Ping only ever receives what’s in an alert, including the link. The link alone doesn’t open the session: anyone who isn’t signed in goes to Claude’s sign-in page.
  • Remote Control connects out from your computer over HTTPS and opens no inbound ports. While it’s connected, Anthropic stores the session’s transcript on its servers, under its data usage policy. Your files and commands stay on your computer.

If you read your sessions in another tool, such as a web viewer you host, point alerts there instead:

agentping config set session-link "https://viewer.example/s/{session_id}"

Agent Ping fills in {session_id}, {project} and {tool}. The template has to include {session_id}. This applies to every alert from that computer, Codex included, and it replaces the Remote Control link.

{session_id} is Claude Code’s or Codex’s own ID for the session, so your viewer has to be able to find a session by that ID, even if its own URLs use a different one. Put the viewer behind a sign-in too, since it can run commands on your computer. To go back:

agentping config unset session-link
Get started