| Primary unit of work | A chat or task that produces a reviewable result. | 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 | Locally in the ChatGPT desktop app, CLI, or IDE extension under an OS-enforced sandbox, or in Codex Cloud, where each task gets its own isolated workspace and keeps working while your computer is asleep. | 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 | OpenAI models such as GPT-6 Astra, GPT-6.1 Sol, and GPT-6 Luna, with subagents and parallel chats; local clients can also use custom providers. The desktop app imports setup and recent work from Claude Code, Claude Cowork, and Cursor. | 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 | A local project can hold several folders, and the desktop app reviews diffs across every repository in it; Codex Cloud environments are set up from GitHub repositories. | 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 | An OS-enforced sandbox plus an approval policy, with network access off by default. Permission modes include Ask for approval, Approve for me, where a separate reviewer agent decides eligible requests, and Full access; which modes appear depends on the app version, environment, and organization. | 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 | Codex reviews local changes and GitHub pull requests against repository guidance. | 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 workflows, scheduled and event-triggered tasks, a built-in browser in the desktop app, and computer use on macOS and Windows 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 | Opt-in local memories are generated from eligible prior chats, stored under the Codex home directory, and controlled per chat and globally. They are off by default. | 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. |
|---|
