AIWG 2026.6.1 — AIWG Cockpit groundwork (beta), leaner agents, and doc accuracy

AIWG 2026.6.1 — AIWG Cockpit groundwork (beta), leaner agents, and doc accuracy

Released 2026-06-15

A consolidation release on top of 2026.6.0. It lands the foundation of the AIWG Cockpit (a UX-first control plane) as beta groundwork, completes the declarative-Flow and cross-stack-Mission work previewed in June, brings every agent definition under the dispatch ceiling, and reconciles the documentation against source.

Install or upgrade:

npm install -g aiwg          # fresh install (stable)
aiwg refresh                 # update an existing install + redeploy

AIWG Cockpit — beta groundwork

The AIWG Cockpit is a UX-first control plane that sits on top of the AIWG CLI and the per-provider agentic stacks — letting you manage an install, deployed agents, and live multi-stack sessions from one surface, without ever replacing or nerfing the CLI underneath. This release ships the groundwork, not the finished UX.

What's in place (epic #1588):

  • A data-driven core bound to the extension / `aiwg discover` / artifact-index registry — capabilities are derived from the registry, not hardcoded.
  • Instance control normalized on the agentic-sandbox interface (a live session view + running-agents board).
  • Two shells over one shared core — a Tauri (Rust) desktop app and a VS Code extension (#1594).
  • A declarative UI contribution model — extensions contribute screens, actions, workflows, and event-hooks (#1591).
  • Strong local control-surface auth — `127.0.0.1` + Origin + CSRF + per-launch token + OS-keychain handshake (#1595).
  • Lean base, opt-in heavy — Cockpit ships as a separate opt-in `@aiwg/cockpit` package with a base-footprint CI guard (#1593); the base `npm i -g aiwg` footprint is unchanged.

The full operator UX is still in construction — install `@aiwg/cockpit` only if you want to follow the foundation. The complete experience lands in a later release.

# opt-in; not installed by the base CLI
npm install -g @aiwg/cockpit

Declarative Flows + cross-stack Missions are complete

The bulk migration of `flow-*` skills to `flow.aiwg.io/v1` Flows (#1539) and the cross-stack Mission conductor with per-stack executor adapters (#1546) — previewed in 2026.6.0 — are now fully landed. One Mission conductor fans heterogeneous workers across stacks (for example, a Claude session dispatching Codex subagents) over the `runtime:<name>` executor convention. Flows are discoverable via `aiwg discover` and runnable as orchestration.

Leaner agents — every definition under the dispatch ceiling

Oversized agent definitions were silently failing subagent dispatch with `Prompt is too long` at 0 tokens — before the agent did any work. A repo-wide debloat (#1587, #1600) fixes this:

  • Worked examples and restated protocol boilerplate are externalized out of agent definitions into the discoverable example catalog (few-shot coverage preserved via an inline anchor + referenced catalog).
  • A hard 16 KB size ceiling is enforced by `aiwg doctor`, with a locked regression test.
  • `aiwg-steward` was reconciled across its dual sources; `rlm-agent` and several SDLC, forensics, marketing, and media-curator agents were trimmed under the ceiling.

Docs match the code

A `doc-sync code-to-docs` pass reconciled every skill/agent count in the documentation against on-disk source:

  • Kernel skills `16`/`19` → 20 (the self-maintenance ops set grew to 10: `aiwg-issue`, `aiwg-pr`, `aiwg-mission` joined).
  • Addons `27`/`28` → 29; addon skill surface `~270` → ~214.
  • Per-framework counts corrected — research `20` → 39 skills, security-engineering `7` → 27 skills, sdlc `90`/`220` → 93 agents.
  • Three doc-to-doc contradictions (the same fact carried as three different stale values) resolved.
  • Hermes's top-level kernel documented as the global 20-skill set (the generator deploys the global kernel, not a 9-skill subset).

Release announcements and dated blog posts were left untouched as immutable historical records.

Other changes

  • `release-publication-verify` skill (#1599) — a post-tag verifier that confirms a tag actually published (npm dist-tag + Gitea/GitHub release artifacts).
  • `aiwg-steward` "Built With AIWG" badge (#1596) — opt-in README attribution badge on request.
  • `aiwg regenerate` additively installs the `@AIWG.md` hook into operator-owned provider files without clobbering them (#1597, #1579); `aiwg doctor` flags drift on non-managed twin files.
  • `package-all-plugins` scoped to plugin packaging so native-release discovery routes correctly (#1598).
  • Docs site reflects all 11 providers; README gains a hero masthead + badges; OpenCode `--help` assertion covers stderr; docsite deploy `~`-resolver fixed; stray `WARP.md` backups removed.

Upgrade notes

  • No action required. All changes are additive or self-healing on the next `aiwg refresh` / `aiwg use`.
  • AIWG Cockpit is beta groundwork — `@aiwg/cockpit` is opt-in and not installed by the base CLI; the base footprint is unchanged. The control-plane UX is still in construction (#1588).