Helicon vs Zed with an ACP bridge

At a glance

What each one is

The Agent Client Protocol lets an editor talk to any conforming agent. Bridges exist that expose Muse Code over ACP so Zed and JetBrains IDEs can use it. You get the agent inside the editor, with the editor's own buffers, diffs and keybindings, and you can swap agents without changing editors.

Helicon does not go through a bridge. It speaks the Muse Code Session Protocol over JSON-RPC to muse serve using Meta's MIT SDK, which means capabilities that are specific to Muse Code, such as the exact approval modes and the usage reporting, arrive intact rather than flattened into a generic agent interface.

Where they actually differ

Protocol fidelity

A bridge maps Muse Code onto a general agent interface. Anything the general interface has no word for has to be dropped or approximated. Helicon reads the protocol directly, so approval modes, reasoning effort, subagents, goals and usage arrive as they are.

What the interface is about

The editor panel is about the file you are in. Helicon's sidebar is about the session you are resuming. Those are different jobs, and which one you want depends on whether you are writing code or supervising agents.

Where the history lives

Helicon keeps a local index of projects, sessions and turns in SQLite, so history is not tied to a workspace being open in a particular editor.

Remote work

The same Helicon UI runs as a web app pointed at a daemon on another machine, so a laptop can drive agents on a workstation or a server without SSH forwarding an editor session.

Choose Zed with an ACP bridge if

• You live in Zed and want the agent in the same window as your buffers.
• You want to switch between several agents behind one editor interface.
• You prefer the editor's native diff and multibuffer review flow.

Choose Helicon if

• You want Muse Code specific behaviour surfaced exactly, not bridged.
• You supervise several threads across repos and want one list.
• You want cost and approval history that outlives the editor session.
• You are on Windows and want an installer that updates itself.

Can you use both?

Use the editor bridge while you are writing, and Helicon when you are supervising. Both run against the same muse CLI and the same subscription, so nothing has to be chosen once and for all.

Helicon is one Muse Code GUI of several, and that page lists the rest. Helicon is free and MIT licensed, and you can try Helicon in your browser on sample data before you install anything.