Watch the film: Skyflo joins your meetings
Most of a company's decisions are made out loud. A release review settles what ships. A standup finds the blocker. A customer call agrees on the fix. Then the call ends, and the work starts somewhere else, later, from somebody's notes.
Skyflo 1.7 closes that gap. From a mission, bring Skyflo into a Google Meet, Zoom or Microsoft Teams call, and it joins as a participant with a voice. Anyone in the call can give it work. It does that work in your Skyflo workspace while the conversation goes on, shows the room what it did when the room wants to see it, and when the call wraps up it says goodbye and keeps going.
Skyflo is the agentic operating system for your company. Meetings brings it into the room where much of that company's work is decided.
A Call, From the First Hello
Here is how a call goes. Your team meets at ten to decide whether the billing release goes out today, and you already have a mission for that release. It knows the repositories, the branch and the agent doing the work.
Open that mission and choose Bring Skyflo into a call, beside Voice Mode in the composer. Paste the meeting link, and Skyflo reads it back: the platform, the meeting code and whether the passcode came with it. If you want, open Meeting brief and write the goal, the constraints and the decisions already made, with how to say the names of the people who will be there. Choose whether to Save a transcript on this Mac and whether to Copy spoken replies to meeting chat. Both start off. Then choose Join call.
Skyflo opens the meeting in a Chromium browser on your Mac, in the background, without taking your focus. It asks to join under the name of the voice you chose, Marin by Skyflo by default, with its orb as its camera, and the host lets it in like any other guest. It introduces itself once, takes up the opening agenda if the brief has one, and posts a notice in the meeting chat saying what it is. Then it listens.
Partway through, someone asks, "Marin, what is still failing in checkout?" That sentence becomes a turn on the release mission, exactly as if you had typed it. The mission's agent runs the tests in its repositories and reads the failure, and Skyflo tells the room what it found when the answer is ready. Someone asks to see it. Skyflo shares the mission's browser into the call, and talks about the screen only once the call is showing it. Someone else says, "Fix the currency rounding and run the suite again." The mission starts on it while the discussion moves on. If the agent reaches a command that needs approval, the room can allow it once or reject it. Anything wider waits for you on your Mac.
At the end you say, "Marin, write up the release notes and open the pull request. I'll leave the call now." Skyflo confirms what it will do, thanks the room, says goodbye and leaves. The mission keeps working. Back in Skyflo, the call is in Meetings in the sidebar, and the work it started is in the mission.
Why Not a Note-Taker
Two kinds of product already sit in calls, and Skyflo is neither.
A meeting note-taker joins, listens and writes a summary. That is useful, and it is also a document about work. Somebody still has to read it, decide what it means and turn it into tasks, usually the next morning.
A separate voice bot can answer questions in the moment. But it arrives with nothing behind it: no repositories, no agents, no approvals, no history of what was tried. It can talk about the work. It cannot do it.
Skyflo in a call is the voice of a mission. The call is attached to one mission that already has a workspace, an agent (ChatGPT, Claude or Skyflo's own), the tools that agent uses, an access mode, memory for its repositories and a place to run, on your Mac or in Skyflo Cloud. A request made in the call is a turn on that mission: planned, approved where its access mode says so, and recorded like any other. When the mission orchestrates, the request can send out specialists, and their results come back to the same conversation. The meeting becomes an input to the work rather than a record of it.
That is also why the transcript is optional. A note-taker's product is the transcript. Skyflo's product is the work, so keeping the text of a conversation is a choice the host makes for each call, not the default.
In A Voice Is a Control Surface we argued that voice in Skyflo is a second way into the same product, under the same authority, producing the same record. Meetings takes that idea into a room with several people in it. Most of the work was deciding what that room may do.
The Room Directs One Mission, Under Its Rules
Everyone admitted to the call can direct the mission the call is attached to. They can give it work, steer a turn, ask where things stand, stop it, drop a waiting message or send it now, and ask Skyflo to speak in a different voice. That is the whole grant, and it is enforced in one place, between the meeting and the mission.
Everything else is refused out loud, with a sentence the room hears:
- Other missions. A call is connected to one mission. A request to start a new mission becomes work on this one, and nothing in the call can open, list or follow another.
- The mission's rules. Its access mode, agent, model and strategy stay as you set them. Changing them is not directing the work. It is changing the rules the work runs under, and that happens in Skyflo on your Mac.
- Wider permission. When the mission is waiting on an approval, the room can allow that one request once or reject it. A choice that reaches further, such as allowing a command for the rest of the session, waits for you in Skyflo.
- Your Mac. The Skyflo window, its settings and its panes belong to the host, not to the meeting.
Leaving the call ends the connection. From that moment, nothing still in flight from the meeting reaches the mission.
Two more boundaries come with the agents and the app. A mission on ChatGPT or Claude shares, presents and demos only with Full access. And in every access mode, the controls that approve, allow, sign in, accept terms or pay are left for a person, in a demo as anywhere else.
Showing, Not Describing
The hard part of putting Skyflo in a call was not making it speak. It was making sure it says only what is true about a screen the room is looking at.
A share is one of two sources and nothing else: the mission's own browser, or the single window of another app that you allowed the mission in Settings › Computer use, which is also new in 1.7. Never the whole screen, never another window, never another mission's browser. When the room has just asked to see something, Skyflo starts the share. Otherwise it asks first and shares only on a yes. The host can take it down at any time with Stop sharing, and anyone in the room can ask it to stop.
A share counts as on screen only when the meeting page itself shows Skyflo presenting and its pictures are reaching the call. Until then the share is starting, and nothing Skyflo says may claim otherwise. If the window it shows is minimized or moved to another Space, the room keeps the last picture, and Skyflo treats the share as paused rather than live until the window is back.
On top of a share, a mission can do two things.
It can present: hand the call a walkthrough in sections, each with what to say and, when it helps, a page to show in the mission's browser while that section is narrated. Skyflo starts a section only after the previous one has finished playing, pauses the moment someone speaks, answers, and picks up where it left off. A walkthrough nobody asked for waits for the room to agree.
It can demo: show the room an app and drive it while it talks. Each step runs in a fixed order. If anyone has spoken since the mission last looked, nothing happens and the mission hears what they said first. Skyflo says one or two sentences about what the room is looking at and waits until they have played. Only then do the actions run, in the background, and the window is read again before the next step. The room never hears about one screen while looking at the next. When something slow is running, Skyflo keeps the room informed with short progress lines instead of silence.
The rule underneath all of it: a claim about the screen waits for the call to confirm it.
Leaving Well
A participant that stays too long, or leaves badly, is worse than one that never came. So leaving is designed as carefully as joining.
- Hand off and go. Give Skyflo the next piece of work as you leave, and it says what it will do, says goodbye and leaves with you. The mission keeps running after the call.
- The room wraps up. When the call is ending, Skyflo answers with a short thank-you and goodbye, not a status update nobody asked for.
- Everyone else has left. A few seconds after the last person goes, Skyflo leaves too, with the platform's own Leave. It never ends the call for anyone. On Zoom, if the departing host hands Skyflo the host role, it still only leaves.
- Stop listening. Anyone can say "Marin, stop listening". Skyflo stays in the call without hearing it, says so in one sentence, and the host can turn it back on from Skyflo. "Marin, leave" works the same way.
- The voice drops. If Skyflo's voice cannot continue, it posts in the meeting chat that it is leaving and whether the host can bring it back, then leaves, and Skyflo on your Mac says why.
A long call does not run out of voice. Before a voice session reaches its limit, Skyflo waits for a pause and renews it, carrying the conversation over without introducing itself again.
What Skyflo Says, and What It Keeps
When Skyflo joins, and again for anyone who arrives later, it posts a notice in the meeting chat. The notice says that it is an AI assistant connected to the mission, that anyone in the call can ask it to work on that mission, that what is said is sent from the host's Mac to OpenAI while it listens so it can answer, whether a transcript is being kept, and how to make it stop listening or leave. Everyone in the call reads the same thing, guests included.
Skyflo records no audio or video. For every call, Meetings in the sidebar keeps when Skyflo asked to join, when it was admitted and when it left, the participants the meeting page showed and what Skyflo shared. When the host chose Save a transcript on this Mac, the meeting also keeps the text of the conversation, on this Mac, with what was heard and what Skyflo said kept apart, and with gaps and unknown speakers marked as such rather than guessed. Copies of spoken replies posted to the meeting chat follow that platform's chat retention.
You can search your meetings, read one back, export it as text or JSON, or delete it. Saved meetings belong to the account that kept them, and they stay reviewable, exportable and deletable after the add-on ends. When a transcript was saved, the mission can read it, so the work after a call starts from what was actually said.
Who It Is For
The reasons change with the size of the company.
Startups. The founder and the first engineers are in calls all day, and every call creates work. With Skyflo in the call, a customer call can end with the fix already underway, and a release review can end with the release notes already being written. Nobody has to remember to start it afterwards.
Growing tech companies. Standups, release reviews and incident calls are where the questions come up: what is failing, what changed, what is left. A participant attached to the mission that knows the repositories answers from the work itself, and "can someone look into that" becomes a turn with a record instead of an action item.
Mid-market companies. Calls cross teams. Product, engineering and operations meet to review a change, and someone always asks to see it. Skyflo can walk the room through it or demo the app live, with the room's agreement before anything goes on screen, and the host keeps a record of what Skyflo did and shared.
Enterprises. The first questions are about control: what can the room do, what is captured and where does it go. The answers are in the product. One mission per call. The mission's approvals and access are unchanged by the meeting, and the room can allow one waiting request once, never more. Skyflo records no audio or video, keeps a transcript only when the host chooses and only on the host's Mac, and says so to every participant in the meeting chat. Controls that approve, sign in, agree or pay are left for a person. A larger rollout starts with a scoped pilot.
How to Get It
Meetings is a $35 a month add-on for a monthly Pro or Max plan. It brings Skyflo into one call at a time, and it is not part of Team plans. On Free or Core, the call button in a mission shows what unlocks it and opens the offer. The pricing page has the plans.
Skyflo joins from a Chromium browser already on your Mac: Google Chrome, Brave, Microsoft Edge or Chromium, using a profile of its own. For Google Meet, sign that profile in once to the Google account Skyflo should join as. Zoom and Microsoft Teams admit Skyflo as a named guest, and a meeting that admits only signed-in accounts opens the same window for you to sign in once. If a platform asks for a passcode, a sign-in or a check meant for a person, Skyflo says so and you take that step.
Download Skyflo for Mac. The release notes cover the rest of 1.7: computer use in the background, Orchestrate in Skyflo Cloud, approvals for merges, tags and releases from Skyflo Cloud, Send Feedback and the new Help menu.
What This Is Part Of
Each release has let Skyflo carry more of the work. 1.1 made Skyflo a HyperAgent that learns from the missions it completes. 1.2 gave it a voice that operates the product. 1.4 let you and an agent share one browser and one terminal. 1.5 let a mission outlive the laptop in Skyflo Cloud. 1.6 brought a team onto one subscription.
1.7 brings that voice into the room, under the same authority and with the same record. The meeting is still where the work gets decided. Now it is also where the work starts.