| Primary unit of work | A coding session or delegated task. Projects, in public beta on Pro and Max and rolling out gradually, add one ongoing conversation that coordinates parallel threads with shared instructions and memory. | 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 | Terminal, IDE, desktop, web, mobile, GitHub, and Slack surfaces; local sessions, cloud sessions and routines on Anthropic-managed infrastructure, and self-hosted environments in public beta. | 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 | Claude models only: in every approach the workers are Claude sessions, and other tools join as MCP servers. Subagents, agent view (research preview), agent teams (experimental, off by default), dynamic workflows, and Projects (public beta) run work in parallel. | 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 | Additional directories can broaden a session, and Projects can take one goal across many repositories, with a thread and pull request per repository. | 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 | Permission modes run from Manual to bypass permissions. Plan mode keeps edits blocked until you approve the plan, and auto mode, where a classifier reviews actions, is the starting mode for interactive terminal and VS Code sessions on recent versions. | 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 | Subagents can be limited to read-only tools, and the built-in Explore and Plan agents cannot write or edit files; review can also run as a separate task. | 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 sessions, a Chrome integration, a browser pane in Desktop, computer use (research preview on Pro and Max, macOS in the CLI and macOS or Windows in Desktop), scheduled tasks, and cloud routines (research preview) are documented. | 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 | CLAUDE.md instructions and auto memory, notes Claude writes from your corrections, persist across sessions on the same machine; subagents and Projects can keep their own memory. | 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. |
|---|
