Meetings is a $35 a month add-on for a monthly Pro or Max plan, with Skyflo in one call at a time. It is not part of Team plans. Skyflo joins from Google Chrome, Brave, Microsoft Edge or Chromium on this Mac, signed in once to the Google account it uses for Google Meet; a sign-in, passcode or check a platform asks of a person is left for you.
A mission on ChatGPT or Claude shares its screen, presents, demos and uses computer use only with Full access. Computer use acts only in a mission that is carrying out work, not in Plan or Ask, and needs the Accessibility and Screen Recording permissions in System Settings.
The updated Privacy Notice describes what a feedback report from Skyflo Desktop carries: what it always includes, the conversation, screenshot, diagnostics and files that are added only when you choose them, and who can read it.
Skyflo joins your meetings on Google Meet, Zoom and Teams
Skyflo joins your Google Meet, Zoom and Microsoft Teams calls as a participant with a voice. Anyone in the call can direct the mission it is connected to, and Skyflo works on it while you talk, shows its work on screen when the room agrees, and carries on after it says goodbye.
Start free. macOS 14+, Apple silicon and Intel. Agent subscriptions and model keys you bring are billed by their providers.
See what changed 26
New
Bring Skyflo into a call from a mission's composer: paste a Google Meet, Zoom or Microsoft Teams link and choose Join call. Skyflo asks to join under its voice's name, such as Marin by Skyflo, with its orb as its camera, and the host admits it like any other guest. A meeting brief can give it the goal, the constraints, the decisions so far and how to say people's names.
Anyone in the call can direct that mission by voice: give it work, steer it, ask where it stands or stop it. The mission does the work with its own agent, tools and access, on your Mac or in Skyflo Cloud, and Skyflo tells the room the result when it is ready. Skyflo introduces itself once, then listens until someone speaks to it.
The call reaches one mission and nothing else. From the call, a waiting request can be allowed once or rejected. Wider permissions, the mission's agent, model and access, your other missions and the Skyflo window stay with you on your Mac.
Skyflo can share its screen into the call: the mission's own browser, or the one window of another app you allowed it with computer use, never the whole screen. It shares at once when the room asks to see something and asks first otherwise. It never says something is on screen until the call shows it, and stops when anyone in the call asks or you choose Stop sharing.
A mission can present to the room section by section, pausing when someone speaks and picking up after the answer. It can also demo an app live, driving the window you allowed while it talks, one step at a time, with short progress lines while slow work runs. Controls that approve, sign in, agree or pay are left for a person.
Skyflo leaves well. Hand it the next piece of work as you leave, and it confirms what it will do, says goodbye and leaves with you while the mission keeps running. When the room wraps up it says goodbye, and once everyone else has left it leaves too, without ending the call for anyone. Anyone can ask it to stop listening or to leave, by name.
When Skyflo joins, and again for people who arrive later, it posts a notice in the meeting chat: it is an AI assistant connected to the mission, what is said is sent from the host's Mac to OpenAI while it listens, and whether a transcript is kept. Skyflo records no audio or video. You can also choose to copy its spoken replies to the meeting chat.
Meetings in the sidebar keeps a record of each call on this Mac: when Skyflo asked to join, was admitted and left, and what it shared. Choose Save a transcript on this Mac before joining to keep the text of the conversation too. Search, review, export or delete a meeting there, also after the add-on ends, and the mission can read a saved transcript for the work that follows.
Computer use. In Settings › Computer use, allow one mission to work in one window of another Mac app. It reads the window, presses its buttons and types into its fields in the background, while the app you are using stays in front. It never presses a control that approves, signs in, agrees or pays. When an app needs to be in front, Allow in front for 2 minutes lets the mission bring it forward, and anything you type, click or scroll stops it.
Orchestrate runs in Skyflo Cloud. A mission there can plan the work and send out specialists, on ChatGPT and Skyflo's own agent, while your Mac sleeps.
A mission in Skyflo Cloud can ask you to approve merging its pull request, creating a tag and publishing a release. The request lists every step, you approve it in Skyflo, and Skyflo Cloud carries out exactly those steps and nothing else. Pushing to your default branch or pushing a tag directly stays refused.
Help › Send Feedback… sends Skyflo a report about the app, and the feedback button beside your account sends one about the mission you have open. Your text is required. A screenshot of the Skyflo window, redacted diagnostics and files are each off until you add them, up to four attachments, and feedback on a mission can also include its conversation. A report written while Skyflo cannot be reached waits on your Mac and sends once, by itself, when Skyflo is reachable.
The Help menu brings together Skyflo Help, Keyboard Shortcuts, What’s New in Skyflo, Welcome to Skyflo, the Troubleshooting Guide, System Status, Export Diagnostics, Contact Support and Send Feedback. System Status shows the local service, your sign-in, whether the account and model services answer, and this version's update state.
Improvements
An Orchestrate turn now shows its plan, its agents and their results in one place, with each agent's state and repository. After a run, a part that failed, was stopped or never started offers Retry this part, and the answer says in plain words who reviewed the work and how that review was independent.
A working mission can move to Skyflo Cloud without waiting for its turn to finish: Stop and run in Skyflo Cloud stops the turn here, and Skyflo Cloud picks the work up.
When a mission in Skyflo Cloud pauses at your plan's included usage, it says when usage resets, and on Core or Pro it offers the upgrade that keeps it going now. Once usage is back, Continue in Skyflo Cloud resumes it.
Settings › Providers can keep agents on this Mac to your own sign-ins, so missions here never run on Skyflo's models. Skyflo Cloud still uses Skyflo's models.
Welcome to Skyflo now walks through Orchestrate, workspaces, Voice Mode and meetings, Skyflo Cloud and the agents on this Mac before your first mission, and names only what your plan can use or add.
The composer keeps mode, access, lead and model as separate controls at every window width, and the lead control names the agent leading the mission. Specialist activity shows readable commands, tables fit the response, and an approval names who is asking once, in its title.
Agent model lists refresh from the agents installed on this Mac, so new models appear without a Skyflo update. A new terminal can open in any repository the mission works on.
Fixes
A turn that Skyflo's restart interrupted says so, and the approval it was waiting on is withdrawn, so nothing is approved after the fact. Before, it read as stopped by you and its approval stayed waiting.
After a restart, your message to a ChatGPT or Claude mission from Voice Mode, a call or the browser and terminal panes starts its session again. Before, such a message was refused.
Missions can fetch and push in repositories added through the GitHub connection, including from sandboxed specialists. Before, these failed with Repository not found.
Orchestrate agents on Skyflo's included models no longer stop on a provider refusal: each keeps its own conversation. A turn that cannot run now says why, such as no model being available or the plan's limit being reached.
A mission on an agent that Skyflo Cloud does not run, such as Cursor, stays on your Mac and says so before anything moves. Before, it could move and sit idle there.
Composer drafts come back after Skyflo restarts, menus stay open while a conversation streams, and quitting no longer stalls on an error dialog.
Steadier Orchestrate missions, specialists and composer
Specialists run Git commands in their own worktrees, hand their finished reports back to the lead on the first turn, and apply changes cleanly in Ask for approval mode. Auto missions switch leads when a lane is out of quota, and the sidebar and composer stay aligned.
See what changed 9
Improvements
Sidebar mission rows are taller with breathing room between rows and sections, aligned to a shared left edge, and keep a steady title weight when selected.
The Orchestrate menu keeps all four strategies at the same height, with an info icon beside Ensemble and Overdrive explaining when approval is required.
The composer's bottom bar stays on one line as the window narrows, truncating long workspace, branch and model names with hover tooltips, and fits all six ChatGPT reasoning levels without clipping Medium.
Fixes
Specialists running in their own Git worktrees can now run git status, git log and git diff inside the sandbox. Skyflo grants read-only access to the main repository's shared Git metadata while keeping the main working tree and branch refs protected.
When a specialist finishes, the lead receives the specialist's report and changed files as soon as its turn resumes, instead of having to poll for status again.
Specialists given relative file paths in multi-folder workspaces, or paths inside a single-repository workspace, can write and apply their changes without false out-of-scope refusals.
When a specialist finishes with changes in Ask for approval mode, Skyflo pauses for your approval to apply those changes to your working tree instead of refusing the integration.
When an Auto mission's chosen lead stops before making changes because a provider lane is out of quota or rate-limited, Skyflo switches to the next eligible lead or a ready local agent such as Claude or ChatGPT and avoids sending reviewers back to the exhausted lane.
Starting a mission with a specific model selected in Auto mode now sends from both the Send button and Command-Return, and shows why a previous attempt could not start.
Skyflo keeps your Mac awake while a task is using an app, so idle sleep or the screen lock no longer ends the work halfway. Right-click menus arrive across the app, and the composer, search and update controls are clearer.
See what changed 9
New
While a task is using an app on this Mac, Skyflo keeps the display awake so the idle lock and screensaver never start. It never unlocks anything: locking the Mac yourself still ends the task's access at once. Turn it off in Settings, Computer use.
Right-click a mission for its actions, a section heading for New mission or Mark all as read, a message to copy it as text or Markdown, and any text field or selection for the standard edit menu.
Improvements
Computer use is simpler: one App control switch in Settings, and window access is granted from the task itself with + then Use an app, bound to that task.
This Mac and Skyflo Cloud share one composer, with repository and branch above the message and agent, model and effort beside Send. While Cloud models load, the composer shows a placeholder and waits rather than accepting a message it cannot start yet.
Composer and menu icons say what they do: a bolt for Auto, a checklist for Plan, a person signing off for Ask for approval, and a plain tick on the chosen row.
The update control is one chip from start to finish: download while an update is available or downloading, restart once it is ready.
Search shows a calmer list without row icons, and menus sit on a darker, cooler surface.
The titlebar controls stay aligned at every interface zoom, your saved zoom returns after navigating, and long menu choices wrap instead of being cut off.
Editing a queued message keeps its attachments and settings, the device link dialog closes itself once linking completes, and Memory diagnostics headings no longer look like buttons.
Skyflo Cloud adds model and reasoning controls before a mission starts and for its next turn. Saved meetings read as conversations, and Settings and Memory explain failed saves, missing data and recovery.
See what changed 12
New
Choose an available model and reasoning level when starting a mission in Skyflo Cloud on Skyflo's own agent or ChatGPT. Choices follow your plan's included models and supported settings; opening the menu starts no machine.
Change the model and reasoning selection for the next message on a mission in Skyflo Cloud. The current turn keeps its model. ChatGPT reasoning is requested, with execution details distinguishing the request from what the provider confirms.
Improvements
An accepted Skyflo Cloud launch opens its conversation. Fresh conversations remain visible in order after repeated moves, and local follow-ups wait behind the conversation currently running. A refused follow-up keeps its draft and a visible explanation through refreshes.
On the Mac, the composer waits for saved mission settings before sending, keeps the draft if they cannot be read and offers Try again. Moving with an initial instruction lets you review the model and reasoning for that work. An idle move keeps the mission's existing configuration.
Tool groups expand independently and keep work you opened visible when a turn finishes. Wider mission windows keep the composer beside the browser or files panel. Plan dialogs and composer menus have solid reading surfaces, and closing them restores keyboard focus to the control you came from.
Missions, Workspaces, Memory, Meetings and Settings share updated colors, text and controls. Narrow panes reflow their controls, and long account and action menus scroll within the window.
Saved meeting transcripts keep fragments of a turn together through activity updates and display corrections. Search follows the corrected conversation across fragments, and the Meetings view and exports share the same readable grouping. Original fragments remain in JSON exports.
Prepared presentations show an editable chapter outline and let the host jump to a chapter by title or topic. A chapter whose page cannot be verified pauses before narration, with explicit options to check the browser and resume or continue with audio only.
Choose and confirm the meeting account before joining, with the participant name and voice shown separately. Google Meet uses your confirmed Google account; Zoom and Teams also offer guest mode, subject to the meeting's sign-in and admission rules.
Meeting setup keeps its brief and Join call controls reachable at enlarged interface zoom. Sign-in handoffs keep the browser page open after Voice Mode ends.
Settings search brings the matching setting into view. Failed preference saves appear beside their section with Retry save, and a failed shell-list read keeps the stored shell visible.
Memory diagnostics groups its views under Records, Review and System. Past work begins with a search invitation, empty results are distinct from unavailable data, and a failed refresh keeps the last successful read visible.
Skyflo's included models can be turned on in the app after you buy a plan. Missions stay manageable through account outages, Keychain prompts and update notices, and models recover when the Mac wakes or reconnects.
See what changed 9
Improvements
A paid plan's Skyflo models can be turned on from the app: in first run, the model menu, the composer, Skyflo Cloud and Voice Mode, through the same agreement the account console shows. Before, that first choice could only be made in the console, and a new Mac offered the plans you had already bought.
Fixes
Skyflo's models stay listed when the window regains focus, the Mac wakes or the connection returns. Before, a message sent in that moment could be refused.
A Keychain prompt never holds Skyflo's launch or turns off an activated Mac. Before, a declined or unanswered prompt could block every mission, including ones on your own keys.
When your plan cannot be read, Skyflo keeps asking until it answers. Before, a paying Mac could stay on Free, with Meetings off, until the window regained focus.
A model key whose provider could not be reached at startup is checked again on its own, and a key already proven keeps working through a failed check.
A Mac that already runs the required version is never kept blocked by an update notice, even offline, and existing missions stay manageable, Bring back included, while an update is required.
Skyflo Cloud and Meetings stay in the app during an outage and say they cannot reach Skyflo yet, then try again when chosen. A mission that could not come back from Skyflo Cloud because the Terms changed offers the agreement in place.
Ask mode runs commands in a workspace that contains a link pointing outside it, and keeps that link out of reach. Before, every command in such a workspace was refused.
A Claude install that is slow to report its version still counts as installed.
GPT-6 models, a clearer missions list, steadier calls
Missions on Skyflo's models move up to GPT-6 Luna and GPT-6.1 Sol. The missions list now leads with what is waiting on you, from every workspace. In a call, Skyflo checks your account's one call seat first, listens until someone speaks to it and says goodbye once.
See what changed 12
Improvements
Missions on Skyflo's models move up to GPT-6 Luna and GPT-6.1 Sol, in place of GPT-5.6 Luna and GPT-5.6 Sol.
Skyflo checks your account's one call seat before it opens a call. If Skyflo is already in another call on your account, nothing opens and nobody in the meeting sees a request to join. Skyflo says it is already in another call and to try again once that call ends.
In a call, Skyflo answers when someone speaks to it and stays quiet while the room talks among itself, without acknowledging remarks meant for others.
Asked to show something it cannot share, Skyflo says what it can share instead: the mission's own browser once a page is open, or one window of another app you allow in Settings › Computer use.
The saved record of a Google Meet call names who spoke.
When Meetings is set to end at renewal, the Meetings view says until when it stays on, and the call button keeps working until then. On a yearly plan, a plan set to end or a payment to fix, the call button says why Meetings cannot be added, as the Meetings page does.
The missions list in the sidebar is redesigned. Missions waiting on you for an approval, an answer, a plan to review or a decision lead it under Needs you, from every workspace. Missions at work or scheduled follow under In progress, then your pinned missions, your sections and your history.
Each mission takes one line, and a mission from another workspace names its workspace at the end. A dot marks a mission that finished or failed since you last opened it, and a turning mark one that is at work. Hover a mark to see what the mission is waiting for. A long history folds behind Show more.
Fixes
Skyflo reports a finished task as finished. Before, it could add that the work was still unverified after it had completed.
On Microsoft Teams, Skyflo's goodbye no longer begins twice, in the call or in its chat copy.
On Google Meet, Skyflo's own screen share no longer counts as someone joining, so the call's notice is not posted again.
A call page that crashes is reopened as soon as the browser reports the crash. Before, Skyflo took 13 to 17 seconds to notice, measured on a development build.
Team plans need this version of Desktop and an organization subscription. They share billing and included usage; missions, workspaces and memory are not shared between members. Voice Mode and Meetings are not included in Team plans.
Team plans and Welcome to Skyflo
Team plans bring members onto one subscription with included usage shared across the organization. Choose your organization on the Mac, manage seats and roles in the account console, and start with a welcome that checks what is ready to run.
See what changed 7
New
Team and Team Max are monthly plans for 1 to 100 people, with one organization bill and included usage shared across its members. Team carries Pro's model access; Team Max carries Max's. The checkout shows the per-person price, quantity and total before you buy.
Invite people from the account console and share their invitation link, see pending invitations, and manage owner, admin and member roles. Members and invitations count against purchased seats, and the organization always keeps at least one owner.
Review a seat change before confirming it. Added seats credit unused time and start a full new billing period, with access following successful payment. Reductions take effect at renewal and must cover members and pending invitations; new invitations also respect a scheduled reduction.
An existing paid organization can move to a Team plan through Billing, with the charge and timing shown before confirmation. The organization keeps its customer and subscription relationship; a personal subscription in another organization stays separate.
Choose the organization you are using in Desktop or the account console. Your personal subscription remains separate. Desktop waits until its missions are idle before switching, and the new organization gets its own device authorization.
Welcome to Skyflo checks the coding agents on this Mac, shows what needs a sign-in or setup, explains the active plan's limits, and takes you to a repository and a first instruction. You can skip it or open it again from Help.
Fixes
Invitation links take new members directly to account creation and preserve their invitation.
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.
Skyflo Cloud continuity on Mac
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.
Superseded by 1.5.4. Download the current version of Skyflo for Mac.
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.
Direct starts in Skyflo Cloud
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.
See what changed 10
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.
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.
Steadier missions and automatic updates
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.
See what changed 5
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 asks before it acts
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.
See what changed 7
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.
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.
Skyflo 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.
See what changed 23
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 Claude Code mission is not moved and stays on your Mac. A Codex mission keeps Codex when it moves; a mission on any other agent, Skyflo's own included, can still be moved and may continue there on a different agent, usually Codex, and the move dialog does not yet say so.
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.
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.
See what changed 6
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.
Phone 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.
See what changed 7
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.
Safer specialist work in your repositories
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.
See what changed 4
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.
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.
Co-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.
See what changed 11
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.
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.
See what changed 5
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.
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.
Voice Mode and managed models on paid plans
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.
See what changed 9
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.
See what changed 8
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.
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.
See what changed 5
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.
If you are on 1.0.7 and stuck on the offline screen, quit Skyflo and install this version.
Repairs the 1.0.7 update regression
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.
See what changed 1
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.
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.
Visible update progress and an organized mission list
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.
See what changed 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.
More 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.
See what changed 8
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.
See what changed 3
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.
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.
See what changed 1
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.
See what changed 4
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.
The Free and BYOK launch
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.
See what changed 3
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.
See what changed 3
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.
Skyflo Desktop releases that reached people on the stable update channel, with clearly labeled historical Desktop launch milestones. Each entry explains what changed for the person using the app.
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
Website, account console, privacy, SEO and internal operations updates do not appear here. Unshipped builds are not presented as released installers. Historical Desktop launch milestones are labeled. Superseded Desktop releases keep their history, including regressions and upgrade guidance.
