Agentic Sandbox v2026.7.3

Released: 2026-07-07 Tag: `v2026.7.3` Previous: `v2026.7.2` Compare: `v2026.7.2...v2026.7.3`

What this release is

v2026.7.3 fixes admin-v2 VM lifecycle visibility and cleanup after Cockpit UAT, repairs host and container enrollment routing, and restores host-runtime PTY sessions in the formal session-list API. Stopped admin-provisioned VMs remain manageable, destroy releases libvirt/storage/IP/CID state, and host sessions reported by local supervisors are listed like Docker and VM sessions.

Highlights

Stopped VMs stay in inventory: admin-v2 qemu provisions persist the

libvirt launch/domain name, so stopped `cockpit-*` VMs remain visible after the in-guest agent disconnects.

Destroy cleans VM allocations: admin-v2 destroy can resolve stopped or

disconnected VMs by launch name, undefine the libvirt domain, remove storage, and release IP and VSock CID registry entries.

Host sessions are listed by the API: dispatcher reconciliation now imports

agent-reported live PTY sessions before pruning stale inventory, so `GET /api/v1/agents/{id}/sessions` includes host/local-supervisor sessions.

Host runtime enrollment uses mTLS: local host agents default to the mTLS

gRPC listener when mTLS is configured, while `AGENTIC_HOST_GRPC_SERVER` remains an explicit override.

Container bootstrap can bind where Docker can reach it:

`AGENTIC_HTTP_LISTEN_IP` can widen the HTTP bootstrap/dashboard listener for `host.docker.internal` enrollment paths without changing the loopback default.

Install / upgrade

curl -fsSL https://github.com/jmagly/agentic-sandbox/releases/download/v2026.7.3/agentic-sandbox-install.sh \
  | bash -s -- --version v2026.7.3

Direct package installs:

sudo apt-get install ./agentic-sandbox_2026.7.3-1_amd64.deb
sudo dnf install ./agentic-sandbox-2026.7.3-1.x86_64.rpm

Upgrade matrix

Audience	Action
Operators	Upgrade management before exercising admin-v2 VM stop/destroy flows. Existing stale IP/CID registry rows from older destroys may need one-time manual cleanup.
Dashboard/Cockpit users	Refresh after the management upgrade; stopped VMs should remain visible and host session lists should no longer need UI-side synthesis.
API clients	Continue using `/api/v2/admin/instances` and `/api/v1/agents/{id}/sessions`; no request-shape changes are required.
Runtime maintainers	Re-test host/container bootstrap endpoints on mTLS and HTTP bind deployments.

Verification

The release fixes were validated locally with:

cargo test -p agentic-management http::admin_v2::tests::
cargo test -p agentic-management http::sessions::tests::
cargo test -p agentic-management dispatch::dispatcher::tests::imported_reported_sessions_are_visible_in_active_sessions
cargo test -p agentic-sandbox-executor instance::tests::

After publication, verify the release assets:

scripts/verify-release-assets.sh v2026.7.3 --skip-ghcr

Runtime checks:

curl -sS http://127.0.0.1:8122/api/v2/admin/instances
curl -sS http://127.0.0.1:8122/api/v1/agents/<host-agent-id>/sessions

Stop an admin-v2 qemu VM and confirm it remains listed. Destroy it and confirm the libvirt domain, storage directory, `.ip-registry` entry, and `.vsock-cid-registry` entry are removed. Create or discover a host runtime PTY session and confirm it appears in the agent-scoped session list.

Notes

This release changes cleanup and inventory behavior only; no API request-shape

migration is required.

Destroy cleanup releases allocations for newly destroyed VMs. Operators with

stale `.ip-registry` or `.vsock-cid-registry` entries left by previous builds should reconcile them during upgrade maintenance.

Container bootstrap deployments that need Docker host-gateway reachability

should set `AGENTIC_HTTP_LISTEN_IP` to an explicitly reachable bind address.