Review changes. Keep evidence current.

Check permission changes before upgrades, detect launcher drift, and measure your own setup experience without collecting tool conversations.

Before an upgrade

warden policy-diff --before old.yaml --after candidate.yaml
warden inventory --client cursor --scope project
warden unwrap --client cursor --server filesystem --yes

New grants, changed commands and expanded limits require review. Keep the original prepared artifact and configuration backup for rollback.

Measure your pilot locally

warden report record --file ./pilot.jsonl --client cursor --event setup-completed --seconds 90
warden report record --file ./pilot.jsonl --client cursor --event first-protected-task
warden report summary --file ./pilot.jsonl

Explicit events include failures, rollback, repeat use and badge activations. Record only test data outcomes. No telemetry runs in the background.

Your local pilot report

Import events you explicitly recorded with the CLI. This page totals them locally. Event counts do not represent unique users or verified activations.

Nothing is uploaded, saved, or collected automatically.

Release, contribution and incident guide →