StatusUpdated with every release

What ships today.

Every registered capability, its current status, and the code, test, or documentation behind it. No chip means the capability is available in the current build.

How to read this

Most of the site carries no status label at all. That is deliberate: the absence of a label means the capability ships in the current build. Labelling everything would make the labels invisible exactly where they matter.

Where a capability is not generally available, the label sits next to the claim on the page, not in a footnote. Nothing appears here as available unless it points at code, a test, or documentation for a shipped implementation.

Audited against skyflo-v2@6824b97a8a62601a579852df5ebf1c42d2e61445

Available

Ships in the current build. No chip is shown for these.

  • One objective, with state that survives the session.free · pro · team · enterprise
  • A workspace is an ordered set of registered Git checkouts; one mission may span them.free · pro · team · enterprise
  • Give each boundary to the right specialist.free · pro · team · enterprise
  • Each coder specialist works in its own git worktree.free · pro · team · enterprise
  • Plan mode blocks the turn until you approve the plan.free · pro · team · enterprise
  • Code, browser, terminal, and automation in one loop.free · pro · team · enterprise
  • Run Codex, Claude Code, Cursor Agent, Antigravity, Grok CLI, OpenCode, and Pi inside a Skyflo mission.free · pro · team · enterprise
  • Mistral, DeepSeek, and open-weight BYOK or local model lanesfree · pro · team · enterprise
  • Some engineering work should keep running after you close the mission.free · pro · team · enterprise
  • Scopedfree · pro · team · enterprise
  • Citedfree · pro · team · enterprise
  • Forgettablefree · pro · team · enterprise
  • Correctable before it is keptfree · pro · team · enterprise
  • What one mission learns, the next one can find.free · pro · team · enterprise
  • Skyflo learns from the missions it completes and keeps what the evidence supports.free · pro · team · enterprise
  • A workflow proven in two repositories can become a reusable Skill once another agent or you approve it.free · pro · team · enterprise
  • Skyflo can improve how it routes work, adopting a change only when it beats the current policy on past routes it was not built from.free · pro · team · enterprise
  • Approvals, credentials, spending limits, and kill switches sit outside anything Skyflo can change about itself.free · pro · team · enterprise
  • Every change Skyflo makes to itself is recorded with who judged it, and one Revert undoes it.free · pro · team · enterprise
  • One approval policy on every runtime: external agents start at maximum-ask, and Skyflo decides who answers each request and records the decision.free · pro · team · enterprise
  • An external runtime cannot start on a mission without an approved plan, and everything it is told about the mission comes from durable mission state.free · pro · team · enterprise
  • External agents reach Skyflo's tools through a per-session MCP gateway, so every call passes the same policy and approval path.free · pro · team · enterprise
  • Each mission keeps an append-only record on your Mac, with every event hash-linked to the one before it.free · pro · team · enterprise
  • Four access modes decide who answers an agent's requests. New Auto missions start with Full access; Orchestrate starts with Ask for approval. An explicit remembered choice takes precedence.free · pro · team · enterprise
  • In every access mode except Full access, external agents launch under a macOS Seatbelt profile scoped to their leased worktree and granted roots, and Skyflo refuses to launch unconfined.free · pro · team · enterprise
  • Values in deterministically sensitive files, such as keys and env files, are masked before they become model-visible.free · pro · team · enterprise
  • Secret-shaped values are redacted before anything is persisted, logged, projected, or reported.free · pro · team · enterprise
  • Every linked device, Mac or phone, is listed in the account console and can be revoked, and a revoked device's access stops working.free · pro · team · enterprise
  • Missions in the same workspace on one Mac can message each other; a message runs on the recipient's own agent, model and access, and never reaches a mission in another workspace or one with more access than the sender.free · pro · team · enterprise
  • Start a mission in Skyflo Cloud from a connected GitHub repository, or move one with its history and uncommitted changes; it keeps working while your Mac sleeps and comes back when idle.core · pro · max
  • The Mac that started or moved a mission follows its fuller Skyflo Cloud conversation, including tools, command output previews, changes and questions, without needing a paired phone.core · pro · max
  • Codex and Skyflo's own agent run in Skyflo Cloud on Skyflo's managed models, with no provider key or sign-in on the machine, and a mission keeps the agent it had on the Mac.core · pro · max
  • A mission in Skyflo Cloud runs on a machine of its own that holds no model provider key and no GitHub credential, and its network reaches only Skyflo and public package registries.core · pro · max
  • Every mission in Skyflo Cloud has a spend limit; it pauses with its work saved when it reaches it, and machine time is charged only while its machine is awake.core · pro · max
  • Connect GitHub on every plan: choose repositories on GitHub, clone one from Add project without the GitHub CLI, and push through the connection.free · pro · team · enterprise
  • An agent that writes nothing reviews the work.free · pro · team · enterprise
  • Execution stays on your linked Mac unless you move a mission to Skyflo Cloud.free · pro · team · enterprise
  • Bring your own model keys. They stay in the macOS Keychain.free · pro · team · enterprise
  • Managed inference through the Skyflo gatewaycore · pro · max
  • Talk to a running mission, and it operates the appcore · pro · max
Preview

Implemented but not yet generally usable, or usable in a limited form.

  • Pair an iPhone or iPad to follow missions, answer questions and approve actions; every decision is signed on the phone and checked by the Mac before anything runs.free · pro · team · enterprise
Planned

Designed and specified. Not implemented.

  • Organization-wide shared knowledgeteam · enterprise
  • A mission should finish on evidence, not a final message.free · pro · team · enterprise
  • Typed connectors for Kubernetes, CI, and telemetryfree · pro · team · enterprise
  • Higher usage, concurrency, automation, and retentionpro · team · enterprise
  • Team administration and policyteam · enterprise
  • Contractual security, deployment, and support controlsenterprise

Start with what ships today.

Available capabilities run in the current Desktop build. Preview and Planned rows remain labeled until their status changes.

macOS 14+. Apple silicon and Intel.