v0.6.0

Features

• Expose verified SDK approval policies with independent sandbox controls, provider-aware model selection, requested reasoning effort, and client gateway settings.
• Report live session progress, bounded stored output, structured failures, observed authentication, and asynchronous task state through negotiated capabilities.
• Support embedded prompt bytes and independent session commands while retaining explicit limits for unsupported host features.

Fixes

• Create and restore sessions without starting a catalog-only host. Model choices update when an execution host becomes ready; /models explicitly refreshes choices before a turn. Clients must accept deferred configuration updates and must not treat the initial model menu as a complete catalog.
• Preserve the initiating SDK failure, startup deadline, cancellation, and whether a turn may have been submitted. Startup deadlines cover the full operation rather than restarting at each phase.
• Keep workflow cancellation targeted and preserve verified task visibility without automatically replaying uncertain requests.

Compatibility and upgrading

Requires Node.js 22+ and @muse-code/sdk@0.1.1. Muse 1.1.1 remains the pinned baseline; the expanded 62-test real-host loopback suite also passes on 1.2.1. A targeted populated-history startup regression was additionally checked on 1.3.0; this is not a claim of full 1.3.0 compatibility.

Long-lived native history can still slow host initialization, especially under concurrency. This release removes unnecessary catalog hosts; it does not fix Muse's native history traversal. See startup measurements and limitations. Applications that scope history to a scan must retain that data directory for subsequent session restoration.

v0.5.0

Features

• Report observed host model and approval-mode changes through opt-in muse/sessionState metadata, including idle sessions. Host-offered persistent-rule choices remain explicitly unverified until a public host report establishes success or failure. Observation never changes policy or retries a turn.
• Expose synchronized ACP mode config options with the same validation and persistence as set_mode, including updates after model, effort and /plan changes. SDK clients cannot select exec-only bypass modes.
• Publish advisory muse/hostCompatibility metadata with the detected host version and pinned/served schema fingerprints.

Fixes

• Complete multi-stage shell approvals on the SDK backend when Muse advances a requirement through approval/updated without re-issuing a request. Ask once per unresolved stage and submit only host-offered choices. Permission titles show current stage arguments and position in plain ACP clients.
• Bound pending host requests with no outstanding client call or host progress using MUSE_CODE_ACP_STALL_MS (default 10 seconds). Stalled approvals and user input fail with diagnostics; already-answered user input is not requested again.
• Require startup of ACP-provided MCP servers explicitly, restoring prompt failures for unauthorized, malformed and unreachable HTTP endpoints on Muse 1.2.1. User-configured server modes are preserved.
• Execute /goal <task> once with an explicit persistence limitation. Recognize slash commands across prompt text blocks and preserve attached text, resources and images through planning and review.
• Add review focus/default Git targets, local goal-status guidance, and bare /plan mode selection. Mixed requests containing planning remain planning-only.

Compatibility and upgrading

Requires Node.js 22+ and pinned @muse-code/sdk@0.1.1. Muse 1.1.1-R2514.1 remains the supported baseline. The complete 29-test loopback suite also passes on 1.2.1-R2847.1, with three legacy-continuation paths asserting the documented host limitation: saved :auto-review exec sessions cannot resume in muse serve. SDK-created continuity passes. Affected legacy sessions receive an actionable error and need a new ACP session or Muse with reviewer support; no saved profile is rewritten.

The multi-stage approval workaround is now included on npm; SDK users no longer need the exec workaround for that hang. The underlying SDK routing defect is tracked in upstream issue #10. Native automatic approval remains unverified; default sandboxing and real host permission gates remain enabled.

Pin the Muse binary outside the launcher's replaceable cache. Direct artifact URLs and SHA-256 checks are recorded in CI. The opt-in session-state extension reports observations only; it does not synchronize ACP settings. Policy-persistence failure recovery is covered by public-wire fixtures; no induced real-host policy-write failure is claimed.

Verification

Release workflow passed on tagged commit ffb42f7. Local checks passed 377 tests and packed-install smoke. CI passed 368 deterministic checks (9 host-dependent checks skipped in the no-host build job), all 29 required Linux Muse loopback tests, and macOS ARM64 standalone smoke. All 29 loopback tests also passed locally on Muse 1.1.1-R2514.1 and 1.2.1-R2847.1.

The published @bex-co/muse-code-acp@0.5.0 installation passed initialize/new/prompt/stream/end_turn/close against the isolated public-wire fixture. npm reports latest: 0.5.0; package SHA-1 matches the publish log.

v0.4.1

0.4.1 (2026-09-13)

Documentation

• Correct the README's host lifecycle, public session discovery and unsupported-worker claims; describe current session, prompt, workflow and negotiated capabilities.
• Add Node.js requirements, pinned-host login and Zed environment examples, explicit host compatibility limits, and accurate standalone distribution scope.
• Group user documentation before development details and use absolute repository links that work from npm.

Documentation-only patch; runtime behavior and dependencies are unchanged. Use Muse Code 1.1.1-R2514.1 with SDK 0.1.1; Muse 1.2.1-R2847.1 remains unsupported.

v0.4.0

0.4.0 (2026-09-13)

Features

• Fork native Muse sessions with isolated branch history, preserved model selection and verified restart continuity. Negotiated clients can select a completed-turn boundary.
• Show bounded, observed before/after file diffs and negotiated per-turn file-change reports. Reports explicitly mark partial coverage and concurrent-edit uncertainty; unknown preimages are no longer presented as file creation.
• Discover sessions through public, lease-free pagination, with scoped cursors, title/recency updates and optional fork provenance. Complete chronological load still uses validated export replay.
• Add guarded plan mode and Git review workflows. Planning disables workspace writes and shell execution; implementation requires an explicit mode change.
• Observe native goal state and progress, including autonomous work after the foreground prompt ends. Goal controls remain unadvertised where no verified public API exists.
• Add a reproducible standalone macOS ARM64 build and real-host smoke profile. The npm package remains the Node.js distribution; the standalone adapter still requires an external Muse host.

Fixes

• Preserve fail-closed behavior when Muse encounters approval-settlement failures, with a safe numeric MSP error code for diagnosis.
• Bound file evidence and session discovery resources, close discovery hosts during disposal, and retire timed-out metadata hosts without replaying completed prompts.
• Publish through explicit GitHub Actions dispatch with OIDC authentication, after validating the exact release commit.

Upgrading from npm 0.1.x

The previous GitHub 0.2.0/0.3.0 releases did not reach the public npm registry. This release also delivers their SDK-default execution backend, interactive ACP approvals, session close/resume, host reuse, negotiated mid-turn steering, embedded editor context, runtime model discovery, and HTTP MCP support with truthful local diagnostics.

Requires Node.js 22+ and the verified Muse Code 1.1.1-R2514.1 host with muse serve, selected with MUSE_CODE_EXECUTABLE, and pinned @muse-code/sdk@0.1.1. Configure credentials through Muse login or META_API_KEY. Explicit legacy execution remains available with MUSE_CODE_ACP_BACKEND=exec, with its documented capability differences.

Known limits

Muse 1.2.1-R2847.1 is not supported: six of 23 real-host checks failed because legacy exec sessions retained an unavailable :auto-review permission profile, and failed HTTP MCP connections no longer failed the prompt. Use the verified 1.1.1 host; do not disable permissions or sandboxing to work around these differences.

This is an unofficial adapter, not a claim of complete ACP/reference parity. Durable compaction, delegated child execution, scheduled retry observations, rich-output retrieval, multiple authorized roots, URL elicitation, account/service-tier APIs, native session deletion and broader approval-policy enforcement remain blocked or unverified on the tested host. File-change reports are partial; session indexes are eventually consistent. Default sandboxing and real host-provided permission gates remain enabled.

v0.3.0

0.3.0 (2026-09-12)

Features

• close Muse ACP sessions cleanly (#4) (0aa9979)
• discover Muse models and forward embedded editor context (5188179)
• forward ACP prompt content to Muse (#3) (3beeee8)
• resume Muse ACP sessions without replay (#5) (dfc1d31)
• reuse Muse hosts and support negotiated mid-turn steering (3b26891)
• skills: add project PM and loop-worker workflows (d5a2e7d)
• support HTTP MCP servers and local connection diagnostics (9b9113e)

Bug Fixes

• harden ACP session lifecycle and prompt metadata (7b1255f)

v0.2.0

0.2.0 (2026-09-12)

Features

• make SDK the default backend with session continuity (m6) (bd4f1c3)
• ship interactive SDK approvals and resilient turns (m5) (be80f1c)
• ship SDK backend ACP wire contracts (m4) (dcf9081)

Bug Fixes

• harden SDK interactions and gate release publishing (7fe495b)

v0.1.1

0.1.1 (2026-08-28)

Bug Fixes

• normalize Muse ACP reliability signals (768f78e)