| Primary unit of work | An agent conversation in the editor, Agents Window, or CLI. Projects, on Premium plans and above, Teams, and Enterprise, add a coordinator that plans, delegates to agents, and keeps context over months of 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 | Local agents in the editor, Agents Window, or CLI, including worktrees and remote SSH; cloud agents in their own VMs; and self-hosted machines on your infrastructure. Since October 6, 2026 the iOS app can watch and message local agents. | 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 | Cursor's own agent, run in parallel, with models from OpenAI, Anthropic, Google, SpaceXAI, Meta, Moonshot, and Cursor, including Composer and Grok models Cursor trains with SpaceXAI. Running other vendors' agents is not documented. | 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 | The Agents Window manages agents across projects from one place, and cloud agents in multi-repo environments make coordinated changes and open a pull request in each repository they change. | 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 | Run Modes (Auto-review, Allowlist, Run Everything) govern shell, MCP, and fetch calls for local agents, with optional sandboxing and a mode that asks before reading outside the workspace. Plan Mode produces an editable plan first. Cloud agents do not use Run Modes. | 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 | Diff and pull-request review in the Agents Window, Agent Review for local changes, Bugbot on pull requests, and on Teams and Enterprise, Security Review, which reports exploitable bugs on each pull request. | 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 | Terminal execution and an agent browser tool are documented. Cloud agents attach screenshots, videos, and logs to the pull request, and Automations run cloud agents on schedules or on events from GitHub, Slack, Linear, and webhooks. | 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 | Cursor persists local chat history and SDK agent checkpoints: the CLI reopens previous chats, and SDK agents resume after a restart. Projects keep shared files where agents add what they learn, and Rules provide persistent instructions. | 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. |
|---|