Skip to main content
This quickstart shows the v0.1 harness loop: inspect, plan, edit, validate, and resume.
1

Open a repository

Run Voss from the repository you want to inspect.
voss login is only needed when no Claude, Codex, or API key credentials are found.
2

Ask for a read-only summary

voss do defaults to plan mode, so mutating tools are denied unless you choose a different mode.
3

Open a scoped edit session

Name the file or directory Voss may edit.
Voss can write the target and existing nearby test mirrors. Other writes require explicit scope expansion.
4

Validate work

Use the repo’s normal checks. For Voss language files, use voss check.
5

Resume later

Sessions are persisted per project. List them, then resume by id or name.
In the Go terminal client, /resume opens a picker over saved sessions.
Run bare voss for the full-screen Go terminal client. It uses the same harness loop, sessions, and permission prompts as voss do and voss chat.
You have completed the core harness loop when Voss can inspect the repo, make a scoped change, run validation, and resume the session.