v0.5.0

Released 25 July 2026. This release adds the Fosnie desktop application for Windows and macOS: paired to your own instance, able to work in folders on your own computer with your approval on every change, run scheduled automations there, and show you clearly what an agent is doing.

Fosnie for desktop

The desktop application is the same Fosnie you use in a browser, connected to your own instance: the chats, projects and libraries are the ones already there. It holds its connection outside the window, so a long answer survives a minimised window, a closed lid or a change of network instead of stopping mid-sentence, and it tells you when an answer is ready or an agent needs approval. Pairing uses a short code from your profile, so the app never asks for your password: its credential belongs to that one computer, lives in the operating system's credential store, and can be withdrawn from the web at any time.

Connected folders

Connect a folder to the desktop app and a chat can work in it: the agent lists what is there, reads files, and, where you allow it, writes them, deletes them, and runs commands. You choose the folder through your system's picker and set how much an agent may do: read only, read and write, or read and write without deleting. Reading runs freely; every write, command and deletion is shown to you first and copied aside so a single file or a whole turn can be undone. A path that would leave the folder once links are followed is refused, and a command inherits none of the app's credentials.

Scheduled tasks that run on your machine

A scheduled automation can now be pointed at a connected folder on one of your machines: the schedule stays on the server, but the folder work is carried out by the machine itself. If the machine is offline when a run is due, the run is recorded as missed rather than skipped, and can be made up once it reconnects. A step that changes a file waits for your approval, answerable from any device you are signed in to.

Seeing what the agent is doing

An agent's plan for a multi-step turn now stays pinned above the conversation, collapsed to a single line you can open into the full checklist, ticking through one step at a time. When the turn finishes, a summary takes its place: the files it changed and the commands it ran, each with how it exited and the tail of its output. A request for approval is harder to miss: decide it on one device and it settles everywhere you are signed in, the desktop app carries a count of those waiting on its taskbar, and a task that fails in the background raises a notification. An actions-only toggle hides the prose so you can review a long turn by what it did rather than what it said.

Getting the desktop application

The desktop application now arrives three ways: a signed download from us, an installer your own instance serves to its users, and a documented build from source. An installation that hosts its own copy never reaches us at all, because paired apps ask it for updates first, so a closed network stays current from inside itself and an administrator decides when the version moves. Every installer is published with its SHA-256 so a vetting pipeline can confirm the file it received is the file that was published.

Fewer interruptions for commands the agent runs on your computer

The desktop agent used to ask you to confirm every command. On a computer where its commands run inside an enforced boundary, that boundary already guarantees a command can only touch the connected folder and, unless it asks otherwise, cannot reach the network, so such commands now run without interrupting you. You are still asked about a command that needs the internet, anything that would change files outside the folder, and every deletion. Where the boundary is not enforced the agent asks exactly as before, and an administrator can switch confirmation for every command back on for the whole deployment.

Fixed

• Fixed the sidebar being squeezed into a stub column with its labels cut off when the window is narrow, such as a desktop window snapped to half a screen: it now steps aside and opens over the page on request, as it already did on a phone.

Upgrade

No action is required. The desktop application is optional and paired from your profile; existing browser use is unchanged.