Start a mission from a connected GitHub repository in Skyflo Cloud, follow its conversation on your Mac, and bring the work back to a local folder.
Upgrade notes
Skyflo Cloud requires a paid plan, managed-model access and a connected GitHub repository. Codex and Skyflo’s own agent are supported; missions run with Full access inside their Cloud machine.
Superseded by 1.5.4. Download the current version of Skyflo for Mac.
Start a mission in Skyflo Cloud from a connected GitHub repository, without a local clone. Follow its full conversation on your Mac and bring its work back to a folder you choose.
Upgrade notes
Direct starts need a paid plan, managed-model access and a connected GitHub repository. Codex and Skyflo's own agent can run there. The mission has Full access inside its Cloud machine; model use and awake machine time count toward its spending limit and the plan's allowance.
The updated Privacy Notice describes the fuller conversation relayed for the owning Mac, its retention and deletion. It is separate from the paired phone's summary.
New
Choose Skyflo Cloud on the new-mission screen, select a GitHub repository, base branch and eligible agent, and send the instruction. The mission starts there without creating a workspace on your Mac.
A mission started in Skyflo Cloud works on its own branch and opens its pull request into the base branch you chose. GitHub access stays limited to the repositories you connected and the mission's own branch.
The Mac that started or moved the mission sees its answers, available reasoning, tool calls, command output previews, plans, file changes and questions through the same conversation views as local work. This works without a paired phone; the phone keeps its separate summary view.
Bring a mission started in Skyflo Cloud back to a parent folder you choose. Skyflo clones its repositories, preserves existing folders and restores its work and conversation. Missions moved from the Mac still return to their existing local home.
Improvements
The open mission shows On this Mac or In Skyflo Cloud beside its tools. Use that control to move it or bring it back, with the transfer state visible while it happens.
Opening plans from the Cloud composer keeps your instruction, repository and branch. Returning from Billing refreshes access and never starts work on its own.
First-run setup, plan comparisons and mission briefings fit narrow windows and larger interface text more reliably. Required updates show download progress during setup.
Mission organization, Resource Manager and memory dialogs fit their frames; keyboard focus, loading states and action labels are more consistent. A stopped turn with no answer now says that it stopped.
Fixes
Bringing a mission back no longer fails when its saved continuation refers to memory recorded only on the Cloud machine. Its continuation content and mission history are preserved.
A return request and the runner renewing its authority no longer block one another until the request times out.
Missions whose agent ran curl or wget in a shell command no longer stop on Skyflo's included models or stop updating your phone. Updates now install on their own even when a stopped turn left a message waiting for you.
Upgrade notes
Skyflo asks you once to review the updated Terms and managed content disclosure. The disclosure covers Skyflo Cloud and corrects how Voice Mode context reaches OpenAI. Until you agree, work on Skyflo's included models, Voice Mode and Skyflo Cloud waits; missions on your own keys or subscriptions carry on, and no work is lost. Choose Review agreement where Skyflo asks, or agree in the account console.
Improvements
When an update has downloaded, the control beside your profile becomes a solid button with an upward arrow: press it to restart and install. Before, a green check beside a refresh arrow made a ready update look like a finished sync. While work is still running it shows as an outline with a clock, and still offers to restart now.
Installing Skyflo on a new Mac opens a window made for its one step: drag Skyflo into your Applications folder. It opens near the middle of the screen, and the instruction stays in view with the Finder path bar showing. Updates still install on their own and never show it.
Fixes
A mission whose agent had run curl or wget through a shell, as ChatGPT Codex does for every command, could stop on Skyflo's included models with a connection error and stop updating on your paired phone. Our hosting provider's firewall refused those requests before they reached Skyflo. Skyflo now sends them compressed, which passes, so the same missions carry on.
An update now installs when Skyflo is idle even if a stopped or failed turn left a follow-up message waiting. Before, that message counted as running work and kept the Mac on the older version. It still waits for you after the update.
The model picker no longer offers Z.ai models that Skyflo's included models cannot run. Auto already skipped them.
Correction, October 3: the original notes incorrectly called Ask for approval the default for every mission. With no explicit remembered choice, Auto starts with Full access and Orchestrate starts with Ask for approval. Check the composer before sending.
Skyflo's own agent now asks before it runs a command or edits a file, as Claude Code and ChatGPT Codex already did. Messages between missions stay within their workspace, and missions on included models wait out a provider's per-minute limit instead of failing.
Improvements
In Ask for approval, Skyflo's own agent asks before it runs a command, edits a file or applies a specialist's work; in Auto-accept edits it asks before commands only. Plain read commands such as ls, cat, grep and git status still run without asking. The request shows the exact command or file, reads Skyflo needs permission, and can be answered from your paired phone. Sandboxed access and Full access do not ask.
A mission sees and messages only the other missions in its own workspace on this Mac. A message never reaches a mission in another workspace.
Missions on your plan's included models now wait when a model reaches its provider's per-minute limit, instead of failing. A turn waits up to about two and a half minutes in all, and Stop ends the wait at once. Hourly and monthly limits still stop a turn straight away.
Z.ai's GLM models are no longer among Skyflo's included models, and Auto uses the remaining OpenAI and Google models. A Z.ai key of your own still works. The mainland China endpoint for your own Zhipu key is retired: a key saved for it shows Endpoint retired, and adding a Z.ai key keeps GLM models available.
Fixes
Skyflo's own agent carries on with its turn after it sends a message to another mission. Before, the message arrived but the sender's turn could end with "The model connection stopped this turn".
Missions on included models that call the model at the same moment no longer fail that way either.
Stop now withdraws a permission request the stopped turn left waiting, so an old request can no longer be approved after the fact.
1.5.0Skyflo Cloud runs missions while your Mac sleeps
Skyflo missions no longer stop when your Mac does. Run in Skyflo Cloud moves a mission there with its history and uncommitted changes, and it keeps working while the Mac sleeps. GitHub connects on every plan, and missions can message each other.
Upgrade notes
Skyflo Cloud needs a paid plan and Skyflo 1.5.1 or later; see the plans on the pricing page. Connecting GitHub works on every plan, including Free, and so does everything else on your Mac.
New
Run in Skyflo Cloud. Choose it on a mission and it moves with its history and your uncommitted changes, staged, unstaged and untracked, with no commit or push. It keeps working while your Mac sleeps or is offline. Measured on our staging service before release, a move from a Mac took 10.7 and 12.6 seconds.
The move says what goes and what stays. The whole mission goes, its conversation included, with your uncommitted changes and unpushed commits; files your repository tracks travel as they are, secrets included. Ignored files such as node_modules, untracked credential files such as .env, very large untracked files, and anything the mission was running on this Mac stay behind. Continue from the conversation so far is your choice; without it, the agent in Skyflo Cloud starts fresh from your next message and the transcript says so.
Bring back to this Mac returns the mission once it is idle, with the work it did there as uncommitted changes. Changes you made on this Mac while it was away are kept separately as Git refs, never overwritten. On staging, bringing a mission back took 5.8 seconds from an awake machine, and 39.5 and 68.2 seconds from one that had gone to sleep.
A mission in Skyflo Cloud works from your Mac like a local one. It reads In Skyflo Cloud, its conversation is live, and you can send it a message, stop it or answer its questions. Your paired phone can follow it too.
ChatGPT 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. A mission keeps the agent it had on your Mac, and if that agent cannot run there, nothing moves; Claude Code and other agents stay on your Mac.
Every mission in Skyflo Cloud has a spend limit, shown as how much of it the mission has used. A model call that would cross it is refused before it runs, and the mission pauses with its work saved. Raise the limit to continue there, or bring it back; the saved work waits 30 days. A mission left without activity for 7 days stops the same way. Machine time is charged only while the machine is awake, at about 9 cents to 1.33 USD an hour depending on what it uses, and counts against your plan's allowance with model use. There is no automatic overage.
Each mission in Skyflo Cloud runs on a machine of its own that holds no model provider key and no GitHub credential. Inside it the agent runs with Full access, whatever mode it had on your Mac, and the mission returns to that mode when it comes back. Model requests go through Skyflo's gateway, and Git goes through Skyflo with access narrowed to one repository at a time: a mission there can push only its own branch and open its pull request, never your default branch, and never a change to your GitHub Actions workflows. Bring the mission back to push such a change from your Mac. The machine's network reaches only Skyflo and public package registries such as npm and PyPI. The checkpoint that carries a mission between your Mac and Skyflo Cloud is deleted once your Mac takes the mission back, and otherwise after 30 days.
Connect GitHub from Skyflo, in the first-run setup or in Settings, Source Control, on every plan including Free. You choose the repositories on GitHub, and Skyflo never asks for a GitHub password or token. Add project can then clone a repository without the GitHub CLI, and missions on your Mac push through the connection.
Messages between missions. A coding agent Skyflo runs, such as Claude Code, ChatGPT Codex, OpenCode or Pi, can see the other missions on this Mac and send one a message, so one agent can ask another mission a question and get the answer back without you relaying it. A message lands the way yours would: it starts an idle mission's next turn, joins a running one when that agent can take it, or waits as the next message.
A message always runs on the receiving mission's own agent, model and access, never the sender's, and it cannot approve anything for you or widen what the receiving mission may do. Skyflo names the sender from its own record of the send, never from the text. A mission can never hand work to one with more access than its own, a chain of messages between agents stops at 8 until you take part, and one turn can send at most 10.
Improvements
A message you send while a mission is working now appears in the transcript as your own message. It joins the running turn when the agent can take one mid-turn, now including recent versions of Claude Code, and otherwise starts the next turn the moment this one ends. Waiting messages read Up next, with Send now and Remove.
When a mission asks for a commit, merge or push, the specialists it sends out can now do it. Each gets a full copy of the repositories it was given to change, pushes only when you asked for a push, never forces one, and Skyflo confirms the branch reached the remote.
Stop now ends everything an agent's command started, including jobs it detached with nohup, setsid or a background &. A timeout and closing a session do the same. In a test on a Mac before release, with a development build and a real ChatGPT Codex turn that started five such jobs, Stop ended all five within a second, both sandboxed and under Full access, and a process started outside Skyflo kept running.
If a process outlives a stop, the turn it belonged to says so. Under Full access, Skyflo tracks these processes through the Mac's list of running processes, which can miss one that detaches and cuts its ties before Skyflo sees it.
Stopping a ChatGPT Codex turn now stops the commands it launched. Before, Codex could report the turn stopped while its command ran on and finished its work.
In Voice Mode, a control that starts with Skyflo's name, such as "Skyflo, stop", now works as a control instead of being queued as new work, and a finished result is spoken as soon as the turn ends.
Fixes
A streamed reply from Claude Code or ChatGPT Codex no longer breaks into separate paragraphs mid-word, and Voice Mode reads the whole answer rather than its last piece. Missions already recorded that way read correctly again.
A hidden Skyflo window reconnects to its local runtime on its own. Before, one slow response while the window was hidden could leave every later action, including spoken ones, refused as offline.
ChatGPT Codex and Grok CLI sessions can now save the sign-in they refresh. Before, a sandboxed session could use up the single-use refresh token and leave Codex failing with "your refresh token was already used", in Skyflo and in your own terminal.
When ChatGPT Codex does need you to sign in again, the turn says so, with the command to run, instead of failing with an empty timeline.
ChatGPT Codex no longer asks you to approve Skyflo's own tools, such as the ones missions use to message each other. Skyflo checks those calls itself, as it already did for Claude Code.
A specialist that finishes while a Claude Code or ChatGPT Codex lead is still working now reaches that lead. Before, its result could wait until you typed again, and the mission looked paused.
Settings and the prompt for sharing a conversation with another agent use plain names, such as "Signed in with your Claude subscription" and Claude Code, instead of internal labels.
1.4.4Included models carry a mission through its tools
Missions on your plan's included models no longer stop after the agent uses a tool. Skyflo sent each tool call and each earlier answer to the model twice; it now sends them once, and the copies are no longer billed.
Fixes
On the included OpenAI models, a mission stopped with "The model connection stopped this turn" as soon as the agent needed another step after using a tool, because OpenAI refused the second copy of the call. On the shipped 1.4.4 build, the same missions complete, across several tool calls and several turns.
Gemini refused the second copy too. That was fixed on our servers on September 28 for every version; 1.4.4 stops sending the copy at all.
Gemini no longer writes its answer twice. With its previous answer sent twice, it repeated the next one in 12 of 12 trials of the same conversation, and in none once the copy was gone.
Z.ai models accepted the copies and they were counted against your included capacity. On the shipped 1.4.4 build, the same Z.ai tool step used 11,041 input tokens where 1.4.3 used 11,790.
Conversations started before 1.4.4 are repaired as they continue. The earlier copies stay stored on your Mac and are no longer sent.
A mission can move between OpenAI and Gemini models, as Auto does when it picks a different model for the next step, without stopping. Each provider now receives only its own saved reasoning. This was fixed on our servers the same day and applies to every version.
1.4.3Phone approvals that show the command and the file
Approvals on your paired phone now show what the agent would do: the exact command or the file it would edit, create or replace, and who is asking. Pairing after a Terms update lets you agree in one dialog, and missions on included models wait for capacity instead of failing.
Fixes
Approvals from Claude Code and ChatGPT Codex show on your phone what the agent would do and who is asking, such as "Claude Code wants to edit src/cart.ts": the exact command, or the file it would edit, create or replace with a preview of the change, and every file a multi-file change touches. Before, the phone showed only the kind of action, such as Edit or Bash, or an internal tool name, even when it asked for Face ID. Skyflo for iPhone and iPad is still in testing ahead of the App Store.
Approval notifications use the same plain sentence. When you choose to show only the mission and the reason, the sentence leaves out the command or the file, and a notification never shows an internal tool name.
A mission's conversation on the phone shows your answers and your guidance in order, with what happened to each piece of guidance. A turn that is waiting on you reads as waiting rather than working, and the agent is named, such as Claude Code or ChatGPT Codex, instead of Skyflo.
Mission times on the phone show when the mission last changed. Before, every mission showed when your Mac last sent it, so every row could read 1h ago.
Pairing a phone after Skyflo's Terms have been updated no longer stops at an error code. The pairing dialog says the Terms have changed, links to them, and Agree and approve records your agreement and pairs the phone in one step.
The pairing dialog explains every refusal in a plain sentence with the next step, and never shows an internal code.
Missions on your plan's included models no longer fail when they reach its limit on simultaneous model requests. They wait for capacity, for up to about two minutes, and a mission that sends out many specialists at once no longer loses the ones past the limit.
There is no 1.4.1. That build was held before release, and 1.4.2 follows 1.4.0.
Specialists can no longer remove files your repository ignores, such as .env, when their work is applied, and nothing they write can make Git run a program on your Mac. Python installed with pyenv now works for sandboxed agents.
Fixes
Applying a specialist's work no longer deletes files your repository ignores. When a specialist was given a whole folder, files it never saw, such as .env or a build folder, could be removed from your copy. Ignored files are now left alone, and one is edited only when the task names that file.
Specialists no longer fail with a change outside their scope in repositories that contain ignored build output. Build output and caches a specialist creates are recorded and not applied.
A sandboxed agent can no longer change Git's settings, hooks or the link to its repository, so nothing it writes there can make Git run a program later, in Skyflo or in your own terminal. Skyflo's own Git checks also run with those features switched off. Commits still work.
Python installed with pyenv works for sandboxed agents. python used to fail with command not found in every sandbox mode; it now runs the version pyenv selects, with read-only access to pyenv's folder.
1.4.0Co-control of the browser and terminal with your agent
You and Skyflo can now share the same browser and the same terminal. Take control of the pane an agent is using, do the part that needs a person, and hand it back; the mission carries on from where you left it. Skyflo also starts about three times faster and does less when idle.
Upgrade notes
Voice Mode still needs a paid plan; see the plans on the pricing page. Sharing the browser and the terminal with an agent works on every plan, including Free.
New
Take control of the browser or the terminal while an agent is using it: press ⌥⌘C for the browser, ⌥⌘T for the terminal, or use the bar above the pane. The agent's clicks and keystrokes stop at once, the page or shell stays exactly where it was, and it is yours until you give it back.
Continue with Skyflo hands it back, and a handback starts from what is true now rather than from where the agent left off. Skyflo reads the page you are on, or the last lines of the shell, and resumes the mission from there, so a sign-in you completed or a command you ran is what it works from next. Add a note if there is something it should know.
Agents can ask for you. When a mission reaches something only a person can do, a second factor, a payment page, a shell that wants your credentials, the bar says why and waits with the pane held for you instead of driving on.
Voice Mode reaches the same controls. "Take control of the browser", "open the terminal", "your turn" and "back to you" do what the bar does, and "start a terminal session" opens the shared shell before any work begins, so you can direct it as it goes.
What you do while you hold a pane is yours. Keystrokes made during your turn never reach the agent, and a page it later reads has tokens and credentials stripped from its address before the model sees it.
Improvements
Skyflo starts about three times faster. On an Apple silicon Mac, the signed 1.4.0 build reaches its window in 1.0 seconds where 1.3.0 took 3.1, and the local runtime is connected in 2.0 seconds instead of 3.9. The runtime compiles only what a launch needs, starts alongside its helpers instead of after them, keeps its compiled code between launches, and the window no longer waits for saved state to load.
An idle Skyflo does less. The mission list is fetched once and again only when something changed, the sidebar no longer redraws every couple of seconds, and hovering a mission no longer stalls the app. In the development benchmark behind this release, with 30 missions loaded, idle CPU fell from 3.3% to 0.7% of a core and memory across all Skyflo processes by about 100 MB.
Replies land sooner. The same benchmark measured message sent to reply finished at 116 ms instead of 190 ms; opening a mission now reads it once instead of twice, and switching missions no longer re-renders the open conversation.
Fixes
"Continue", "done" and "your turn" are ordinary words again unless you are holding a pane. They no longer end a Voice call or get swallowed as a handback.
The bar above a shared pane no longer shows another mission's request, and Take control no longer aims at another mission's shell.
A hung helper can no longer outlive the app: quitting now force-stops a runtime or process runner that ignores the polite signal.
1.3.0Pair a phone and approve missions from anywhere
Your Mac can now pair a phone. Skyflo for iPhone and iPad follows the missions running here, answers their questions and approves their actions from wherever you are. The phone app is in testing and arrives on the App Store after Apple's review.
New
Settings, Devices, Pair a phone. Type the code the phone shows, check that it is the phone in your hand, and approve. A paired phone sees this account's missions within a few seconds, and removing it here cuts it off.
Answers, guidance and approvals sent from the phone are signed on the phone and checked by your Mac before anything happens, and an approval applies only to the exact action you reviewed. Agents, repositories and execution stay on your Mac.
While a phone is paired, your Mac shares what the phone needs to show your missions: each mission's title and status, and the conversation of one you open there or one that is waiting for you. With no phone paired, it shares none of it.
Fixes
A mission that resumes after Skyflo restarts goes back to the agent you chose for it, instead of continuing on the built-in one.
While an agent waits for your approval, Skyflo no longer keeps your Mac busy checking on it.
Skyflo has a voice. On a paid plan you can talk to it while it works, and it operates the app you are looking at. Paid plans also bring the models with them.
Upgrade notes
Voice Mode and the included models need a paid plan, and that rollout is by invitation to begin with, for verified businesses in India and the United States. Free keeps everything it had, including missions on your own provider keys.
New
Voice Mode. Talk to Skyflo while it works, and it answers. It opens the pane it is talking about, starts missions, queues follow-up work, drives the in-app browser and runs terminal actions, rather than only describing them.
It goes quiet the moment you talk over it, and it carries the conversation across a change of voice instead of sounding like a dropped call. Ask for a different voice by name and it changes.
Paid plans bring the models. Core, Pro and Max each carry a monthly allowance, drawn on a catalogue of seven from OpenAI, Google and Z.ai, so there is no separate provider key to bring. Core reaches five of them; Sol and Astra are what the higher plans are for.
Adaptive chooses the model from what the mission needs rather than working down a price list. On Max it escalates to the most expensive model in the plan when the work justifies it, and declines to when it does not.
A Usage page with two meters: mission capacity, which every plan has, and managed capacity, which the managed models and Voice draw on together. It shows a share and a reset time, and no amount of money anywhere.
The model menu groups by where a model comes from and folds away the rows you have no key for.
Fixes
Voice no longer reports that your time is up when the other end simply ended the conversation.
The model menu no longer hides the model you have selected.
An abandoned reservation is no longer counted against your allowance. It could make Voice refuse to start while the Usage page still showed the same allowance as free.
Skyflo is now a HyperAgent. It learns from the missions it completes, carries that knowledge into future work, turns workflows that prove themselves into Skills, and improves how it improves, inside boundaries it cannot change.
New
Memory is on in the Mac app. When you state a convention or a correction, such as the commands to run before a commit, Skyflo keeps it for that repository and applies it in later missions there.
A workflow that succeeds in two of your repositories can become a Skill. It has to be approved first, by another agent or by you, and then you can call it from the / menu in that repository.
Skyflo can also improve how it chooses the agent and model for a mission when you let it pick. A change is adopted only if it beats the current choice on past missions it was not built from, and it is halted automatically if it later stops beating it. Skyflo can raise the bar a change has to clear, never lower it.
Approvals, credentials, spending limits, and kill switches sit outside anything Skyflo can change about itself. Only a signed release from Skyflo changes them, and the agent that proposes an improvement never judges it.
The Memory page shows what Skyflo has learned, what is waiting for your review, and a timeline of every change. Each memory opens into its sources and history, and you can remove or erase it.
Improvements lists every change Skyflo has made to itself and who judged it, with one Revert on the change in effect.
Improvements
Two settings govern memory: Use memory in tasks decides whether what Skyflo learned reaches a mission, and Learn automatically decides whether it learns at all.
The unread bell shows a dot, and a specialist's hand-back appears under the work it belongs to.
1.0.9Clearer menus and consistent keyboard shortcuts
With update recovery repaired, this release refines everyday work: clearer composer menus, consistent keyboard shortcuts, and a sidebar that stays readable at larger text sizes.
Improvements
Work mode and approval menus use clearer rows, descriptions, and selection states.
Keyboard shortcuts share one treatment across the app and shortcut settings.
Mission groups and sidebar headings have more consistent spacing and backgrounds.
Fixes
Work mode and approval menus take keyboard focus when opened, so their choices can be reached without returning to the message field.
Mission group headings no longer clip at larger text sizes.
Repairs the update regression in 1.0.7 that could leave Skyflo offline on every launch. The progress, recovery, and mission-list improvements from that release are all included.
Upgrade notes
If you are on 1.0.7 and stuck on the offline screen, quit Skyflo and install this version.
Fixes
Updating from 1.0.2 or 1.0.3 could leave part of the previous installation running and prevent Skyflo from starting. The update now clears that conflict and starts normally.
1.0.7Visible update progress and an organized mission list
Superseded by 1.0.8. Updating to this version from 1.0.2 or 1.0.3 could leave Skyflo offline, because a background helper from the older installation stayed running and this version could not replace it. Install 1.0.8 instead.
With orchestration more reliable, the focus turns to keeping Skyflo up to date: visible download progress, clearer recovery, and a more organized mission list. An upgrade regression was subsequently repaired in 1.0.8.
Improvements
An update shows real download progress instead of a stalled Downloading label, with the same progress you see in the sidebar.
The mission sidebar reads as one list grouped by day, with search and filters inline at the top.
A workspace badge appears only when a mission from another workspace needs your attention or is still running.
Fixes
If an update leaves Skyflo unable to open your missions, the recovery screen now offers a working way forward rather than a dead end.
Skyflo no longer waits on a local runtime that has already failed to start.
Updates are checked for compatibility with existing mission data before publication.
Signing in no longer gets stuck repeating a Keychain prompt, and an unanswered prompt is no longer reported as an invalid activation key.
When the account service cannot be reached, Skyflo says what actually happened instead of showing a network library's internal wording.
1.0.5More dependable orchestration and clearer failures
Delegating a mission becomes more dependable. Skyflo honors your choice of lead, carries accepted specialist work through recovery, and makes failures easier to understand.
Improvements
Orchestration lead choices show the runtime version Skyflo detected for each harness.
Specialists find the development tools configured on your Mac more reliably.
Settings status regions are named independently, so a screen reader announces which one it is reading.
Fixes
An explicitly chosen orchestration lead now runs instead of being replaced, and a slow probe or a cold catalogue no longer disqualifies one.
If a specialist route fails, Skyflo explains what happened without treating the entire mission as a failure.
Specialist context carries into a route that has to be repaired, and accepted specialist work is integrated back across every strategy.
Sign-in recovers when this installation cannot use its stored device key, instead of stopping at an invalid activation.
Read-only specialists can start reliably without gaining permission to change your project.
Now that missions start with the right model access, completion notifications become quieter: Skyflo keeps silent when you are already watching and brings missed results to your attention when you return.
Fixes
A completion you miss while Skyflo is in the background appears once when you return.
A completion in another mission still notifies you, and your notification preferences are respected.
Resumed and deleted missions no longer leave a stale completion reminder behind.
1.0.2External coding agents use their own model access
Getting started with your existing coding agents is simpler. A mission using an external harness no longer asks for separate Skyflo model access it will not use.
Fixes
Missions using an external harness or an automatically selected lead use that agent’s own model access. You still need to sign in to the chosen agent before it can run.
The Free and BYOK launch reaches its first published 1.0 installer. Guided activation gets your Mac ready for its first mission, and existing coding agents are discovered more reliably.
Improvements
Guided first-run activation connects your Free account before you start a mission.
Apple silicon and Intel installers bring the Free lane to Macs running macOS 14 or later.
Fixes
Codex installed through npm is found through its underlying executable.
Background health checks preserve the verified capabilities of an unchanged coding agent, so it stays available for your next mission.
Free and BYOK launch milestone. The first published 1.0 installer followed in 1.0.1 on September 6.
Skyflo opens its public Free lane around the tools and model access you already have. Bring your projects, connect your own provider keys or coding agents, and run engineering missions on your Mac without a paid Skyflo plan.
New
A Free Skyflo account, with no credit card required, becomes the starting point for Desktop missions.
Bring your own keys (BYOK) or use supported coding agents with their existing model access.
Your repositories and mission execution stay on your Mac. Skyflo-managed inference and paid plans remain unavailable at launch.
The Desktop foundation arrives on Mac: a signed, notarized app bringing the local runtime, account linking, workspace orchestration, and automatic updates together.
New
Native Apple silicon and Intel builds, Developer ID signed, hardened, and Apple notarized.
Local runtime, account linking, and workspace orchestration on your Mac.
Bring-your-own-key model routing, automatic updates, and privacy-safe diagnostics.
Every Skyflo Desktop release that reached people on the stable update channel, plus clearly labeled product launch milestones. Read oldest first to follow how the product develops; each entry explains what changed for the person using it. Purely internal work is left out.
When notes are published
With the release. Historical omissions may be filled from release records, commits, and confirmed launch dates. Reconstructed milestones are labeled and do not imply an installer was published on that date.
What is not here
Unshipped builds are not presented as released installers. A launch milestone may be documented even when its tagged installer remained a draft. Releases that reached people and were later superseded keep their history, including regressions and upgrade guidance.
