AIWG 2026.10.0 - Muse Code stable, gates and decision studies

AIWG 2026.10.0 promotes the Muse Code provider to stable, adds native Muse session discovery, fixes a Factory settings corruption bug, and ships more…

AIWG 2026.10.0 - Muse Code stable, gates and decision studies

AIWG 2026.10.0 promotes the Muse Code provider to stable, adds native Muse session discovery, fixes a Factory settings corruption bug, and ships more experimental, default-off gates and decision-study work.

What changed

  • Muse Code is stable: `--provider muse` graduates from experimental, backed

by a Linux walkthrough on Muse Code 1.4.2, a path security review, and release notes. `aiwg use all --provider muse` now installs the managed `SessionStart` hook and an opted-in `--mcp` profile, and `aiwg doctor` gains a Muse Code native extensions section.

  • Muse session discovery: `aiwg sessions discover --muse-root <path>`

imports Muse's own session logs for a workspace. It runs only for an explicitly authorized root and matches workspaces from facts recorded in the logs.

  • Factory settings safety: Factory deploys no longer corrupt glob or URL

values in `~/.factory/settings.json`, and a hand-edited settings file is backed up before it is rewritten.

  • Gates (experimental, default-off): gate-pack discovery and CLI, project

gate floors in `aiwg.config`, and addon/extension bundle metric providers.

  • Decision studies (experimental, default-off): D17 and D29 calibration

and held-out study tooling, issue-triage, routing, and context-pruning pilots. Live qualification remains pending where each entry says so.

Try it

Update with `npm install -g [email protected]`. Muse users can deploy with `aiwg use all --provider muse` in a trusted workspace. The versioning guide describes the stable-channel policy.

The full change history is in the changelog.