The desktop app for Mac and Windows.

The desktop app shows the same surfaces as the web app. It adds a long-lived session, files and a terminal, and it bundles the platform's local server at the app's version.

The desktop app shows the web app’s surfaces in a native window. It adds what a browser lacks: a session that lasts across restarts, a workspace of files, a terminal, and the local server beside the app.

Installers#

The team releases the app with the platform, under one version and one receipt. The changelog lists each release. An update changes the local server’s version only together with the app’s version.

Local processes#

The local server starts with the app. It runs these parts:

• the MCP server, on the local socket, and on the TCP and WebSocket listeners when you turn them on
• the query client over the lakehouse
• the file manager, limited to the workspace
• the response cache

The acquisition system runs beside the local server as a second process. Pages that you read and files that you drop therefore enter the record from your machine. The page on the local server describes each part.

Files and the terminal#

The files in the workspace belong to the app. The app reads and writes them through the files routes, and the platform does not reach them on its own. The terminal runs the named procedures that the app knows. Each procedure runs as a task, and the app’s journal records its steps.