Skip to main content
A session is the record of one line of work. It keeps the question or claim, Navi’s answer, each verdict or check result, and the evidence you return.

​
Continue the same work

When Navi asks for more evidence, its next command includes the session ID:
Keep -t <session> on the next run. Without it, Navi starts a new session and does not bring the earlier result into the review. The same continuation flag works for a repository question or a flow:

​
Read the record

List your sessions, inspect every turn, or read the shorter story:
Use session show when you need the complete timeline and current state. Use story when you want the sequence of decisions and checks without the full turn detail. These commands do not call a model. Founder verdicts (GO, REFINE, REJECT) and completion-check results are part of the session record. There is no separate verdict object for you to manage.

​
Try an alternative without changing the original

Fork a session when you want to test another approach while preserving the source:
Navi creates a new session with the source history and records the relationship between them.

​
Hide finished sessions from the default list

Archiving changes list visibility; it does not delete history:

​
Record an explicit override

If you choose to proceed against a demanding result, give the reason:
Navi preserves the original result and records the override beside it. It does not rewrite the result as approved. For session filters, JSON fields, result values, and process exits, use the Automation reference.