Meta ships Muse Code terminal-first. There is no Muse Code extension for VS Code from Meta, no desktop app, and no GUI of its own; Meta's own page calls it multi-agent coding in your terminal. The free AFK Pilot extension (previously Grok Build for VS Code) runs the real Muse Code CLI in a VS Code or Cursor sidebar, and the same interface runs it in a standalone desktop app for Windows, macOS and Linux and in any browser, including your phone. You get permission cards, diffs, resumable history, and Muse's own approval modes.
I build the extension, the desktop app, and the afkpilot.com phone client. None of them is affiliated with or endorsed by Meta. Muse Code and Muse Wonder are Meta's.
Last updated: November 5, 2026 (extension v4.15.8).
At a Glance
What it is. A graphical interface for Meta's Muse Code CLI, not a re-implementation of it. Muse speaks Meta's own protocol rather than the Agent Client Protocol the other agents use, so the extension ships a small adapter between the two.
Where it runs. VS Code 1.106+ and Cursor 3.x as an extension; Grok Build Desktop (Community) as a standalone app on Windows, macOS and Linux; any browser through AFK Pilot.
Sign-in. Muse's own login, on the machine that runs it. The app shows Meta's link and a short code, and your usage counts against your own Meta account.
Approval modes. Muse's own, under Muse's names: Allow all, Prompt unmatched, and, at the desk on macOS and Linux, On request.
Other agents. Grok Build (the default), DeepSeek, OpenAI Codex, Claude Code and Google's Antigravity run in the same window; DeepSeek and Antigravity on your own computer only, once you turn them on in Settings → Advanced (they're off by default). Each conversation keeps the agent it started with.
Price. The extension and the desktop app are free. The phone client has a free tier; Remote Max is $5 a month.
Not yet for Muse. Steering a running turn, compaction, deleting history, and the connectors the app manages for Grok Build, Codex and Claude Code.
Why Muse Code Needs a GUI
Muse Code is built for long, multi-agent runs. In a terminal that is a scrolling log and a permission prompt you have to be sitting in front of. In a GUI it is a conversation you can leave and come back to, from the desk or from your phone.
What the interface adds, concretely:
Permission cards and diffs. In Prompt unmatched, every command Muse wants to run shows up with the exact command line, and a file edit shows as a diff before it lands.
A workflow card. Muse delegates through workflows, and the chat shows each one as a single card: the steps as rings on a track, the agents grouped under each step with their status and tokens, and what the run returned, with a copy button.
History you can resume. Conversations reopen with their tool calls and command output. Muse keeps its own history, and this app does not delete it.
A model and effort picker. The models Muse offers your account (as of October 2026, Muse Wonder, and Muse Wonder Full on the Muse Code plans that include it), with contributor models marked by Meta's data-use notice, and the reasoning-effort strip.
Usage. The usage popover shows Muse's current window and its weekly window once Muse reports them, usually after your first reply.
Your phone. The same session in a browser, which matters for an agent built for long runs.
Set It Up
Install a host. In VS Code, Cursor or another VS Code-based editor, open Extensions (Ctrl/Cmd+Shift+X), search “AFK Pilot” or the ID
grok-vscode-phuryn, and install, or use the direct links for the VS Code Marketplace and Open VSX. No editor? Download Grok Build Desktop (Community) from afkpilot.com/desktop.Install Muse Code if you do not have it. When the CLI is missing, the Muse panel shows Meta's install command and an Install Muse Code button, which runs Meta's official installer in a visible terminal after you confirm. Then click Re-check.
Connect. Settings → Providers → Connect Muse Code. If Muse is already signed in on this machine, the app uses that sign-in. If not, Muse starts its own login and the app shows Meta's link and short code; the link opens when you click it.
Pick Muse and start. Choose a Muse model in the picker and send your first message. From then on the conversation stays with Muse.
Or install the CLI yourself with Meta's installer:
# Windows (PowerShell)
irm https://dev.meta.ai/install.ps1 | iex
# macOS and Linux
curl -fsSL https://dev.meta.ai/install.sh | bashOn Windows that puts muse.cmd under AppData\Local\Programs\muse in your user folder and adds it to your user PATH; on macOS and Linux it lands in ~/.local/bin/muse. Meta's own page: dev.meta.ai.
Muse Code on Windows
Muse Code runs natively on Windows. Early write-ups said it needed WSL; Meta now ships a PowerShell installer, and both the extension and the desktop app run Muse on Windows without WSL. One difference: on Windows, Muse's shell sandbox does not work in the server mode the app runs Muse in, so every approval mode runs without it there, On request is not offered, and the sandbox settings are hidden. Workspace trust stays yours to set.
Muse's Own Approval Modes
A Muse conversation offers Muse's modes, under Muse's names, instead of the ones the other agents use:
Allow all. Muse's full access, the same as
muse --yolo. No prompts, the shell sandbox off, the workspace trusted. A new install starts Muse here.Prompt unmatched. Muse asks about anything no rule matches. The one I would start with on a real repository.
On request. Tools run in Muse's sandbox, and it asks only when a tool requests permission. At the desk, on macOS and Linux only: Windows and Cloud machines run Muse without its sandbox, so they do not offer it.
A fourth mode, Deny unmatched, is still hidden here. In it, every turn used to stay open for about a minute, a Muse bug reported as muse-code-sdk issue 63; Meta says Muse Code 1.4.2 fixes it. Conversations saved in it open in Prompt unmatched.
Approval changes apply from the next action. The sandbox settings work differently: Settings → Providers → Muse Code has Shell sandbox, Sandbox network, and Trust workspaces for new conversations, and they take effect when a conversation reopens or a new one starts. On Windows the two sandbox settings are hidden and Trust workspaces stays. A trusted workspace also runs the repository's hooks, so trust only projects you would run yourself.
Muse Code From Your Phone
Link the machine once with AFK Pilot and the same Muse conversation opens in any browser. From the phone you can send work, approve permission cards, follow a workflow card, switch Muse's approval mode, and connect Muse in the first place: the computer runs Muse's login and the phone shows Meta's link and code. Two things stay at the desk: installing Muse, which has to run on that machine, and Muse's sandbox and workspace-trust settings.
No computer to leave on? AFK Pilot Cloud machines come with Muse Code preinstalled next to Grok Build, Codex and Claude Code. The machine is already an isolated virtual machine, so Muse runs there without its own shell sandbox, its approval rules still apply, and On request is not offered. Setup, privacy and pricing, for all four agents: Grok Remote Control.
What It Does Not Do Yet
No steering mid-turn. Muse does not take a correction while it works, so a message you send queues and runs next. Grok Build and Codex do take one.
No Plan mode. This app cannot make Muse hold its edits until you approve a plan, so it does not pretend to.
No compaction or history deletion from here. Muse keeps its own history.
No app-managed connectors. The connectors you add under Settings → Connectors go to Grok Build, Codex and Claude Code, not to Muse.
FAQ
Is there an official Muse Code GUI or VS Code extension?
No. As of October 2026 Meta ships Muse Code as a terminal agent, installed with a one-line script, plus an SDK for developers. There is no Meta extension for VS Code or Cursor and no Meta desktop app. This one is a community project.
Is it free?
The extension and the desktop app are free and open source (FSL-1.1-MIT; each release becomes MIT after two years). Muse Code itself runs on your own Meta account and plan.
Can I use Muse Code without the terminal?
Yes. Grok Build Desktop (Community) offers to install Muse with Meta's installer, after you confirm, and connects it from Settings. You never type a command.
Does Muse Code work in Cursor?
Yes. The extension runs in Cursor 3.x and VS Code 1.106+, and Muse connects the same way in both. Google's Antigravity editor is on an older VS Code base, so it keeps an extension version from before Muse support.
Does Muse Code work on Windows?
Yes, natively. Meta's PowerShell installer puts it on your PATH, and the extension and the desktop app run it without WSL.
Can I run Muse Code and Claude Code side by side?
Yes. Grok Build, Muse Code, Codex and Claude Code can all be connected at once, and on your own computer so can DeepSeek and Google's Antigravity, once you turn them on in Settings → Advanced (they're off by default). Models from every connected agent share one picker, and each conversation keeps the agent it started with, which makes it easy to put the same task to two agents. To keep Claude Code running on a server around the clock instead, see Claude Code on a VPS.
Can I control Muse Code from my phone?
Yes, through AFK Pilot. Link the machine once, open afkpilot.com on the phone, and the same Muse conversation is there, approvals and workflow cards included. Or skip your own machine and use a Cloud machine, where Muse is preinstalled.
Which is better, Muse Code or Claude Code?
It depends on the task. In this app the practical difference is what each one supports: Claude Code has Plan mode, compaction and the connectors the app manages; Muse Code has none of those yet, and neither takes a correction mid-turn. Connect both and put the same task to each: each conversation keeps its agent, so the results sit side by side.
Is this the same app as the Grok Build GUI?
Yes, one app. It is built for Grok Build, which stays the default, and the extension's listing names Muse Code next, because those are the two agents with no graphical interface of their own. The Grok side: Does Grok Build have a GUI?
I build these in the open and write up what building them teaches me about product work. That is the newsletter: not the tool tour, but what changes for PMs and builders once agents do the building.
AFK Pilot and Grok Build Desktop (Community) are unofficial community projects by Pawel Huryn, not affiliated with or endorsed by SpaceXAI (formerly xAI), Meta, DeepSeek, OpenAI, Anthropic or Google. Muse Code, Muse Wonder and Muse Spark are trademarks of Meta; Grok and Grok Build of xAI; DeepSeek of DeepSeek; Codex of OpenAI; Claude and Claude Code of Anthropic; Antigravity of Google.