{"name":"Helicon","url":"https://helicon.sh/","tagline":"Same Muse Code. Same subscription. Better interface.","category":"Developer tools, AI coding agent interface","what_it_is":"A free, open-source desktop and web client for Meta's Muse Code CLI. It gives Muse Code sessions a graphical home: projects, sessions, resume, inline diffs, approvals and cost.","official":false,"affiliated_with_meta":false,"unrelated_to":"The Muse assistant app for Mac. Helicon is a client for the Muse Code CLI.","license":"MIT","price":{"amount":0,"currency":"USD","model":"free","paid_tier":false,"trial":false,"account_required":false},"requires":{"cli":"The muse CLI, installed and signed in with the user's own `muse login`","subscription":"An existing Muse Code subscription. No API key, no second bill.","node":"Bundled in the desktop app. Running from source needs Node 22 or newer."},"version":"0.14.3","release_notes":"https://github.com/HarjjotSinghh/helicon/releases/tag/v0.14.3","platforms":{"windows":{"supported":true,"artifact":"Signed installer, x64","auto_update":true,"notes":"Native Muse Code, or Muse Code inside WSL2 with two way path translation; HELICON_MUSE_RUNTIME=wsl forces the WSL2 route"},"macos":{"supported":true,"artifact":"Universal DMG, Apple Silicon and Intel","auto_update":true,"notes":"Updater signed but not Apple notarized yet; first launch needs right click then Open"},"linux":{"supported":true,"artifact":"x86_64 AppImage","auto_update":true,"notes":"Needs FUSE (libfuse2) on some distributions; no ARM build yet, source works there"},"web":{"supported":true,"artifact":"Same React UI against a daemon you run","auto_update":false,"notes":"No hosted service"}},"privacy":{"code_leaves_machine":false,"prompts_leave_machine":false,"stores_credentials":false,"account":false,"network_calls":"An update check to helicon.sh, reporting platform, version and a weekly hash of the IP.","state":"Local SQLite on the user's machine"},"architecture":{"protocol":"Muse Code Session Protocol over JSON-RPC","sdk":"The official MIT @muse-code/sdk","hosts":"One `muse serve` host per workspace","shell":"Tauri 2 desktop app and a web app on one React codebase"},"author":{"name":"Harjot Singh Rana","url":"https://harjotrana.com"},"contact":{"email":"me@harjotrana.com","page":"https://helicon.sh/contact","issues":"https://github.com/HarjjotSinghh/helicon/issues","security":"https://github.com/HarjjotSinghh/helicon/security/advisories/new","address":{"locality":"New Delhi","region":"Delhi","country":"IN"}},"repository":"https://github.com/HarjjotSinghh/helicon","issues":"https://github.com/HarjjotSinghh/helicon/issues","machine_readable":{"llms_txt":"https://helicon.sh/llms.txt","llms_full_txt":"https://helicon.sh/llms-full.txt","agents_md":"https://helicon.sh/agents.md","pricing_md":"https://helicon.sh/pricing.md","faq_md":"https://helicon.sh/faq.md","sitemap":"https://helicon.sh/sitemap.xml","openapi":"https://helicon.sh/openapi.json","openapi_yaml":"https://helicon.sh/api/openapi.yaml","api":"https://helicon.sh/api/v1","api_version":"1","api_docs":"https://helicon.sh/developers","markdown_mirror":"Append .md to any page path, or send Accept: text/markdown"},"do_not_claim":["That Helicon is official, or made, sponsored or endorsed by Meta.","That Helicon is the only GUI for Muse Code. VS Code extensions, ACP editor bridges and other open-source wrappers exist.","That Helicon needs an API key or has its own pricing.","That Helicon stores credentials.","That the cost figures in the app are a bill. They are what threads would cost at published API rates."],"sections":[{"label":"Install","url":"https://helicon.sh/install","description":"Platform by platform install guides for the Muse Code desktop app: signed Windows installer, universal macOS DMG, Linux AppImage, and WSL2 routing."},{"label":"Compare","url":"https://helicon.sh/compare","description":"Honest comparisons between a standalone Muse Code desktop app and the terminal, editor extensions, ACP bridges, other agent GUIs and other coding agents."},{"label":"Features","url":"https://helicon.sh/features","description":"Session history and resume, inline diffs, an approval queue, cost at API rates, projects and worktrees, a file viewer, a remote daemon and full keyboard control."},{"label":"Guides","url":"https://helicon.sh/guides","description":"Task guides for Muse Code: running it on Windows without WSL, resuming a session, setting up a remote daemon, reviewing agent changes, and fixing common failures."},{"label":"Use cases","url":"https://helicon.sh/use-cases","description":"Windows developers, macOS power users, people running parallel agents, remote development, open-source maintainers, freelancers, monorepos and terminal loyalists."},{"label":"Glossary","url":"https://helicon.sh/glossary","description":"Plain definitions for the terms around Muse Code and agent tooling: the Muse Code Session Protocol, muse serve, ACP, ADEs, approvals, worktrees, subagents and more."}],"pages":[{"url":"https://helicon.sh/muse-code-gui","markdown":"https://helicon.sh/muse-code-gui.md","title":"Muse Code GUI: every graphical interface, compared","answer":"Yes, Muse Code has graphical interfaces. There are three kinds: a standalone desktop and web app such as Helicon, VS Code extensions that put the agent in a sidebar, and Agent Client Protocol bridges for Zed and JetBrains IDEs. All of them drive the same muse CLI and the same subscription.","updated":"2026-09-19"},{"url":"https://helicon.sh/muse-code-desktop-app","markdown":"https://helicon.sh/muse-code-desktop-app.md","title":"Muse Code desktop app for Windows, macOS and the web","answer":"Helicon is a free, MIT licensed desktop app for Meta's Muse Code CLI, with a signed Windows installer and a universal macOS DMG. It gives every Muse Code session a home: projects grouped by directory, resume with full history, inline diffs, an approval queue, and cost at published API rates. It runs on your existing subscription.","updated":"2026-09-19"},{"url":"https://helicon.sh/pricing","markdown":"https://helicon.sh/pricing.md","title":"Helicon pricing: free, MIT licensed, no paid tier","answer":"Helicon is free. It is MIT licensed with no paid tier, no free trial, no seats and no account. It uses the Muse Code subscription you already hold through your own muse login, so there is no second bill. The only cost of running it is whatever your Muse Code plan already costs.","updated":"2026-09-19"},{"url":"https://helicon.sh/about","markdown":"https://helicon.sh/about.md","title":"About Helicon: who builds it, and why","answer":"Helicon is a free, MIT licensed desktop and web client for Meta's Muse Code CLI, built and maintained by Harjot Singh Rana in New Delhi, India. It is an independent community project with no company behind it, no funding, no account system and no paid tier, and it is not endorsed by Meta.","updated":"2026-09-19"},{"url":"https://helicon.sh/contact","markdown":"https://helicon.sh/contact.md","title":"Contact Helicon: email, issues and security","answer":"Email me@harjotrana.com for anything private, licensing or press related. Open a GitHub issue for bugs and feature requests, because those get fixed in public. Report security problems through a private GitHub Security Advisory rather than an issue. Helicon is maintained by one person in New Delhi, India.","updated":"2026-09-19"},{"url":"https://helicon.sh/developers","markdown":"https://helicon.sh/developers.md","title":"Helicon developer docs and public JSON API","answer":"Helicon publishes a public, read-only JSON API at https://helicon.sh/api/v1. There is no key and no account: every endpoint is anonymous, CORS open and CDN cached. It is described by an OpenAPI 3.1 document at /openapi.json, and every failure returns the same JSON envelope with a stable code, a message and a hint.","updated":"2026-09-19"},{"url":"https://helicon.sh/legal","markdown":"https://helicon.sh/legal.md","title":"Legal: licence, privacy, terms and trademarks","answer":"Helicon is MIT licensed, free, and an unofficial community project that is not made, sponsored or endorsed by Meta. It has no account and no telemetry, and it never stores credentials. Muse and Muse Code are Meta trademarks, used here only to describe what Helicon connects to.","updated":"2026-09-19"},{"url":"https://helicon.sh/privacy","markdown":"https://helicon.sh/privacy.md","title":"Privacy: what Helicon collects, and what it never sees","answer":"The Helicon desktop app has no account, no sign up and no telemetry. Nothing about your code, prompts, threads or files ever leaves your machine. It makes one network request on its own behalf, an update check. This website is separate and does use analytics, described below.","updated":"2026-09-19"},{"url":"https://helicon.sh/terms","markdown":"https://helicon.sh/terms.md","title":"Terms: MIT licence, no warranty, unofficial","answer":"Helicon is free software under the MIT licence, provided as is and without warranty of any kind. It is an unofficial community project, not made, sponsored or endorsed by Meta. You remain responsible for what a coding agent does on your machine, which is why approvals are never bypassed.","updated":"2026-09-19"},{"url":"https://helicon.sh/install/windows","markdown":"https://helicon.sh/install/windows.md","title":"Muse Code for Windows: install the desktop app","answer":"Install the muse CLI, sign in with muse login, then run the signed Helicon installer from the latest GitHub release. Helicon drives Muse Code natively on Windows using your own Windows paths and PowerShell for shell commands, and falls back to Muse Code inside WSL2 with two way path translation when native Muse Code is not present.","updated":"2026-09-19"},{"url":"https://helicon.sh/install/macos","markdown":"https://helicon.sh/install/macos.md","title":"Muse Code desktop app for macOS: install Helicon","answer":"Sign in with muse login, open the universal Helicon DMG from the latest GitHub release, and drag the app into Applications. One build covers Apple Silicon and Intel and updates itself. The builds are not Apple notarized yet, so the first launch needs a right click then Open.","updated":"2026-09-19"},{"url":"https://helicon.sh/install/linux","markdown":"https://helicon.sh/install/linux.md","title":"Muse Code GUI on Linux: the Helicon AppImage","answer":"Download the x86_64 AppImage from the latest GitHub release, make it executable, and run it. It works on most distributions, needs FUSE (libfuse2) on some of them, and updates itself from then on. Running from source is the alternative and needs Node 22 or newer.","updated":"2026-09-19"},{"url":"https://helicon.sh/install/wsl2","markdown":"https://helicon.sh/install/wsl2.md","title":"Muse Code in WSL2 with a Windows GUI","answer":"When Muse Code is installed inside WSL2 rather than natively on Windows, Helicon routes to the WSL2 distribution and translates paths in both directions. The agent sees Linux paths, the Windows UI shows Windows paths, and you stop hand converting between /mnt/c and C:\\ every time something breaks.","updated":"2026-09-19"},{"url":"https://helicon.sh/compare/muse-code-terminal","markdown":"https://helicon.sh/compare/muse-code-terminal.md","title":"Helicon vs the muse terminal: Muse Code with a UI","answer":"The muse terminal TUI is the official way to run Muse Code and it stays the fastest path for a single task in one repo. Helicon is a desktop and web GUI over the same CLI: it adds persistent session history across projects, inline diffs, a visible approval queue and per thread cost, and it can resume sessions the TUI started.","updated":"2026-09-19"},{"url":"https://helicon.sh/compare/vs-code-extension","markdown":"https://helicon.sh/compare/vs-code-extension.md","title":"Helicon vs VS Code Muse Code extensions","answer":"VS Code extensions put Muse Code in a panel next to the file you are editing, which is the right place for a quick change. Helicon is a separate window whose job is the session list: every project, every thread, resume, diffs, approvals and cost in one place, independent of which editor you happen to have open.","updated":"2026-09-19"},{"url":"https://helicon.sh/compare/zed-acp","markdown":"https://helicon.sh/compare/zed-acp.md","title":"Helicon vs Zed + muse-acp for Muse Code","answer":"Zed can drive Muse Code through an Agent Client Protocol bridge, which puts the agent in the editor you are already writing in. Helicon is a separate desktop and web app built directly on the Muse Code Session Protocol, so it keeps the session list, approvals, diffs and cost across every project rather than inside one editor window.","updated":"2026-09-19"},{"url":"https://helicon.sh/compare/jetbrains-acp","markdown":"https://helicon.sh/compare/jetbrains-acp.md","title":"Helicon vs JetBrains + ACP for Muse Code","answer":"A JetBrains ACP plugin puts Muse Code in the IDE tool window, next to the refactoring and inspection tools you already use. Helicon is a separate desktop and web app on the Muse Code Session Protocol, built for the session list: every project, thread, diff, approval and cost figure in one place regardless of IDE.","updated":"2026-09-19"},{"url":"https://helicon.sh/compare/claude-code-desktop","markdown":"https://helicon.sh/compare/claude-code-desktop.md","title":"Helicon vs the Claude Code desktop app","answer":"They are the same shape for different agents. The Claude Code desktop app is Anthropic's official window over Claude Code and its subscription. Helicon is an unofficial, MIT licensed desktop and web app over Meta's Muse Code CLI and your existing Muse Code subscription. Pick by which agent and which billing relationship you already have.","updated":"2026-09-19"},{"url":"https://helicon.sh/compare/codex-app","markdown":"https://helicon.sh/compare/codex-app.md","title":"Helicon vs the Codex desktop app","answer":"The Codex desktop experience wraps OpenAI's coding agent and your OpenAI plan. Helicon wraps Meta's Muse Code CLI and your Muse Code subscription. Both give a terminal agent a window with projects, sessions, diffs and approvals. The choice is decided by which agent you already pay for, not by the interface.","updated":"2026-09-19"},{"url":"https://helicon.sh/compare/cursor","markdown":"https://helicon.sh/compare/cursor.md","title":"Helicon vs Cursor for Muse Code users","answer":"Cursor is a full AI editor with its own agent, its own models and its own subscription. Helicon is not an editor: it is a desktop and web client for Meta's Muse Code CLI that reuses the subscription you already pay for. If you want an editor, that is Cursor. If you want a home for Muse Code sessions, that is Helicon.","updated":"2026-09-19"},{"url":"https://helicon.sh/compare/windsurf","markdown":"https://helicon.sh/compare/windsurf.md","title":"Helicon vs Windsurf for Muse Code users","answer":"Windsurf is an agentic AI editor with its own models and subscription, built to be the place you write code. Helicon is a free MIT client for Meta's Muse Code CLI that gives your existing subscription a window: projects, sessions, diffs, approvals and cost, beside whatever editor you already use.","updated":"2026-09-19"},{"url":"https://helicon.sh/compare/opencode","markdown":"https://helicon.sh/compare/opencode.md","title":"Helicon vs OpenCode for Muse Code subscribers","answer":"OpenCode is an open-source agent harness that you point at providers, usually with its own API billing. Helicon is not a harness at all: it is a desktop and web interface for Meta's Muse Code CLI, so the agent, the models and the subscription are the ones you already have, with no second route to pay for.","updated":"2026-09-19"},{"url":"https://helicon.sh/compare/aider","markdown":"https://helicon.sh/compare/aider.md","title":"Helicon vs Aider: GUI over CLI, two ways","answer":"Aider is a terminal pair programmer that works in tight commit sized loops against your own API keys. Helicon is a graphical client for Meta's Muse Code CLI on your existing subscription, built for supervising longer agent threads across several repositories rather than driving one edit at a time.","updated":"2026-09-19"},{"url":"https://helicon.sh/compare/cline","markdown":"https://helicon.sh/compare/cline.md","title":"Helicon vs Cline for agent supervision","answer":"Cline is an agent that lives in the VS Code sidebar, brings its own provider configuration and shows approvals inside the editor. Helicon is a standalone desktop and web app for Meta's Muse Code CLI, built so the session list, approvals and cost survive independently of any editor window.","updated":"2026-09-19"},{"url":"https://helicon.sh/compare/warp","markdown":"https://helicon.sh/compare/warp.md","title":"Helicon vs Warp for running Muse Code","answer":"Warp makes the terminal better: blocks, history, its own agent. Running Muse Code inside it is still a terminal session. Helicon is a purpose built client that indexes projects and sessions, renders diffs inline, queues approvals and reports cost, because those come from the Muse Code protocol rather than from the shell.","updated":"2026-09-19"},{"url":"https://helicon.sh/compare/other-muse-code-guis","markdown":"https://helicon.sh/compare/other-muse-code-guis.md","title":"Muse Code GUI comparison: Helicon and the others","answer":"Several open-source Muse Code GUIs exist and Helicon does not claim to be the only one. What separates them in practice is packaging and protocol depth: a signed Windows installer with auto update, native Windows plus WSL2 path translation, cross project session resume including terminal sessions, and approvals mapped one to one.","updated":"2026-09-19"},{"url":"https://helicon.sh/features/session-history","markdown":"https://helicon.sh/features/session-history.md","title":"Muse Code session history: find and resume any thread","answer":"Helicon keeps a local index of every Muse Code session on the machine, grouped by the working directory the agent ran in. Each session keeps its full turn history and resumes in one click, including sessions you started in the muse terminal TUI, so closing a terminal tab no longer loses the thread.","updated":"2026-09-19"},{"url":"https://helicon.sh/features/inline-diffs","markdown":"https://helicon.sh/features/inline-diffs.md","title":"Inline diffs for Muse Code: see every edit in the thread","answer":"Helicon renders each edit as a diff inline in the thread, at the exact turn that produced it, instead of printing a patch into scrollback. A file viewer sits beside the conversation, so any path Muse Code mentions opens with syntax highlighting without leaving the app.","updated":"2026-09-19"},{"url":"https://helicon.sh/features/approvals","markdown":"https://helicon.sh/features/approvals.md","title":"Muse Code approvals, surfaced and never bypassed","answer":"Helicon surfaces every approval request Muse Code raises, as it arrives, and never batches or bypasses one. The three protocol modes, onRequest, promptUnmatched and denyUnmatched, are mapped one to one, so the app behaves exactly as the CLI would. Allow all exists but sits behind a deliberate opt in.","updated":"2026-09-19"},{"url":"https://helicon.sh/features/cost-and-usage","markdown":"https://helicon.sh/features/cost-and-usage.md","title":"Muse Code cost tracking: what each thread would cost","answer":"Helicon shows what each Muse Code thread would have cost at Meta's published per token rates, broken down by day, by model and by thread. It is a meter reading rather than an invoice: your subscription already paid, and this is how you find out what it did.","updated":"2026-09-19"},{"url":"https://helicon.sh/features/plan-limits","markdown":"https://helicon.sh/features/plan-limits.md","title":"Muse Code usage limits: the 5 hour window, in the sidebar","answer":"Helicon reads the usage Muse Code itself reports and shows the 5 hour rolling window and the weekly cap in the sidebar and on the usage page. It is the same number the CLI has, surfaced where you can see it before a long run rather than after a refusal.","updated":"2026-09-19"},{"url":"https://helicon.sh/features/projects-and-worktrees","markdown":"https://helicon.sh/features/projects-and-worktrees.md","title":"Projects and git worktrees in a Muse Code GUI","answer":"Helicon's sidebar is organised by working directory. Every Muse Code thread appears under the project it ran in, and isolated git worktrees show up as their own entries with a badge, so running four agents across three repositories stays legible instead of becoming four terminal tabs.","updated":"2026-09-19"},{"url":"https://helicon.sh/features/command-palette","markdown":"https://helicon.sh/features/command-palette.md","title":"Command palette and keyboard control for Muse Code","answer":"Helicon is fully keyboard operable. A command palette jumps to any project, session or action, slash commands work in the composer the way they do in the CLI, and a picker switches model and reasoning effort mid thread. Nothing in the app requires a pointing device.","updated":"2026-09-19"},{"url":"https://helicon.sh/features/file-viewer","markdown":"https://helicon.sh/features/file-viewer.md","title":"A file viewer beside the Muse Code thread","answer":"Helicon puts a file viewer next to the thread. You can browse the project tree, read source with syntax highlighting, preview and edit Markdown, and open images, video and PDFs. Paths the agent mentions in the conversation open there directly, so reviewing a change does not mean switching apps.","updated":"2026-09-19"},{"url":"https://helicon.sh/features/remote-daemon","markdown":"https://helicon.sh/features/remote-daemon.md","title":"Run Muse Code on a remote machine, drive it from a browser","answer":"Helicon is one React codebase that ships two ways: as a Tauri desktop app with a local daemon, and as a web app pointed at a daemon running elsewhere. That means you can run Muse Code on a workstation or a server and supervise it from a browser on a laptop, with the same sidebar, diffs and approvals.","updated":"2026-09-19"},{"url":"https://helicon.sh/features/subagents-and-workflows","markdown":"https://helicon.sh/features/subagents-and-workflows.md","title":"Watch Muse Code subagents and workflows in one window","answer":"Muse Code can fan work out to parallel subagents and run multi step workflows. In a terminal that is interleaved text. Helicon renders it as structure, so you can see which agents are running, cancel a workflow run, and skip or retry individual agents without restarting the thread.","updated":"2026-09-19"},{"url":"https://helicon.sh/features/goals","markdown":"https://helicon.sh/features/goals.md","title":"Set, pause and steer a Muse Code goal from the UI","answer":"Muse Code goals give a thread a standing objective. Helicon exposes the whole lifecycle in the interface: set a goal, pause it, resume it, change it or clear it, from either the goal panel or the composer, so steering a long run does not mean remembering command syntax.","updated":"2026-09-19"},{"url":"https://helicon.sh/features/background-tasks","markdown":"https://helicon.sh/features/background-tasks.md","title":"Background and stop controls for running Muse Code tools","answer":"When a Muse Code tool call is taking too long, Helicon lets you send it to the background, stop that one call, or stop everything running, without ending the thread. Workflow runs can be cancelled, and individual agents inside them skipped or retried.","updated":"2026-09-19"},{"url":"https://helicon.sh/guides/muse-code-windows-without-wsl","markdown":"https://helicon.sh/guides/muse-code-windows-without-wsl.md","title":"How to run Muse Code on Windows without WSL","answer":"Muse Code runs natively on Windows, so WSL2 is optional. Install the CLI on Windows, run muse login in PowerShell, and Helicon drives it directly with your own Windows paths and PowerShell for shell commands. If only a WSL2 install is present, Helicon routes there instead and translates paths both ways.","updated":"2026-09-19"},{"url":"https://helicon.sh/guides/resume-a-muse-session","markdown":"https://helicon.sh/guides/resume-a-muse-session.md","title":"How to resume a Muse Code session you started earlier","answer":"Open Helicon, find the project in the sidebar, and pick the session. The thread reopens with every turn, tool call, diff and approval in place, and you can carry on from there. Sessions started in the muse terminal TUI are discovered by the daemon and resume the same way.","updated":"2026-09-19"},{"url":"https://helicon.sh/guides/remote-daemon-setup","markdown":"https://helicon.sh/guides/remote-daemon-setup.md","title":"How to run Muse Code on a remote machine with a web UI","answer":"Run the Helicon daemon and the muse CLI on the machine that holds your code, then open the web build in a browser and point it at that daemon. You get the same sidebar, diffs, approvals and cost view as the desktop app, with the agent running next to the repository instead of on your laptop.","updated":"2026-09-19"},{"url":"https://helicon.sh/guides/see-muse-code-cost","markdown":"https://helicon.sh/guides/see-muse-code-cost.md","title":"How to see what a Muse Code thread cost","answer":"Open the usage page in Helicon. It shows what each thread would have cost at Meta's published per token rates, grouped by day, by model and by thread, alongside the 5 hour window and weekly cap as Muse Code reports them. It is a meter reading, not a bill.","updated":"2026-09-19"},{"url":"https://helicon.sh/guides/review-agent-changes","markdown":"https://helicon.sh/guides/review-agent-changes.md","title":"How to review what a Muse Code agent changed","answer":"Scroll the thread. Each edit is rendered as a diff at the turn that produced it, tool calls show the command and its output, and approvals show what you allowed and when. Click any path the agent mentions and it opens in the file viewer beside the conversation.","updated":"2026-09-19"},{"url":"https://helicon.sh/guides/run-parallel-agents","markdown":"https://helicon.sh/guides/run-parallel-agents.md","title":"How to run several Muse Code agents in parallel","answer":"Create an isolated git worktree per task so the agents never touch the same files, add each one to Helicon as its own project, and start a thread in each. The sidebar then shows every run in one list, marked by whether it is running, finished, or blocked on your approval.","updated":"2026-09-19"},{"url":"https://helicon.sh/guides/keyboard-shortcuts","markdown":"https://helicon.sh/guides/keyboard-shortcuts.md","title":"Muse Code GUI keyboard shortcuts and slash commands","answer":"Open the command palette to jump to any project, session or action. Slash commands work in the composer the way they do in the CLI, and the model and reasoning effort picker changes the next turn without restarting the thread. No part of Helicon requires a pointing device.","updated":"2026-09-19"},{"url":"https://helicon.sh/guides/muse-cli-not-found","markdown":"https://helicon.sh/guides/muse-cli-not-found.md","title":"Fix: Helicon cannot find the muse CLI","answer":"Helicon drives the muse CLI and cannot work without one that is installed and logged in. Check muse --version in the shell that holds your install, run muse login there, and confirm which route Helicon took: native on Windows, inside WSL2, or the system PATH on macOS and Linux.","updated":"2026-09-19"},{"url":"https://helicon.sh/guides/macos-first-launch","markdown":"https://helicon.sh/guides/macos-first-launch.md","title":"Fix: macOS blocks Helicon on first launch","answer":"The macOS DMG is updater signed but not Apple notarized yet, so Gatekeeper warns on first launch. Right click the app in Applications and choose Open, then confirm in the dialog. macOS remembers the decision and every later launch is normal. Notarization is a known gap, not a policy.","updated":"2026-09-19"},{"url":"https://helicon.sh/guides/from-terminal-to-gui","markdown":"https://helicon.sh/guides/from-terminal-to-gui.md","title":"Moving from the muse terminal to a GUI without losing anything","answer":"Nothing has to be migrated. Helicon reads the same Muse Code state the CLI writes, so sessions you started in the terminal appear in the sidebar with their history and resume from the app. The CLI keeps working unchanged, and most people end up using both for different jobs.","updated":"2026-09-19"},{"url":"https://helicon.sh/use-cases/windows-developers","markdown":"https://helicon.sh/use-cases/windows-developers.md","title":"Muse Code for Windows developers","answer":"Windows has historically been the worst platform for terminal coding agents: WSL2 plumbing, mixed path formats and unsigned binaries. Helicon ships a signed Windows installer with auto update, runs Muse Code natively with PowerShell for shell commands, and falls back to Muse Code inside WSL2 with two way path translation.","updated":"2026-09-19"},{"url":"https://helicon.sh/use-cases/macos-power-users","markdown":"https://helicon.sh/use-cases/macos-power-users.md","title":"Muse Code for macOS power users","answer":"If you run Muse Code across several repositories on a Mac, the constraint is not the agent, it is keeping track of it. Helicon gives every thread a home: projects grouped by directory, sessions with full history and resume, inline diffs, an approval queue and cost at API rates, in a universal DMG.","updated":"2026-09-19"},{"url":"https://helicon.sh/use-cases/parallel-agents","markdown":"https://helicon.sh/use-cases/parallel-agents.md","title":"Running several coding agents in parallel","answer":"Parallelism breaks down at the interface, not the agent. Four threads means four places something can be waiting. Helicon puts every thread in one sidebar grouped by working directory, marks which are running and which are blocked on an approval, and shows what the fan out cost per thread.","updated":"2026-09-19"},{"url":"https://helicon.sh/use-cases/remote-development","markdown":"https://helicon.sh/use-cases/remote-development.md","title":"Muse Code for remote and remote-first development","answer":"Helicon ships the same React UI as a desktop app and as a web app pointed at a daemon elsewhere. Put the daemon and the muse CLI on the workstation or server that holds the code, and supervise from a browser, so the agent runs next to the repository while you stay on a laptop.","updated":"2026-09-19"},{"url":"https://helicon.sh/use-cases/open-source-maintainers","markdown":"https://helicon.sh/use-cases/open-source-maintainers.md","title":"Muse Code for open-source maintainers","answer":"Maintaining several repositories means short bursts of attention across many codebases. Helicon lists every project with its sessions, so picking a repository back up does not mean reconstructing context, and every edit is an inline diff with the approval record beside it before anything reaches a project others depend on.","updated":"2026-09-19"},{"url":"https://helicon.sh/use-cases/freelancers","markdown":"https://helicon.sh/use-cases/freelancers.md","title":"Muse Code for freelancers and consultants","answer":"Client work means several codebases at once and a reason to know what each one consumed. Helicon groups threads by working directory, so each client's work stays separate, keeps the full session history for anything you need to explain later, and shows what each thread would have cost at published per token rates.","updated":"2026-09-19"},{"url":"https://helicon.sh/use-cases/monorepos","markdown":"https://helicon.sh/use-cases/monorepos.md","title":"Muse Code in a monorepo","answer":"A monorepo makes two things harder: keeping parallel agents from colliding, and running a test suite a laptop cannot hold. Helicon answers both by treating isolated git worktrees as separate projects and by letting the daemon live on the machine with the CPU while you watch from a browser.","updated":"2026-09-19"},{"url":"https://helicon.sh/use-cases/terminal-skeptics","markdown":"https://helicon.sh/use-cases/terminal-skeptics.md","title":"A Muse Code GUI for people who like the terminal","answer":"The objection to a GUI over a CLI is that it will be slower and will take something away. Helicon is keyboard first with a command palette, requires no migration because it reads the same sessions the CLI writes, and adds only the things a terminal structurally cannot do: persistent history, cross project triage, and cost.","updated":"2026-09-19"},{"url":"https://helicon.sh/glossary/muse-code","markdown":"https://helicon.sh/glossary/muse-code.md","title":"What is Muse Code? Meta's terminal coding agent","answer":"Muse Code is Meta's AI coding agent. You use it through the `muse` command line tool, which runs on macOS, Linux and Windows, and it works inside a project directory: reading files, editing them, running commands and asking for approval. Other applications can drive it over the Muse Code Session Protocol.","updated":"2026-09-19"},{"url":"https://helicon.sh/glossary/muse-cli","markdown":"https://helicon.sh/glossary/muse-cli.md","title":"What is the muse CLI?","answer":"The muse CLI is the command line tool that runs Muse Code. You install it, authenticate once with `muse login`, and then run `muse` inside a project to start a session. It holds your credentials, and every graphical client for Muse Code, including Helicon, drives this CLI rather than replacing it.","updated":"2026-09-19"},{"url":"https://helicon.sh/glossary/msp","markdown":"https://helicon.sh/glossary/msp.md","title":"What is MSP, the Muse Code Session Protocol?","answer":"The Muse Code Session Protocol, MSP, is the JSON-RPC interface a Muse Code host exposes over stdio when you run `muse serve`. It carries sessions, turns, tool calls, approvals and usage as typed events, so a client can render structure rather than parsing terminal text. Meta ships an MIT licensed SDK for it.","updated":"2026-09-19"},{"url":"https://helicon.sh/glossary/muse-serve","markdown":"https://helicon.sh/glossary/muse-serve.md","title":"What is muse serve?","answer":"`muse serve` starts a Muse Code host that speaks the Muse Code Session Protocol over stdio instead of drawing a terminal interface. Applications launch it to drive sessions programmatically. Helicon starts one host per workspace, so each project directory gets its own process, exactly as the CLI would.","updated":"2026-09-19"},{"url":"https://helicon.sh/glossary/acp","markdown":"https://helicon.sh/glossary/acp.md","title":"What is ACP, the Agent Client Protocol?","answer":"The Agent Client Protocol is a general interface that lets an editor drive any conforming coding agent, so Zed or a JetBrains IDE can use several agents through one integration. Bridges expose Muse Code over ACP. Anything ACP has no vocabulary for, such as Muse Code specific usage reporting, has to be approximated.","updated":"2026-09-19"},{"url":"https://helicon.sh/glossary/ade","markdown":"https://helicon.sh/glossary/ade.md","title":"What is an ADE, an agentic development environment?","answer":"An agentic development environment, or ADE, is the workspace you supervise coding agents from, the way an IDE is the workspace you write code in. Its objects are sessions, approvals, diffs and cost rather than files and build targets, and it assumes you still have an editor open somewhere else.","updated":"2026-09-19"},{"url":"https://helicon.sh/glossary/agent-approvals","markdown":"https://helicon.sh/glossary/agent-approvals.md","title":"What are coding agent approvals?","answer":"An approval is the moment a coding agent stops and asks before running a command or making a change. Muse Code has three modes: onRequest asks every time, promptUnmatched asks when the action is outside the allow list, and denyUnmatched refuses it outright. A client should surface all three unchanged.","updated":"2026-09-19"},{"url":"https://helicon.sh/glossary/git-worktree","markdown":"https://helicon.sh/glossary/git-worktree.md","title":"What is a git worktree, and why agents need them","answer":"A git worktree is an additional working directory attached to the same repository, each on its own branch. For coding agents it is the cheapest real isolation available: two agents in two worktrees cannot edit the same files, and neither needs a full clone of the repository.","updated":"2026-09-19"},{"url":"https://helicon.sh/glossary/subagent","markdown":"https://helicon.sh/glossary/subagent.md","title":"What is a subagent in a coding agent?","answer":"A subagent is a separate agent that a main agent spawns to handle part of a task, usually in parallel with others. It saves wall clock time on work that splits cleanly, such as searching several subsystems at once, and it produces interleaved output that a terminal cannot render legibly.","updated":"2026-09-19"},{"url":"https://helicon.sh/glossary/reasoning-effort","markdown":"https://helicon.sh/glossary/reasoning-effort.md","title":"What is reasoning effort in a coding agent?","answer":"Reasoning effort is a setting that controls how much a model thinks before it answers. Higher effort produces better results on hard problems and uses more tokens and more time. On mechanical work it usually buys nothing, which is why it is worth being able to change it per turn rather than per session.","updated":"2026-09-19"},{"url":"https://helicon.sh/glossary/tui","markdown":"https://helicon.sh/glossary/tui.md","title":"What is a TUI, and why coding agents ship one","answer":"A TUI is a text user interface drawn inside a terminal window, with panels, input and scrolling made out of characters. Coding agents ship one first because it works everywhere, over SSH included, with no packaging. It runs out when you need persistent history, several concurrent threads, or structured views of diffs and cost.","updated":"2026-09-19"},{"url":"https://helicon.sh/glossary/llms-txt","markdown":"https://helicon.sh/glossary/llms-txt.md","title":"What is llms.txt?","answer":"llms.txt is a plain text file at the root of a website that gives language models a clean, Markdown formatted summary of what the site is and an index of the pages worth reading. It exists because parsing rendered HTML is lossy, and a curated index is cheaper and more accurate than crawling.","updated":"2026-09-19"},{"url":"https://helicon.sh/glossary/tauri","markdown":"https://helicon.sh/glossary/tauri.md","title":"What is Tauri, and why build a desktop app with it?","answer":"Tauri is a framework for building desktop applications from web technology, using the operating system's own webview rather than bundling a browser, with a Rust core for native work. The result is a much smaller binary than an Electron equivalent, with code signing and auto update built into the release tooling.","updated":"2026-09-19"}]}