| Primary unit of work | A worktree with its agent terminal: every task gets its own on-disk copy of the repository, and one prompt can fan out across several agents. The experimental orchestration layer adds Runs, Tasks, and Dispatches for supervised multi-agent work. | A mission: one goal with its conversation, the agents working on it, their approvals, and its record. It persists across sessions and goes idle rather than closing. |
|---|
| Execution environment | Agents run on your computer or, over SSH, on a remote machine with file editing, Git, terminals, and port forwarding; remote sessions survive closing the desktop app. Desktop apps for macOS, Windows, and Linux; iOS and Android companions pair with the desktop. | Agents run on your Mac by default. On a paid plan you can start or move a mission to Skyflo Cloud, a machine Skyflo runs for that mission, which keeps working while your Mac sleeps. Only Codex and Skyflo's own agent run there; Claude Code stays on your Mac. A mission started there from a GitHub repository opens a pull request. |
|---|
| Agent and model choice | Any agent that runs in a terminal, including Claude Code, Codex, Grok, Cursor, GitHub Copilot, OpenCode, Antigravity, Pi, Devin, Cline, and Kiro, each on its own subscription. Orchestration workers can set a model and effort for Claude, Codex, Muse, Cursor, Antigravity, and OpenCode. | Skyflo's own agent plus seven external agents: Codex, Claude Code, Cursor Agent, Antigravity, Grok CLI, OpenCode, and Pi, and one custom ACP agent added through a manifest file. External agents use their own sign-in and models; Skyflo's own agent uses included models on paid plans or your Moonshot or Z.ai key. Orchestrate runs several on one mission and can pick the lead. |
|---|
| Cross-repository coordination | Each repository has its own worktrees from a base ref, and orchestration can start a worker in a new worktree of a chosen repository on this or a connected Orca server. The reviewed sources organize that work around worktrees and tasks rather than one registered multi-repository mission. | A workspace is an ordered set of up to eight registered Git checkouts, and one mission can span them. In Skyflo Cloud a mission spans one to five. Each writing specialist works in its own worktree, so edits stay apart while the work runs; integrating them is still a change you review. |
|---|
| Approval and mutation boundaries | Each agent keeps its own permission settings in its terminal, and Orca's chat view shows an agent's permission requests and questions. Orchestration adds decision gates, coordinator questions that block a task until they are answered. The reviewed sources do not describe one access mode applied across agents. | One access mode governs every agent on a mission, Skyflo's own and the external ones. Skyflo answers each agent's permission requests by that mode and records the decision. In Full access, the default for a new Auto mission, prompts are off and folder confinement is lifted. Orchestrate starts at Ask for approval, and Plan mode waits for you to approve the plan. |
|---|
| Independent review | Line comments on an AI diff go back to the agent, pull requests and Linear issues open in the app, and racing several agents on one task lets you compare results. The reviewed sources do not define a dedicated reviewer role that cannot edit files. | In Orchestrate missions, Skyflo adds a separate reviewer by strategy and risk, and Skyflo's own agent can start one. The reviewer can read, search, ask, and report, but cannot edit files. Not every mission is reviewed, and a review is a second opinion, not a guarantee. |
|---|
| Browser, terminal, and automation evidence | WebGL terminals with splits and scrollback that survives restarts, a Chromium browser with Design Mode, computer use for desktop apps, automations, and a CLI that agents can drive with commands such as orca worktree create, snapshot, click, and fill. | Code, browser, terminal, and automations share one workspace, where you and Skyflo's own agent work in the same browser and terminal. Each mission keeps an append-only record on your Mac of approvals, Skyflo tool calls, including external agents' calls through Skyflo's tools, and review findings, every event hash-linked to the one before it. |
|---|
| Cross-mission memory, provenance, and user control | Worktrees and terminal scrollback persist between sessions. The reviewed sources do not document memory learned from completed work for later tasks. | Personal memory stored on your Mac, learned from finished missions with a link to its source. Skyflo keeps a memory when the evidence supports it; otherwise it waits for you to keep, correct, or dismiss it, and you can remove any memory later. A workflow verified in two repositories can become a Skill once you or an independent agent approves it. Reverting a Skill or a routing change alters what Skyflo does next, not past work. |
|---|
