skyflo

Release notes7 releases

Release notes.

What changed in each Skyflo Desktop release, newest first. Notes are published with the release, so they never describe a build you cannot install.

Subscribe by RSS

1.0.8

Current release

Fixes an update that could leave Skyflo offline on every launch. Everything in 1.0.7 is 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 left a background helper from the older installation running, and the new version could not replace it, so Skyflo started with no local runtime and reported that it was offline. It now retires that helper and starts normally.
Download Skyflo for Mac

1.0.7

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.

Updating is the focus of this release: real download progress, a recovery screen that offers a way forward, and a compatibility floor that stops a build shipping if it cannot open missions a newer version created.

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.
  • A release can no longer ship a version that refuses to open missions a newer version of Skyflo created. Builds that would do this are rejected before they are published.
  • 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.5

Orchestration reliability. The lead you choose is the lead that runs, a route that fails says what happened, and sign-in recovers from a device key this Mac cannot use.

Improvements

  • Orchestration lead choices show the runtime version Skyflo detected for each harness.
  • Specialist lanes find the Python and CLI versions your Mac actually selects, including a sandboxed interpreter and the version your nvm default points at.
  • 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.
  • A route that fails reports what happened, scoped to that route rather than to the whole mission, and settles once its last worker finishes.
  • 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.
  • A read-only specialist lane keeps its own disposable home directory, so it starts instead of being denied.
How orchestration selects a lead

1.0.3

Mission completion notifications stay quiet while you are looking at the mission.

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.2

Model requirements now follow whichever runtime will actually do the work.

Fixes

  • A mission that runs on an external harness, or on an automatically selected orchestration lead, no longer asks for Skyflo model access it will not use. The harness still refuses on its own terms when it is not ready.

1.0.1

The first public 1.0 release. Skyflo Desktop runs missions on your own Mac, against your own repositories, with the model access you configure there.

New

  • Free accounts activate from inside the app. No credit card is required.
  • Apple silicon and Intel Macs running macOS 14 or later.
  • Missions use your repositories and the local or bring-your-own-key model access on your Mac.
Plans and what is available today

0.1.0

The first production build of Skyflo Desktop for macOS, signed, notarized, and Gatekeeper verified.

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.
Capability status

What gets a release note

What appears here
Every Skyflo Desktop release that reached people on the stable update channel, with what changed for the person using it. Purely internal work is left out when it changes nothing you can see: build tooling, release machinery, tests, and infrastructure.
When notes are published
With the release. An entry exists by the time a version is on the stable channel, so the notes and the build you can install never disagree.
What is not here
Builds nobody could install. A version that was tagged, drafted, or published and then held back before it reached the stable channel gets no entry. A release that did reach people and was later superseded keeps its entry, and says so.

Skyflo Desktop

Run the current release.

Every entry above describes a build you can install. Automatic updates keep an installed Skyflo on the current one.

Download for Mac

Free. macOS 14+. Apple silicon and Intel.