Desktop runtime

Your worker. Your machine.

Run portable workers against your files and shell. Your keys stay local, and new shell commands ask first.

Windows
Windows 10 or newer
macOS
Choose the chip in your Mac

v0.5.0 installers are public and checksum-published, but unsigned. Windows and macOS will show a publisher warning — on Windows choose More info → Run anyway, on macOS right-click → Open. Updates are cryptographically signed either way.

SHA-256 checksumsRelease notesPublic core publishing
AgentMug Desktop: Local Doer
› Why is the build slow?
Let me see what's in the repo and what the build script looks like.
Shell approval
Reason: list the files in the project root.
ls -la
Always allow this exact command (skip next time)
DenyAllow
package.json / src / dist / node_modules / ...
Found it. The build re-runs the type-checker on every file change because noEmit is not set in dev. Want me to patch tsconfig.json?
Why local

A runtime that lives on your disk

Runs on your machine
Agents can use shell.execute, inspect files, and reach local development tools that browser-bound assistants cannot. The work happens where your code already lives.
Native approval gate
Every command is checked against your approval rules. New commands show the agent's reason before they run, while safe exact patterns can be pre-approved.
Your keys never leave
Anthropic and Gemini API keys stay in local app storage on your device. Calls go directly from the app to the provider. AgentMug's servers are never in the loop.
Audit log on disk
Every approved command is appended to a local JSONL file. Open it, read it, prune it. Trust requires receipts.
Setup

Four steps to your first run

1
Install the app for your OS
2
Paste your Anthropic key in Settings once
3
Open a .agent file (start with Local Doer)
4
Ask in plain English, then approve commands per call
Get started

Install AgentMug Desktop

Choose your installer above. Your keys stay on your machine and new shell commands remain behind visible approval controls.