Muse CLI Chat (unofficial)VS Code / Cursor sidebar chat that drives Meta’s Muse Code CLI ( Not affiliated with Meta. Muse Code, Muse Spark, and related marks belong to Meta. Install and authenticate Muse separately: Muse Code docs. Requirements
Install (published)After this extension is on a marketplace:
Or install a local
Develop
Open this folder in VS Code/Cursor and press F5 (Run Muse Code Extension). In the Extension Development Host:
Commands
Settings (
|
| 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.