VS Code / Cursor sidebar chat that drives Meta’s Muse Code CLI (muse exec --json). The agent harness stays Muse; this extension is only the IDE UI.
Not affiliated with Meta. Muse Code, Muse Spark, and related marks belong to Meta. Install and authenticate Muse separately: Muse Code docs.
Requirements
- macOS or Linux (Muse Code CLI does not support Windows yet)
- Muse Code installed and signed in (or
META_API_KEYset) - VS Code or Cursor
- An open workspace folder that is not a symlink root (Muse rejects reparse points)
curl -fsSL https://dev.meta.ai/install.sh | sh
Install (published)
After this extension is on a marketplace:
- VS Code Marketplace: search “Muse CLI Chat” (publisher
codemarc) - Open VSX / Cursor: same extension id
codemarc.muse-cli-chat
Or install a local .vsix:
cd tools/extensions/muse-code
bun install
bun run package
code --install-extension muse-cli-chat-0.1.0.vsix
# Cursor: cursor --install-extension muse-cli-chat-0.1.0.vsix
Develop
cd tools/extensions/muse-code
bun install
bun run compile
Open this folder in VS Code/Cursor and press F5 (Run Muse Code Extension). In the Extension Development Host:
- Open a real directory (not a symlink)
- Command Palette → Muse CLI Chat: Open Chat (or click the Muse activity icon)
- Optional: set
muse.useEchoProvidertotruefor offline JSONL UI testing - Send a prompt
Commands
| Command | Action |
|---|---|
| Muse CLI Chat: Open Chat | Focus the sidebar |
| Muse CLI Chat: Send Selection | Send the editor selection as context |
| Muse CLI Chat: New Session | New --session-id |
| Muse CLI Chat: Stop | SIGINT the running muse exec |
| Muse CLI Chat: Open Interactive Terminal | Full Muse TUI (approvals, slash commands) |
| Muse CLI Chat: Check Installation | muse --version |
Settings (muse.*)
| Setting | Default | Notes |
|---|---|---|
executablePath |
muse |
Also tries ~/.local/bin/muse |
model |
empty | Optional --model |
reasoningEffort |
empty | Optional --reasoning-effort |
trustWorkspace |
true |
Loads project skills/rules |
disableApproval |
true |
Needed for headless; sandbox stays on |
yolo |
false |
Disables approval and sandbox (dangerous) |
useEchoProvider |
false |
Offline UI smoke tests |
extraArgs |
[] |
Extra argv |
Safety
Headless muse exec cannot answer interactive approval prompts. The extension defaults to --disable-approval with the OS sandbox still on (Meta’s recommended CI posture). For staged shell approvals, use Muse CLI Chat: Open Interactive Terminal.
Never enable muse.yolo on a machine with real credentials unless you fully trust the workspace. Enabling it shows a one-time warning.
Tests
bun test
bun run check
Publish
- Create publisher
codemarcon VS Code Marketplace and/or Open VSX (changepublisherinpackage.jsonif you use another id). bun installthenbun run package(producesmuse-cli-chat-0.1.0.vsix).- Open VSX (good for Cursor):
npx ovsx publish muse-cli-chat-0.1.0.vsix -p <token> - VS Code Marketplace:
bunx vsce publish --no-dependencies(aftervsce login)
Production compile minify: NODE_ENV=production bun run compile.