v2026.7.25

AIWG 2026.7.25 - Target-native managed session directories

Released: 2026-07-31
Channel: stable

AIWG 2026.7.25 makes Cockpit-launched provider sessions start in the working
directory selected by the managed target. Host sessions use the host runtime's
resolved workspace, while container and VM sessions use the executor-reported
directory with /home/agent as the compatibility fallback.

What changed

• Cockpit Bridge now forwards normalized launch_context.cwd to provider
  processes for host, container, Docker, and VM targets.
• Older container and VM inventory without cwd metadata falls back to
  /home/agent instead of a root-owned directory.
• The protected daily gate asserts the cwd invariant on the candidate phase
  while retaining immutable previous-stable and rollback validation.
• The bounded Codex live probe supports gate-owned workspaces that are not Git
  checkouts without relaxing its read-only sandbox.

Cockpit and sandbox compatibility

Agentic Sandbox v2026.7.18 supplies the target-native cwd field and gives its
non-root container image a matching HOME and WORKDIR. Older sandbox
versions remain usable through Cockpit's compatibility fallback, but do not
provide the same executor-bound cwd evidence.

Package matrix

All three packages publish in CalVer lockstep:

aiwg@2026.7.25
@aiwg/cli@2026.7.25
@aiwg/cockpit@2026.7.25

Upgrade

Full local-corpus distribution:

npm install --global aiwg@2026.7.25

Lightweight signed-web distribution:

npm install --global @aiwg/cli@2026.7.25

Install or refresh Cockpit through the base CLI so it remains version-locked to
the installed AIWG release:

aiwg use cockpit
aiwg cockpit

Upgrade Agentic Sandbox to v2026.7.18 to receive executor-bound cwd metadata
and the corrected non-root container home.

Rollback

Roll back all three packages together to 2026.7.24. Cockpit will again use its
older local cwd selection, so verify host and container startup directories
after rollback.