Run agents remotely

Use managed Skyforge compute when you want an agent's work to run on a cloud machine.

Before you start

Sign in and check Armoury → Account & Sync for Remote Compute availability, plan access and billing state. Skyforge requires the relevant entitlement and available allowance. Know which repository state, environment and agent authentication the remote task needs.

Start a Skyforge session

1. Open the compute-status chip at the top right of the app. Before connecting it reads Local; its tooltip is The Skyforge.
2. In The Skyforge — Remote Compute, choose Connect. The app prepares the machine, copies the workspace and establishes its connection. Inspect the actual progress; closing this panel does not cancel setup.
3. Wait for Ready. The panel's Link, Machine and Sync views show the connection, machine and workspace state. Resolve any access or agent-setup requirement shown by the app.
4. Open Summon. Check Where agents run and choose Cloud machine for the new agent. When no cloud machine is usable, the control explains why only This machine is available.
5. Confirm the intended agent and working directory, then give it the task. Check the session's Runs on: Cloud machine indicator.
6. Keep track of the task's output and tests. A paired phone can follow the supported remote workflow while the responsible host and connection remain available.

The launch choice affects new agents. It does not teleport an existing local process to the VM. Ready cloud compute may become the default for new launches, so always inspect the selected destination.

Inspect changes locally

The Sync view states Remote changes mirror automatically. Check its actual status and resolve conflicts or failures before relying on the local copy. Ask a local agent in the intended repository to show git status --short and git diff in its terminal, then review the intended changes and test results before committing.

If a connection is interrupted, follow the recovery actions displayed by the app. It can offer Connect again or a guarded route to switch the workspace to this desktop. A visual status change alone is not evidence that every remote change was preserved.

Older instructions: “Ignite”, “Send to Forge” and “Recall to Local” describe an earlier interface. The current flow uses Connect, automatic mirroring and the actual recovery controls shown in your build.

Example instruction

In this Skyforge workspace, run the integration checks for the settings change. Report the working directory, failures and final result. Leave any generated report in the workspace so I can review it locally.

Check the result and finish safely

Confirm that the session runs on the cloud machine, that its files and checks match the intended workspace, and that the mirrored local changes are ready to inspect. Keep the required machine available for long tasks; allowance and automatic stop policies can affect unattended work.

Read the current machine and billing state before ending remote work. Destroy removes the cloud machine. It is not a pause button. Preserve required work first, and follow any decision card about changes that could not be verified. Do not assume closing the panel or browser stops provider charges.

Use an existing SSH server

For an ordinary SSH session, open Bash Terminal and use your established SSH connection command. This can run remote shell commands and an agent installed on that server.

That shell is not automatically a managed Skyforge workspace. Code Overlord does not document the same integrated arbitrary-host worktree, editor and multi-client server workflow as Orca. Do not assume phone session discovery, file transfer or remote-agent tool routing will work just because SSH connects.

More detail

Cloud Sync and Skyforge · Control agents from your phone

The current control names were checked against the compute-popover actions, launch-target controls and workspace-sync presentation in source version 1.5.119 on 5 September 2026. Existing screenshots elsewhere in the guide may show earlier builds.