Your existing access
External agents run on their own subscription or setup. Skyflo's own agent can use your Moonshot or Z.ai key on any plan, Free included; the key stays in your Keychain.
Model keys and supported agentsThe agentic operating system for your company
Give Skyflo a goal. It brings Claude Code, Codex, Cursor and its own agent together to plan, build and review work across your repositories. You control access, follow progress and keep what each mission learns.
Multi-agent orchestrationPreview
Start free with the agents you already use. No card. macOS 14+.Agent subscriptions and model keys you bring are billed by their providers.Plans and pricing


Skyflo for Mac. The iPhone app is a Preview, in App Store review.
Internal demonstration on Skyflo for Mac 1.5.4. Not a customer result.
Give Skyflo a goal you would hand to a capable engineer. One repository and one agent are enough to start.
Coordinate a feature across the frontend, API and SDK. The plan and the shared interface stay together while specialists work in separate worktrees.
What you get
A change in each repository, the contract they share and the checks that ran.
Carry the migration's exceptions and reasoning between passes, so the next agent continues with the context it needs.
What you get
Mechanical call sites done, and each exception listed with its reason.
Plan with one, build with the other, then ask for a second opinion. Switch agents between turns without starting a new mission.
What you get
One mission and one record of which agent did what.
More agents should mean less coordination. Each tool keeps its own history. Skyflo keeps the goal, context and permissions together as the work moves between them.
Skyflo control plane
Holds the mission, whichever agent runs it
Skyflo's own agent
When you switch to another provider's agent mid-mission, Skyflo asks before sharing the conversation. A custom ACP agent can join through a manifest file, and every external agent reaches Skyflo's tools through the same approval path.
External agents run on their own subscription or setup. Skyflo's own agent can use your Moonshot or Z.ai key on any plan, Free included; the key stays in your Keychain.
Model keys and supported agentsCore, Pro and Max add Skyflo-managed models with no key to bring, plus Voice Mode and Skyflo Cloud.
Compare models and capacityAgent subscriptions and model keys you bring are billed by their providers.
Using them directly or through Skyflo:Claude CodeCodexCursor
Start a mission in Skyflo Cloud from GitHub, or move one from your Mac. It keeps working while the Mac sleeps, and you bring the work back when it is done.
Included with Core, Pro and Max.

Delegate the whole task, or work through it together. Either way the conversation, the files and the record stay in one mission.
Skyflo's own agent works in a browser and terminal you can see and use. Step in when it needs you, then let it carry on in the same mission.
Take over, hand backTalk through a goal, ask how a mission is going or redirect it while it runs. Spoken requests stay inside the mission's access.
Core, Pro and Max
See Voice ModeAsk Skyflo's own agent to run something daily, on chosen weekdays or once. It runs while Skyflo is open on your Mac.
What Skyflo's own agent can useCodex, Claude Code and the other external agents keep their own tools, and reach a fixed set of Skyflo tools through the mission's approval path. The shared browser and terminal belong to Skyflo's own agent.
Skyflo keeps what finished work proved, with a link to its source, and brings it back when a later mission needs it.
Organization-wide shared memoryPlanned
Skyflo improves how it improves. It can change how it routes Orchestrate missions, but only after a change passes an evaluation it cannot influence. Approvals, credentials and spending limits stay outside its reach.
Conventions you state and commands that worked become memory, linked to their source. A sequence proven in two of your repositories can become a Skill once approved.
Task layer · memory and Skills
On Orchestrate missions, Skyflo can change how it picks the agent and model. A change is kept only if it wins on routes it never saw, and halted if it stops winning.
Meta layer · routing, judged on held-out routes
Approvals, credentials, spending limits and kill switches are out of its reach; only a signed release changes them. Reverting an improvement changes what Skyflo does next, not work already done.
Root layer · changed only by a signed release
Choose an access mode for each mission. It applies to every agent in it, and Skyflo records each decision.
Access mode
Applies to every agent in the mission
Every command and edit stops and waits for you.
New Auto missions start in Full access and Orchestrate starts in Ask for approval. Change it in the composer before you send.
Work mode
Each writing specialist works in its own Git worktree, so its edits stay out of yours while the work is in progress. You review and integrate them through the mission.

A separate reviewer can read the work and report findings without editing a file. Orchestrate adds one by strategy and risk, and Skyflo's own agent can start one.

Permission decisions, Skyflo tool calls, including external agents' calls through Skyflo, and review findings stay in one append-only record on your Mac.

Use Skyflo for your own work today. When your team wants to evaluate it, bring one objective and a few engineers.
Install Skyflo, connect an agent you already use and give it one real task. It keeps the mission, the record and what it learned for the next one.
Free, no card. Agent subscriptions and model keys you bring are billed by their providers.
Evaluate Skyflo in a pilot on the current product. We plan it with you:
Each engineer uses Free or an individual paid plan.
Team administration and organization-wide memoryPlanned
Engineering is the first application of Skyflo's operating system. Missions that persist, agents that coordinate, context that carries forward and access you control. We are building that foundation for more of a company's work, and each new capability will be labelled as it arrives.
Agents run on your linked Mac unless you start or move a mission to Skyflo Cloud. BYOK credentials stay in the macOS Keychain.
See what ships todayToday
Next for teams
Skyflo is the agentic operating system for your company, starting with engineering. You give it a goal, and Skyflo's own agent or the coding agents you already use, like Claude Code and Codex, work on it in one mission that keeps its conversation, access mode and record. Skyflo remembers what finished missions proved.
Software work: changes that cross repositories, migrations, and tasks that benefit from more than one agent. Skyflo's own agent also works in a browser and terminal beside you. Orchestrate, which runs several agents on one mission and can add a reviewer, is in Preview. See the use cases.
No, and you can keep using them directly. Skyflo runs Codex, Claude Code, Cursor Agent, Antigravity, Grok CLI, OpenCode, Pi and one custom ACP agent on their own sign-ins, and adds a shared mission, one access mode, a record and personal memory around the work. You can switch agents between turns; Skyflo asks before sharing the conversation with another provider. Use Codex and Claude Code together.
That depends on the access mode you choose for the mission: Ask for approval, Auto-accept edits, Sandboxed access or Full access. It applies to every agent in it, and each decision is recorded. New Auto missions start in Full access, and Orchestrate starts in Ask for approval. Choose Plan mode to approve a plan before any change is made. How access and approvals work.
On your Mac by default, in your repositories. Model requests go to the provider of the lane you choose: a signed-in agent, your own key, or a paid plan's included models. On a paid plan you can also run an eligible mission in Skyflo Cloud, so it keeps working while your Mac sleeps. Missions there run on Codex or Skyflo's own agent; Claude Code missions stay on your Mac. See the plans.
Every supported external agent, Skyflo's own agent with your Moonshot or Z.ai key, missions, Orchestrate (Preview), personal memory, Skills, automations and the GitHub connection. Start with an account and no card. Agent subscriptions and model keys you bring are billed by their providers. Core, Pro and Max add included models, Voice Mode and Skyflo Cloud. See the plans.
Yes, through individual accounts and a pilot on the current product: one objective, two to five engineers and success criteria we agree with you. Team administration, organization-wide memory and contracted enterprise controls are Planned. Tell us your requirements before assuming a company-wide deployment fits. Skyflo for teams.
The objective, plan versions and approvals, every permission decision, Skyflo's tool calls, including the ones external agents make through Skyflo's tools, any reviewer's findings, and what was learned, with sources. It does not capture every step inside an external agent. The record stays on your Mac, append-only, each event hash-linked to the one before it, which shows corruption, gaps and reordering but does not stop someone who can rewrite the whole store.
What a finished mission taught, such as a convention you stated or a command that worked, linked to its source. Memory the evidence supports is kept; the rest waits for you. You can correct a record before it is kept, remove any record later, or turn learning off. Personal memory stays on your Mac and does not travel to Skyflo Cloud. Organization-wide shared memory is Planned.
Yes, up to eight registered Git checkouts on the Mac. Each coding specialist works in its own git worktree, so edits in progress stay apart. Bringing them together is still a change you review, and a shared contract can still need a decision.
Skyflo for iPhone and iPad is in Preview and in App Store review, so it is not available to download yet. Once paired, it follows your missions, answers their questions and approves or declines actions. Your Mac checks every decision before anything runs.
Oct 03 · 4 min
A mission can begin in Skyflo Cloud without cloning its repository on your Mac first. The useful boundary is the mission: its instruction, branch, work and conversation stay together wherever it runs.
Read the entry
Oct 02 · 11 min
Skyflo 1.5 introduces Skyflo Cloud: a mission moves from your Mac with its history and uncommitted changes, keeps working while the Mac sleeps, and comes back when it is idle. How the handoff keeps one owner at a time, what the machine holds and what it can reach, and what the work costs.
Read the entry
Oct 01 · 4 min
An agent can understand your permission and still reach the wrong execution path. Skyflo 1.5.1 carries the mission's approval policy to the command and file change itself, while messages from other missions keep their own identity and limits.
Read the entry
Looking for the Kubernetes agent? It is a separate Apache-2.0 project, deprecated since October 2, 2026, with its own pages and docs.
Start with something you already need done. Run it through Skyflo, read the result and decide where it belongs in your work.
Start free, no card. Agent subscriptions and model keys you bring are billed by their providers. Paid plans add included models, Voice Mode and Skyflo Cloud.