Skip to content

v2026.7.18

Choose a tag to compare

@jmagly jmagly released this 23 Jul 20:03
· 441 commits to main since this release
v2026.7.18
d8c0d8c

AIWG 2026.7.18 - "Web-first CLI and packaged Cockpit"

Released: 2026-07-23
Channel: stable

AIWG 2026.7.18 is a corrective package release for the lightweight web-backed
CLI and Cockpit distributions introduced in 2026.7.17. It makes the documented
no-configuration install path match the behavior of the packages users receive
from npm.

Highlights

  • Web resources by default in @aiwg/cli — install the lightweight package
    and run aiwg discover or aiwg show without project configuration or
    resource flags. Both the binary and exported CLI API select the signed
    stable channel.
  • Legacy local behavior preserved — the full aiwg package still defaults
    to its bundled local corpus, so existing installations can opt into web mode
    per call without changing project deployments.
  • Deployable Cockpit tarball@aiwg/cockpit now includes its compiled
    production web UI and license, launches through npm's global binary symlink,
    and remains available when the optional executor is not installed.
  • Package-level regression coverage — clean-install tests verify the real
    package entry points, default configuration, resource resolution, served
    Cockpit UI, licenses, and allowlists.

Package matrix

All three packages publish in CalVer lockstep:

aiwg@2026.7.18
@aiwg/cockpit@2026.7.18
@aiwg/cli@2026.7.18

Use the full local-corpus distribution:

npm install --global aiwg@latest
aiwg discover "architecture evolution"

Use the lightweight signed-web distribution:

npm install --global @aiwg/cli@latest
aiwg discover "architecture evolution"
aiwg show skill architecture-evolution

Operators can pin resources for one call with --aiwg-version <version> or
override source selection with --resource-source local|web|auto.

Upgrade

npm install --global aiwg@latest
# or
npm install --global @aiwg/cli@latest

No project migration is required. Existing local configurations and explicit
web-mode invocations continue to work.