AIWG 2026.10.11 - Leaner session catalogs and steadier helper CLIs

AIWG 2026.10.11 keeps your session catalog smaller and more accurate. Grok Bot conversations are no longer copied into every project, and large images from tool output are stored once. Handing work to helper CLIs such as Codex and Muse is also more reliable: every worker now starts with your project's AIWG rules, and a misbehaving worker is stopped instead of left running.

Grok Bot conversations count once

Grok Bot keeps conversations per account, not per project. Before, every project that read the same Grok Bot folder imported its own copy of every conversation, and searches across projects counted each one several times.

Now each conversation is imported once into a shared host catalog, and each project keeps a light reference to it. `aiwg sessions list`, `search` and `analytics` in a project show those conversations as before, and totals count each one once. Copies imported by older versions stay readable; nothing is deleted.

Big tool-output images stored once

Screenshots and generated images that tools return (for example Codex `view_image`) used to be saved inline in session text, often several megabytes each and repeated. They are now stored once per catalog by content hash and linked from the event, so catalogs stay small and searches don't wade through image data.

Helper workers start with your project's rules

When AIWG launches a helper CLI in a fresh worktree, it now deploys AIWG context for every provider you configured, all in one pass. Muse is started with `--trust-workspace`, so it loads your project's rules, skills and hooks. If a worker would start without any AIWG context, the launch is refused with a clear fix instead of running blind.

Runaway workers are stopped

A worker that floods its output past the size limit is now always stopped, including one that writes just over the limit and then goes idle. On Linux with systemd, AIWG force-stops the worker's whole unit, so nothing it started is left behind.

Retries and verification are also less likely to be blocked for no reason: AIWG can now tell a worker's own leftover processes apart from an unrelated helper CLI running in parallel.

More dependable releases and installs

If signing fails after a release is published to npm, a rerun now picks up the published packages and finishes signing instead of failing. On a clean machine, `aiwg doctor` no longer reports a false discovery error when `aiwg` isn't on your PATH, and the first `aiwg use` adds AIWG's `.gitignore` entries.

If you are upgrading

• Redeploy to pick up the worker changes: `aiwg use all`.
• Requalify worker approvals, because the Muse launch arguments changed: `aiwg doctor --probe-workers --qualify`.
• Nothing to do for Grok Bot or images. New imports use the new storage automatically.

Full technical detail is in the CHANGELOG entry.