Desktop app

For a developer's own computer this is the shortest way to run a worker: download the installer, start the app, connect it. Nothing else has to be installed; the app brings its own Node.js. For servers and machines without a desktop, use the installers.

Download

The links always point at the newest release. The dashboard offers the same downloads in the Install the worker card on Workers, Getting started and the pairing page, next to your server's address to paste into the app. A fork sets UPDATE_CHECK_REPO on the server to link its own releases.

What the app does

• The window shows the same local UI as the browser does, with a folder chooser next to path fields.
• Closing the window keeps the worker running. The tray icon shows its state and opens the window, the log and Quit. Quitting the app stops the worker.
• Start at login is in the tray menu and in Settings. The app then starts in the tray.
• The worker runs as you and uses the same data folder as a worker installed with the scripts, so the pairing, settings and credentials carry over in both directions.

Connect it as any other worker: see Pairing.

With a command-line worker on the same computer

The app and a command-line worker use the same data folder and port, so only one runs per user. If a worker installed from the command line already runs, the app says so and offers:

• Use the desktop app instead: removes that worker's autostart entry and stops it, and keeps its data;
• Keep it and open its UI.

Updates

• The worker inside the app updates as every worker does: see Worker updates.
• The app itself (window, tray, bundled Node.js) changes rarely. Check for updates… in the tray menu, or Updates → Check for app updates…, installs a newer one after asking. App updates are signed with the project's updater key and refused when the signature does not match.
• On Linux the .AppImage updates itself; a .deb is updated by installing the newer one.

Linux tray icon

The tray icon needs an AppIndicator host (on GNOME, the AppIndicator extension). Without one the app works, and the window is the only way to reach it.

Scripts and uninstalling

• Start the app again with --quit to stop the running app and its worker cleanly.
• Uninstalling keeps the worker's data (pairing, settings, credentials) and the app's own folder with the installed worker versions and the log. To leave nothing behind, delete them by hand: the worker data folder is the one agentctl doctor names, and the app's folder is io.agent-orchestration.worker in your local application data.