AIWG 2026.8.1 - Persistent memory and governed fleet operations

AIWG 2026.8.1 - Persistent memory and governed fleet operations

Released: 2026-08-02 Channel: stable

AIWG 2026.8.1 introduces a complete persistent-memory cycle, expands governed sandbox work from one target to durable fleets, and adds authenticated access to paid resource channels. It also makes Codex deployment safer and more predictable across project workspaces.

Compound memory

The new `compound-memory` addon combines line-memory and llm-wiki without forking either storage model:

aiwg use compound-memory --provider codex
aiwg compound-memory ingest notes.md
aiwg compound-memory context "current project decisions"
aiwg compound-memory review

Raw inputs remain immutable. Knowledge and short facts require reviewed promotion, context packs enforce hard budgets and carry source citations, and generated outputs remain derived evidence until accepted. Canonical project context uses exact-preview confirmation, idempotent receipts, lifecycle metadata, conflict visibility, and provider-neutral storage.

Review and maintenance expose stale facts, contradictions, orphaned wiki pages, unlinked outputs, and due canonical context before mutation. A deterministic three-session fixture verifies continuity, retrieval quality, latency, provenance, restart safety, and portable activation without rewriting existing line-memory or wiki data.

Governed sandbox fleets

The fleet workload contract and mission conductor extend Cockpit's sandbox controls to multiple targets. Stable parent and child identities, admission checks, retries, restart reconciliation, and durable cross-product evidence make fleet progress observable without hiding partial failures.

The conformance suite exercises a three-target recovery path and fails closed on malformed or unavailable inventory. Cockpit now projects parent/child mission state while preserving the daemon health contract.

`aiwg auth login`, `status`, and `logout` manage paid-resource account access using protected platform storage with a permission-restricted file fallback. Authorization is scoped to the configured HTTPS API origin and access material never participates in URLs, cache keys, lockfiles, or routine diagnostics.

Signed manifests, digest checks, bounded downloads, and offline cache behavior remain unchanged for authenticated channels.

Codex and reliability improvements

  • `aiwg use ... --provider codex` preserves native kernel skills across addon

sweeps and writes Codex UI metadata under `agents/openai.yaml`.

  • Setup guidance uses `$aiwg-regenerate` and tells operators to reopen Codex at

the target project root.

  • Generated `.codex/` and `.agents/` trees are added to `.gitignore`; existing

tracked files stay tracked and dry-run remains non-mutating.

  • Development launchers load notifier and logging modules from the active

checkout, and stale cache entries from another installed version are ignored.

  • The lightweight CLI can package external standalone plugins and install valid

wrappers either into the current project or globally for the user. Each mode refreshes its matching artifact and Fortemi indices.

Package matrix

All three packages publish in CalVer lockstep:

[email protected]
@aiwg/[email protected]
@aiwg/[email protected]

Upgrade

Follow the installation guide and select `2026.8.1` for the full local-corpus package or lightweight signed-web CLI. Cockpit remains installable and refreshable through the base CLI.

Rollback

Roll back all three packages together to `2026.8.0`. Existing memory stores and fleet evidence remain on disk; disabling the new addon or conductor does not delete retained data.