One instrument. One useful task.
Prepare a remote workspace and launch an agent
Step 1: Strike the distant forge
Connect prepares cloud compute. Choose Cloud machine in Summon for a new session; workspace changes mirror automatically.
Still frames · every step is available
“Prepare a remote workspace and launch an agent.”
Connect prepares cloud compute. Choose Cloud machine in Summon for a new session; workspace changes mirror automatically.
See who does what
Choose the task, workspace and permitted scope.
Connect prepares cloud compute. Choose Cloud machine in Summon for a new session; workspace changes mirror automatically. Start here: Compute status → Connect → Ready → Summon → Cloud machine.
Confirm Ready, the session’s Runs on: Cloud machine indicator, and the actual task output.
Skyforge requires eligible paid access. This launches a new remote session after transfer.
Copy an example instruction
Illustrative task shared across these lessons. Adapt the scope and file ownership to your project. Try the complete example and inspect its tests →
Add a saved-filter control. Keep the change focused. Inspect the existing filtering behaviour, implement the control, and run the relevant checks. Ask a separate agent to review the diff without editing it. Collect its findings and resolve confirmed issues before proposing a commit.
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.
See the product guide screenshot
This screenshot is currently unavailable. Follow the written guide for the current workflow.
Illustrated explanation · The scene explains the workflow. Follow the guide to perform it in the app.
About this demonstration
Instructions reviewed against product 1.5.119. Real application frame from the Skyforge UI test fixture. This does not demonstrate a paid cloud job or agent execution.