TokenPak

Release

TokenPak v1.13.0

v1.13.0 · Jul 21, 2026

Minor release: deterministic memory configuration, Receipt v1 inspection, bounded managed-request admission, safer launch defaults, and a broad proxy/release-tooling reliability pass.

Added

  • Deterministic memory optimization. tokenpak config optimize can plan, apply, inspect, and roll back a process-local MemoryGuard configuration derived from physical and cgroup memory limits. Managed state uses canonical hashes, atomic writes, drift detection, and an exact preimage receipt; runtime environment overrides remain authoritative.
  • Receipt v1 proof objects and debug inspection. Request accounting can emit structured proof receipts, and tokenpak debug receipt can inspect a recorded request without changing request behavior.
  • Managed-request admission. Classified background traffic can use a bounded concurrency gate with deterministic queue-full and wait-timeout responses; unclassified traffic retains its existing pass-through behavior.
  • Per-client launcher permission defaults. tokenpak permissions launcher can persist inherit, approval-bypass, sandbox-bypass, or full-bypass for TokenPak-launched Codex sessions, plus the supported Claude Code subset. Bypass modes require explicit confirmation, leave client config files untouched, warn on every affected launch, fail closed on invalid state, and retain permissions set fleet as a full-bypass compatibility alias.
  • Cross-platform process and service helpers. CLI maintenance and launcher paths share a platform abstraction for process discovery, signaling, and service lifecycle behavior on Linux, macOS, and Windows.
  • Read-only dashboard layouts. tokenpak dashboard --layout... --json exposes home, dispatch, spend, debug, and multi-instance views without adding a mutating dashboard control plane.
  • Typed unsupported-stateful-surface helper. Callers can build a stable stateful_api_unsupported remediation payload. The helper is additive and dormant: no route handler invokes it, and callers remain responsible for the route-appropriate HTTP status.

Improved

  • Proxy lifecycle and memory return. Idle client retirement, cleanup bounds, listener admission, vault-index memory return, and MemoryGuard ownership are coordinated so cleanup remains bounded and in-flight work is not retired prematurely.
  • Streaming fidelity for short event streams. Short server-sent-event responses are forwarded incrementally while preserving byte-for-byte pass-through behavior.
  • Telemetry database canonicalization. A dry-run-first migration helper identifies legacy database locations, fails closed on incompatible targets, and preserves source data rather than overwriting it.
  • Dispatch and licensing diagnostics. Discovery, dry-run ledger, install truth, doctor, and fail-closed licensing paths have expanded regression coverage and more consistent CLI behavior.

Fixed

  • Optimization savings use token units. Receipt fields and legacy fixtures no longer present token counts as currency-shaped values.
  • Optional dependency declarations match imports. Dashboard-serving extras now include Jinja2 and python-multipart, and optional compression/import guards report missing capabilities truthfully.
  • SDK dependency floors are coherent. The TypeScript SDK keeps compatible Jest/ts-jest tooling and declares the tested axios runtime floor without an unrelated major toolchain upgrade.

CI

  • GitHub Actions use current checkout, setup-python, upload-artifact, and cross-workflow artifact-download releases with matching gate-inventory hashes.
  • The public-API snapshot now captures the service-layer optimization, provider-usage, and routing symbols exposed by the regularized tokenpak.services package. This is additive; no public symbol is removed.
  • The development lock now includes the import-contract checker and its graph engine, keeping local architecture validation reproducible.
  • The release audit now composes the complete test, quick smoke, architecture, clean-wheel demo, passthrough-performance, byte-fidelity, documentation, and public-safety gates with fail-closed evidence handling.

Docs

  • Add the MemoryGuard optimizer guide and Receipt v1 reference.
  • Refresh generated CLI reference and current-release limitation metadata.

Upgrade

pip install --upgrade tokenpak==1.13.0

No additional steps are required.

Rollback

If tokenpak config optimize --apply was used, restore its recorded preimage before downgrading:

tokenpak config optimize --rollback
pip install tokenpak==1.12.0

Otherwise, no TokenPak-home cleanup is required; run only the pip install command above.