Start directly in Skyflo Cloud
On the new-mission screen, choose Skyflo Cloud. Select a repository shared through your GitHub connection, its base branch and an eligible agent. Write the instruction and choose Start in Skyflo Cloud. You do not need a local workspace or clone first.
If a repository is missing, use Choose repositories on GitHub to review the connection's access. Leaving the branch unchanged starts from the repository's default branch. The mission works on its own branch and opens its pull request into the base you chose.
Opening plans preserves the instruction and repository choices. Returning from Billing refreshes access and never starts the mission for you. Review the access and spending notice before starting.
Move a mission from the Mac
Skyflo Cloud runs an eligible mission on a machine Skyflo operates for it, including while your Mac sleeps. It requires a paid plan, an available account, the current agreements and managed model access. Only Codex and Skyflo's own agent are offered there. Claude Code missions stay on the Mac.
Wait until the mission is idle and answer outstanding requests. Open On this Mac beside the mission tools, or its actions menu, and choose Run in Skyflo Cloud. Give an optional next instruction. Choose Continue from the conversation so far only if you want the agent to receive that history for continuity.
Review the move
The mission record, uncommitted changes and unpushed commits can travel. Ignored files, untracked credential files, some large files and processes running on the Mac do not. Review the reported omissions. Processes owned by the mission on the Mac stop during the move.
The history-sharing choice controls what is replayed to the agent. It does not mean the mission record stays off Skyflo's service when you move the mission.
Access and cost
Inside its machine the mission runs with Full access. GitHub writes remain restricted to its own branch and pull request. Model use is Skyflo-managed even if the mission used your own key or subscription on the Mac.
Review the displayed spend limit before starting or moving. Machine time and model work consume the managed allowance. Raising a mission limit does not increase that allowance or lift an organization daily limit. The Mac's explicit spend control is required to raise it.
Published machine pricing is $0.07 per CPU-hour, $0.04375 per GB-hour of memory and $0.00683 per awake hour for hot storage. The total awake-hour rate is bounded between $0.089955 and $1.3283. See the Terms for the measurement and billing rules; this is not a promise of a fixed machine size.
Follow the work from your Mac
The Mac that started or moved the mission can follow its conversation, including answers, available reasoning, tool calls, command output previews, plans, changes and questions. Send guidance, answer a question or stop the turn from that conversation. A Cloud file change opens its relayed contents rather than a same-named local file.
This fuller view is separate from the paired phone's summary. It works without a paired phone. If the connection drops, the mission can keep working in Skyflo Cloud; reconnect before assuming the view is current.
Bring work back
When idle, open In Skyflo Cloud beside the mission tools and choose Bring back to this Mac. Let the transfer finish and inspect the returned files. A mission started in Skyflo Cloud asks where to clone its repositories on this Mac. Review the destination and choose another parent folder if needed. Existing folders are preserved. A mission you moved from the Mac returns to its existing home and restores its prior Mac access mode. If the return fails, read the recovery state before retrying; a pending transfer is not a completed return.
Work retained remotely has retention limits. Return promptly when you need a durable local copy. The current Privacy Notice describes what is retained and when it is deleted.