muse-code-acp logo

muse-code-acp

Free

Unofficial ACP adapter for Meta's Muse Code — use Muse in Zed, VS Code, and other Agent Client Protocol editors with streaming, tools, sessions, modes, auth, and skills.

Visit Website
Related by shared tags and keywordsiris-agentHarnessDeskcodeagent
ai-agentacpagent-client-protocolclicoding-agentaiai assistantautomation

Overview

muse-code-acp is an unofficial adapter that allows Muse Code to be used through an Agent Client Protocol (ACP) client, such as Zed or VS Code with an ACP extension. It is a community project and is not affiliated with, endorsed by, or supported by Meta. The adapter requires Node.js 22+ for npm installation and a separately installed Muse Code host, with authentication through browser login or META_API_KEY. It speaks ACP over stdio and is launched through an editor rather than as an interactive terminal chat UI.

The default SDK backend supports prompt execution with streamed text, tool calls/results, cancellation and multi-turn continuity. It also supports prompt context including PNG/JPEG/GIF/WebP images, resource links and embedded text; session navigation with paginated list, full history load, resume without replay, close, and native fork; permissions; modes; model settings; MCP; file changes; workflows; goals; and mid-turn steering when explicitly negotiated by the client. The adapter starts or resumes native sessions, translates message/tool items into ACP updates, routes permission requests to the client, and cancels using turn/cancel.

Some ACP features and Muse terminal UI features are not implemented. Delegated workers and token usage are explicitly reported as unavailable. The legacy exec backend runs muse exec --json per turn and supports the echo provider, store-based session listing, and stdio MCP servers only.

Pricing

Free

Detailed plans have not been confirmed in our catalog. Check the official website for current limits and billing terms.

Visit Website

Prices and limits may change. Confirm the currency, billing period, seat minimum and usage caps on the official website.

Use Cases

  • Teams use muse-code-acp to access Muse Code from Zed or VS Code with an ACP extension.
  • Teams use muse-code-acp for headless operation by providing META_API_KEY to the adapter process instead of browser login.
  • Teams use muse-code-acp to stream text, tool calls/results, cancellation and multi-turn continuity during prompt execution.
  • Teams use muse-code-acp to include PNG/JPEG/GIF/WebP images, resource links and embedded text as prompt context.
  • Teams use muse-code-acp to navigate sessions with paginated list, full history load, resume without replay, close, and native fork.
  • Teams use muse-code-acp to run skills as slash commands, planning and Git reviews.
  • Teams use muse-code-acp to connect client-provided stdio and HTTP MCP servers.
  • Teams use muse-code-acp to run the legacy exec backend with muse exec --json per turn.

Features

AI assistant

Natural language interface

Workflow automation

Reviews

No reviews yet. Be the first to share your experience!

Rankings & collections