| Primary unit of work | A persistent thread with messages, activity, checkpoints, diffs, and provider session state. Several threads can run in parallel. Since v0.1.0 a thread can delegate tasks to child threads on other providers, fork, and switch provider between turns with a budgeted handoff. | 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 the machine hosting the T3 Code server. macOS, Windows, Linux, web, iOS, and Android clients connect locally or remotely through T3 Connect, network pairing, or desktop-managed SSH. The host must stay running and reachable. | 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 | Stable v0.1.1 supports Codex, Claude Code, Cursor, Grok Build, OpenCode, Antigravity, and Pi, with Muse Code as a beta integration, plus ACP Registry agents and local ACP commands. Each uses its own sign-in and model access. | 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 the managed models every paid plan includes, or your Moonshot or Z.ai key. Orchestrate runs several on one mission and can pick the lead. |
|---|
| Cross-repository coordination | Threads can use separate worktrees, an existing checkout, or no project, and orchestrator V2 can give a delegated child its own worktree. The reviewed sources organize that work around threads and projects 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 | Supervised, Auto-accept edits, Auto, and Full access map to provider-specific permission behavior; the initial default is Full access and can be set per environment or project. Delegated children inherit modes unless overridden, a thread cannot message another with broader permissions, and agents cannot approve their own permission requests. Plan mode is a separate legacy setting. | 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 review, comments sent back to the agent, checkpoints, and pull-request workflows. Orchestrator V2 runs delegated review rounds on another provider or model. The reviewed contract does 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 | Terminals, a shared browser, iOS and Android simulators on the host, source-control integrations, and usage reporting. Since v0.1.0, scheduled tasks run on the server, including webhook triggers, and delegated tasks can watch pull requests. | Code, browser, terminal, and automations share one workspace, where you and Skyflo's own agent work in the same browser and terminal. On paid plans, missions sign in to websites with your saved sign-ins, passwords kept in the Keychain, and agents can work in any Mac app through Skyflo Computer Use, stopping before a submit, send or payment outside Full access. 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 | Threads, checkpoints, drafts, and provider session state persist, and interrupted threads can continue after a restart. Handoffs and forks carry selected conversation context between providers. The reviewed sources do not document a separate layer that learns source-linked memory from completed threads for later work. | 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, and you can also teach a Skill a task once, by showing it, saving a finished mission or attaching the steps. Reverting a Skill or a routing change alters what Skyflo does next, not past work. |
|---|
