AIWG 2026.7.0 - "MCP elicitation and native interaction routing"

AIWG 2026.7.0 - "MCP elicitation and native interaction routing"

Released: 2026-07-01 Channel: stable (`npm install -g aiwg`)

This release adds a native human-in-the-loop path for MCP clients. AIWG now ships an `ask-user` MCP interaction tool that emits protocol-native elicitation requests when the connected client supports them, and falls back to a markdown prompt when it does not. That gives operators a consistent interaction surface without forcing every provider or MCP host to expose the same UI capability on day one.

It also records interactive-question support in the provider capability matrix, so AIWG can route prompts through the best available native UX. Codex guidance now documents its mode-gated `request_user_input` path, and Cockpit's merged console topology ADR is accepted for the next stage of session UX work.


What changed

MCP `ask-user` interaction tool

The MCP server now exposes an `ask-user` interaction tool backed by a shared elicitation helper. When a client advertises elicitation support, AIWG sends a structured request with schema-backed choices. When that support is unavailable, the same request is rendered as a markdown fallback so the session can continue through ordinary text.

The behavior is covered by unit tests for protocol-native elicitation, markdown fallbacks, and response normalization.

Native interaction routing

The provider capability matrix now includes native interactive-question support. That lets AIWG distinguish providers that can ask structured questions through their own UX from providers that need a text fallback. The bundled Codex rule documents the `request_user_input` mechanism and the mode gating around it.

Cockpit console topology

AIWG accepted the Cockpit merged console topology ADR, capturing the direction for a session UX that unifies operator console work without losing provider native behavior.

June 2026 report

The June 2026 AIWG progress report is published under the docs blog and the docs manifests were refreshed.

Upgrade

npm install -g aiwg
aiwg refresh

No breaking changes.