[{"data":1,"prerenderedAt":21},["ShallowReactive",2],{"doc:en:remote-control":3},{"title":4,"lede":5,"html":6,"headings":7},"Remote control","Remote control makes an agent’s session reachable from claude.ai and the Claude mobile app, so you can answer it from a browser or your phone. This page explains how to turn it on, what shows in Escouade, how long the agent stays reachable, and how to turn it off.","\u003Cp>\u003Cimg src=\"\u002Fimages\u002Fen\u002Fremote.jpg\" alt=\"Escouade on the left, with the remote control icon on the card of the agent “refacto-auth”, and on the right the Claude mobile app showing the same conversation, named “demo-api · refacto-auth”\" width=\"1920\" height=\"960\" loading=\"lazy\" decoding=\"async\">\u003C\u002Fp>\n\u003Ch2 id=\"turning-on-remote-control\">Turning on remote control\u003C\u002Fh2>\n\u003Col>\n\u003Cli>Right-click the agent’s card in the sidebar.\u003C\u002Fli>\n\u003Cli>Choose “Turn on remote control” (“claude.ai, mobile”).\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>Escouade starts the agent’s process if it’s stopped and asks Claude Code to open the remote session. A message confirms: “refacto-auth is reachable from claude.ai and the Claude app”. The session is named \u003Ccode>project · agent\u003C\u002Fcode> there, for example \u003Ccode>demo-api · refacto-auth\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Cp>If Claude Code can’t open the session, an error message starting with “Remote control unavailable” appears, and the option stays off.\u003C\u002Fp>\n\u003Cp>The menu of an archived agent doesn’t offer remote control. For an agent running in \u003Ca href=\"\u002Fen\u002Fdocs\u002Fclaude-code-view\u002F\">the Claude Code view\u003C\u002Fa>, the entry is only offered if it’s already on: in that view, Claude Code’s interface \u003Ccode class=\"key\">\u002Fremote-control\u003C\u002Fcode> command turns it on and off, and switching views is refused while Escouade’s remote control is on.\u003C\u002Fp>\n\u003Ch2 id=\"what-shows-in-escouade\">What shows in Escouade\u003C\u002Fh2>\n\u003Cp>A wave icon appears on the agent’s card, after its name. It says how the link is doing, and its tooltip details it:\u003C\u002Fp>\n\u003Cdiv class=\"table\">\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Icon\u003C\u002Fth>\n\u003Cth>Start of the tooltip\u003C\u002Fth>\n\u003Cth>Meaning\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>Blue\u003C\u002Ftd>\n\u003Ctd>“Remote control: connected”\u003C\u002Ftd>\n\u003Ctd>The session is open and connected.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Gray\u003C\u002Ftd>\n\u003Ctd>“Remote control: connecting…” or “Remote control: waiting for a connection”\u003C\u002Ftd>\n\u003Ctd>The link is being established.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\u003C\u002Ftable>\u003C\u002Fdiv>\n\u003Cp>Each tooltip ends with “(reachable from claude.ai and the Claude app)”.\u003C\u002Fp>\n\u003Cp>When the agent is reachable, the card’s menu changes:\u003C\u002Fp>\n\u003Cdiv class=\"table\">\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Entry\u003C\u002Fth>\n\u003Cth>Effect\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>Turn off remote control\u003C\u002Ftd>\n\u003Ctd>Cuts the link (see below).\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Open on claude.ai\u003C\u002Ftd>\n\u003Ctd>Opens the session in your browser.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Copy the claude.ai link\u003C\u002Ftd>\n\u003Ctd>Copies the session’s address (“claude.ai link copied”), to open it on another device.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\u003C\u002Ftable>\u003C\u002Fdiv>\n\u003Cp>The last two entries appear as soon as the session’s address is known.\u003C\u002Fp>\n\u003Cp>What you send to the agent from claude.ai or the Claude app also shows in Escouade’s conversation, in a bubble like yours, with the note “from claude.ai” (its tooltip says: “Sent from claude.ai or the Claude app (remote control)”).\u003C\u002Fp>\n\u003Ch2 id=\"how-long-the-agent-stays-reachable\">How long the agent stays reachable\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Cstrong>As long as Escouade runs.\u003C\u002Fstrong> The agent stays reachable when you close the window: it hides and the app goes on in the notification area (see \u003Ca href=\"\u002Fen\u002Fdocs\u002Fmanaging-agents\u002F#closing-the-window-quitting-and-restarting\">agents\u003C\u002Fa>). If you quit the app with “Quit”, the agents stop and are no longer reachable.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>No stop for inactivity.\u003C\u002Fstrong> Escouade normally stops an idle agent’s process after a delay (30 minutes by default); an agent whose remote control is on keeps its process, to stay reachable.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>After a restart.\u003C\u002Fstrong> Escouade restarts the agents whose remote control is on along with the app and reattaches their previous remote session: the link you had opened on your phone stays valid. If that session is gone in the meantime, a new one is opened, with a new link. If the link fails at startup, a “Remote control unavailable:” notice followed by the cause appears in the agent’s conversation.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2 id=\"turning-off-remote-control\">Turning off remote control\u003C\u002Fh2>\n\u003Cp>Right-click the agent’s card, then “Turn off remote control”. Escouade asks Claude Code to close the remote session, the icon goes away, and the agent becomes an ordinary agent again (which the idle stop can stop again). Archiving or deleting an agent also turns off its remote control.\u003C\u002Fp>\n",[8,12,15,18],{"id":9,"text":10,"depth":11},"turning-on-remote-control","Turning on remote control",2,{"id":13,"text":14,"depth":11},"what-shows-in-escouade","What shows in Escouade",{"id":16,"text":17,"depth":11},"how-long-the-agent-stays-reachable","How long the agent stays reachable",{"id":19,"text":20,"depth":11},"turning-off-remote-control","Turning off remote control",1791926756230]