Capture
Project-local lifecycle hooks record supported coding-agent sessions as they work.
The agent session belongs with the change.
Agent Transcripts preserve the work behind agent-authored code. Vex captures supported harness sessions, screens them before upload, and binds the authorized record to the exact Change so reviewers can inspect provenance and start a bounded handoff.
Commit-bound provenance / authorized handoff
Review the code and the path that produced it.
A Change can carry sessions from multiple people, supported harnesses, and models. Vex keeps the patchset binding, capture status, redaction metadata, token totals, and subagent count with each attached transcript.
The Change page lists provenance; transcript content stays behind the server-authorized handoff instead of being embedded into the review payload.
Agent Transcripts · explanatory model
Capture and attachment model
1Agent sessionHarness, model, title, token totals, and observed subagents
2Privacy screenKnown sensitive patterns are screened and redacted before upload
3Exact attachmentThe authorized transcript binds to the Change and commit it produced
Change
History
Sessions
Screen
Vex detects known credential and sensitive-field patterns before upload.
Attach
When the working copy leaves a Change, active sessions bind to its exact commit.
Review
Changes, History, and Sessions expose scoped provenance and authorized handoff actions.
One record / four useful surfaces
Change review
See who and which harness produced each attached session.
Repository History
See commit-bound agent context beside Change, CI, and deployment state.
Organization Sessions
Filter captured sessions across repositories, people, harnesses, and status.
Ask why or continue
Open an authorized sanitized handoff for explanation or a fresh-agent continuation.
Install capture with agent setup
$ vex setup --with-agent-checkpointsAudit the local delivery path
$ vex session doctorCapture is best-effort by design: a hook or network failure never blocks a source operation. Screening detects known credential and sensitive-field patterns and fails closed; it is not a guarantee that arbitrary secrets can be recognized. The local outbox and doctor command keep incomplete delivery visible and retryable.
Transcript access remains authorization-scoped. Retention, deletion, legal hold, and organization policy are deployment decisions to confirm during evaluation. Native lossless resume is not universal; Continue starts a bounded sanitized handoff when exact provider resume is unavailable.
Start with proof