Control agents from your phone
On this page
Read agent progress, send follow-up instructions and attach context while away from the desktop.
Before you start
Install the Code Overlord companion for iOS or Android through your available download route. Sign in with the same Code Overlord account. The desktop or Skyforge machine owning the session must remain reachable; the phone does not run the coding agent itself.
Pair and open a session
- On desktop, open Summon → Sync. The Connect a phone dialog displays the pairing QR code.
- On the phone, choose Scan QR to connect and complete pairing.
- Select the intended workspace.
- Open the agent/session area (Minions) and choose a running session.
- Read recent output, then send a specific follow-up instruction. Attach an image or dictate when useful.
- If local and cloud sessions are both available, check the session's home/cloud indicator before sending work.
Example instruction
Give me a short progress update on the settings fix. Identify any question you need me to answer, and tell me which checks have completed.
When the agent needs a decision, reply with the decision and its scope. For a new task, use the phone's Summon control where available and confirm the agent and working directory.
Read files and notes
The Scrolls area shows files exposed from the desktop, including open documents. Use the note area to capture work for later. Do not assume this is the same as browsing every file in an arbitrary remote repository.
Check the result
Confirm the intended session receives your reply and produces new output. If the host is offline, restore its connection before resending work. Treat stale output as a connection state, not proof of a running task.
Recorded example
The video uses the actual Android companion paired with Code Overlord 1.5.119. It starts after pairing, selects Ember Studio → Minions → OpenAI Codex / app, and sends a request to identify the app README's start and test commands. The real desktop agent reads the file and saves phone-session-proof.json; its answer returns to the phone. The film then opens the same README in Scrolls and checks the workspace's two existing Thy Quill notes.
The commands, README path and SHA-256 match the saved result. All 19 pre-existing workspace files and both notes remain unchanged. Neither the server nor the tests are run in this example. The Android emulator paired by opening the exact link from the desktop QR through the companion's normal pairing flow; the film does not demonstrate a camera scan.
Platform differences
Controls differ between iOS and Android. Some Android resume and saved-workflow dispatch paths are documented as incomplete; use the desktop when the app reports that an action is unavailable. Phone supervision does not imply complete desktop Git or editor parity.
More detail
Mobile overview · Android sessions · iOS sessions · Cloud Sync