v2026.8.8
AIWG 2026.8.8 - Managed project capability routing
Release date: 2026-08-12
Channel: stable
AIWG 2026.8.8 gives projects a compact, automatically maintained way to expose
their own extensions and addons to agents. It also makes context regeneration
choose and explain the appropriate workflow from repository state, strengthens
the CLI performance gate, and improves artifact-root and documentation-release
reliability.
What changed
- Project-local extensions, addons, frameworks, plugins, and providers can now
synthesize a project-only kernel quickref from discovered bundle manifests.
This keeps custom capabilities visible without adding them to AIWG's base
quickrefs or loading every project artifact into context. - Operators can curate managed quickrefs with
.aiwg/quickref.config.json,
including exclusions and overrides. Existing.aiwg/quickref.json
definitions continue to work as the legacy compatibility format. aiwg regeneratenow selects workspace refresh or transactional project
adoption when no branch flag is supplied. It reports whether the choice was
explicit or inferred and lists the evidence used to make it.- Artifact relocation preserves the repository-local control plane while
discovery and synchronization follow the attached corpus. - CI now enforces a reproducible CLI cold-start performance gate with documented
local diagnostics. - Scheduled documentation publication checks for releasable changes every six
hours.
Verification
The release candidate must pass version and marketplace lockstep validation,
plugin metadata and layout checks, TypeScript, the production CLI build, the
full automated test suite, metadata and Fortemi-index validation, stable UAT,
hosted CI, signed-tag verification, and post-publication checks for npm packages,
installer checksums, release assets, SBOMs, and provenance.
Package matrix
aiwg@2026.8.8
@aiwg/cli@2026.8.8
@aiwg/cockpit@2026.8.8
Upgrade
npm install --global aiwg@2026.8.8For the lightweight signed-web distribution:
npm install --global @aiwg/cli@2026.8.8After upgrading, run aiwg use all --provider <provider> and
aiwg regenerate --provider <provider> in each project that should receive the
updated kernel and context routing.
Rollback
Roll all three npm packages back together to 2026.8.7, then redeploy the
project's provider assets and regenerate its context files.