You want a coding agent to fix a repository while your Mac is closed. Cloning that repository onto the Mac, creating a workspace and starting the mission here adds steps before the work reaches the machine that will run it.
In The Mission Outlives the Laptop, we described a mission moving from your Mac to Skyflo Cloud with its history and uncommitted changes. That move matters when work has already started here. A new mission can begin where you want it to run.
Desktop 1.5.3 adds that starting point. On the new-mission screen, choose Skyflo Cloud, a repository shared through your GitHub connection, the branch to start from and the agent. Write the instruction and start it. There is no local folder to add and no local clone to wait for.
Choose the Branch Before the Work
The base branch is part of the instruction's context. A fix for a release branch needs that branch's code, and its pull request should land there too.
Skyflo starts the mission from the branch you choose, or the repository's default branch when you leave it unchanged. The mission gets its own branch. When its work is ready, Skyflo Cloud commits and pushes that branch and opens its pull request into the chosen base. You review the result on GitHub.
The GitHub connection still determines which repositories Skyflo can reach. A missing repository leads back to GitHub's own access screen. The machine running the mission holds no GitHub credential, and its Git access permits only its own branch and pull request. It cannot merge the result or push your base branch. Changes to GitHub Actions workflows still need a push from your Mac.
Keep the Work Visible
A final answer is one part of a coding mission's record. The command that reproduced the problem, its output, the file change and the next test explain how the agent reached that answer.
The Cloud mission's conversation on the Mac uses the same views as a local mission: answers, reasoning when the agent provides it, tool calls, command output previews, plans, changes and questions. A mission running somewhere else should still be possible to inspect while it works. Opening a Cloud file change shows the relayed change; it does not act on a same-named file in your Mac's workspace.
The fuller conversation copy is for the Mac that started or moved the mission. It works without a paired phone. The paired phone keeps its smaller summary view. The Privacy Notice names what Skyflo relays and how long it keeps that copy.
Bring It Home When You Need It Here
A mission started in Skyflo Cloud has no original local folder. Bringing it back therefore includes a destination choice. Skyflo shows where it will clone the repositories, lets you choose another parent folder and keeps any folder already there by choosing a new name beside it.
The checkpoint carries the mission's work and conversation back with the repositories. From there, the mission continues on your Mac. A mission you first moved from your Mac still returns through its existing local home.
The Boundaries Stay Visible
Skyflo Cloud comes with paid plans and uses the plan's included models. ChatGPT Codex and Skyflo's own agent can run there. Claude Code and other agents remain available on your Mac.
Inside its Cloud machine, the mission runs with Full access. Its model use and awake machine time count against the mission's spending limit and the plan's allowance. The launch screen states those consequences before you start. Opening plans keeps the instruction, repository and branch you chose, and returning from Billing starts no work on its own.
The Mac remains the default place to run a mission. Skyflo Cloud gives you another place to start, while the mission remains the unit you direct, inspect and bring home.
The release notes record the Desktop changes, and the pricing page shows what each plan includes.