A Windows, macOS, and Linux desktop client for Muse, Meta's Muse agent. It uses Electron's Chromium webview so Muse receives the browser platform it expects, while keeping the main experience in a focused window.
The app keeps a dedicated browser profile, opens the system file picker for uploads, saves downloads to the user's Downloads directory without overwriting existing names, and grants Muse's web notifications through the native desktop notification system.
Download an installer from the latest GitHub release. Choose the file matching your operating system and CPU:
- Windows (x64): download the
.exeand run the installer. - macOS: choose
arm64for Apple Silicon orx64for Intel. Open the.dmgand drag Muse into Applications, or extract the.zipand move Muse into Applications. - Linux (x64): install the
.debon Debian/Ubuntu (sudo apt install ./Muse-*.deb) or the.rpmon Fedora (sudo dnf install ./Muse-*.rpm). Alternatively, download the AppImage, make it executable withchmod +x Muse-*.AppImage, and run it with./Muse-*.AppImage. AppImages may require your distribution's FUSE compatibility package. On NixOS, use the Nix package below instead.
These builds are not developer-signed or notarized. Windows SmartScreen and macOS Gatekeeper may show warnings or block launch. Only approve a downloaded app if you trust its source; on macOS, System Settings → Privacy & Security → Open Anyway may be available after attempting to open it. Managed devices may prohibit unsigned applications.
The flake supports x86_64-linux, aarch64-linux, x86_64-darwin, and aarch64-darwin. It uses Nixpkgs' Electron runtime, so no npm install is needed. Enable Nix's nix-command and flakes experimental features first (for example, set experimental-features = nix-command flakes in ~/.config/nix/nix.conf).
Run without installing:
nix run github:benjaminkitt/muse-desktopOr install into your user profile:
nix profile add github:benjaminkitt/muse-desktop
muse-desktopFrom a local checkout, use nix run . or nix build .. The package is exported as both packages.<system>.default and packages.<system>.muse-desktop; the app is exported as both apps.<system>.default and apps.<system>.muse-desktop. Linux includes a desktop entry and icon, and macOS includes an Applications/Muse.app launcher. A graphical desktop session is required. Nix on non-NixOS Linux may need host graphics integration such as nixGL.
Add the input to your configuration's flake.nix:
inputs.muse-desktop.url = "github:benjaminkitt/muse-desktop";Pass your flake inputs to modules with specialArgs = { inherit inputs; }; in nixosSystem or darwinSystem. Then add this to a NixOS or nix-darwin module:
{ inputs, pkgs, ... }: {
environment.systemPackages = [
inputs.muse-desktop.packages.${pkgs.stdenv.hostPlatform.system}.default
];
}For Home Manager, pass extraSpecialArgs = { inherit inputs; }; to homeManagerConfiguration (or set home-manager.extraSpecialArgs when used as a NixOS/nix-darwin module), and use:
{ inputs, pkgs, ... }: {
home.packages = [
inputs.muse-desktop.packages.${pkgs.stdenv.hostPlatform.system}.default
];
}Here inputs is the input set from your flake's outputs = inputs@{ ... }: ... function. Rebuild or switch your configuration normally. Keep this input's own Nixpkgs pins unless you deliberately want to change its Electron/platform support. Your flake.lock pins the app revision; update the muse-desktop input to receive newer versions.
On Linux/NixOS:
nix develop
npm install
npm run devThe Nix shell supports both Intel and Apple Silicon macOS, as well as x86_64 and ARM Linux, and supplies Electron 43. On macOS, enter nix develop, run npm install, then use the same commands.
Create installers with:
nix develop --command npm run buildOn Linux this creates AppImage, .deb, and .rpm packages. On macOS it creates .dmg and .zip artifacts. On Windows, use Node.js 22 and npm ci, then npm run build to create an NSIS .exe installer. Packages are written to dist/ with platform and architecture in their filenames.
Desktop shells (GNOME, KDE) show the app icon by matching the running window to an installed muse-desktop.desktop entry, which points at muse-desktop icons in the freedesktop hicolor theme. The identity basename muse-desktop is set in four places that must stay in sync: desktopName and build.linux in package.json, the app.setDesktopName call in electron/main.cjs, and the desktop entry in flake.nix. test/packaging.test.cjs fails if they drift apart.
Linux packages install one PNG per size from build/icons/ (16–1024px), and the Nix package also installs build/icon.svg as a scalable icon. Regenerate the sized set after changing the icon source:
for size in 16 24 32 48 64 96 128 256 512 1024; do
magick build/icon.png -resize ${size}x${size} build/icons/${size}x${size}.png
doneAlready-installed packages keep their old icon until rebuilt and reinstalled; desktop shells may also cache icons until relogin. The release workflow verifies that Linux artifacts contain the icon set and a matching desktop entry.
Run the Release workflow on the default branch with a patch, minor, or major bump. It pushes the version commit and tag, then builds all platforms and publishes their assets.
If a build or publication fails after the tag was pushed, start a fresh Release run with resume_tag set to that exact tag (for example v0.2.1). The bump choice is ignored: the workflow rebuilds the tagged commit and creates or resumes its draft release without changing the version, branch, or tag. Do not leave resume_tag blank when retrying a stranded release, as that allocates a new version. Only existing version-matching tags on the default branch's history that have not already been published are accepted. This also works after the original run's artifacts expire.
Quit Muse, then remove its profile and cache:
rm -rf "${XDG_CONFIG_HOME:-$HOME/.config}/Muse" \
"${XDG_CACHE_HOME:-$HOME/.cache}/Muse"On macOS:
rm -rf "$HOME/Library/Application Support/Muse" \
"$HOME/Library/Caches/Muse"This signs out of Muse and clears its cookies, local storage, downloads history, and cached content.
The embedded window has Node integration disabled and uses a sandboxed, isolated renderer. The main window permits in-app navigation only to Muse and the small set of Meta-hosted sign-in redirect pages required by Muse. Other same-window links open in the system browser.
Links requesting a new window and OAuth popups open in managed, sandboxed child windows sharing the Muse profile. These preserve window.opener, callback messaging, and blank-window-then-redirect flows without navigating away from the main Muse page. Child windows allow HTTP(S) navigation for identity providers and callbacks, block unsafe URL schemes, and close when their opener closes. They receive no Node or shell access; notification permissions remain restricted to the exact Muse origin.
Copy buttons using the browser Clipboard API can write to the clipboard only from the exact https://muse.ai origin. Programmatic clipboard reads and clipboard permissions for other origins remain denied. Restart the development app or rebuild/reinstall the packaged app to apply permission changes.
Some identity providers may prohibit authentication in embedded browsers. The popup regression tests verify desktop handler behavior, not successful authorization with every provider; authenticated connection flows still require manual testing.
Muse Desktop's source code is available under the MIT License. Muse itself and third-party dependencies remain subject to their respective terms and licenses.