> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tryvoss.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Sessions

> List and resume Voss harness sessions.

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](/orchestration/session-tree) — one node per agent — plus per-card review sidecars, which form the run's [audit trail](/orchestration/audit).

## List sessions

```bash theme={"theme":"github-dark"}
voss sessions
```

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

## Resume a session

```bash theme={"theme":"github-dark"}
voss resume <session-id>
```

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.

<Warning>
  Do not paste secrets into natural-language prompts. Voss avoids storing provider credentials, but user-provided text can still become part of a transcript.
</Warning>