Skip to main content
Voss records harness sessions so work can be resumed and audited. This page covers single-agent harness sessions. A team run additionally persists a session tree — one node per agent — plus per-card review sidecars, which form the run’s audit trail.

​
List sessions

The session list shows saved work with enough context to choose what to resume.

​
Resume a session

Resume restores prior conversation context and model/session metadata. Use voss sessions first when you need the id.

​
What sessions are for

  • Continuing multi-step repo work
  • Preserving task goals and assumptions
  • Auditing tool use and decisions
  • Avoiding repeated context reconstruction

​
Redaction rule

Provider credentials and API keys must not be written into session payloads.
Do not paste secrets into natural-language prompts. Voss avoids storing provider credentials, but user-provided text can still become part of a transcript.