Sessions

A session is one conversation with the agent. Sessions are saved per project, under .jan/agent/threads, so a project's history stays with the project.

Because they're per project, resuming from a different directory finds nothing - that's expected, not a bug.

Resuming

From inside the console:

For a headless run the value form needs an equals sign, because run takes a positional task that a space-separated id would swallow:

Starting fresh

Both drop the active goal along with the conversation.

Rewinding

Press Esc twice while idle to pick an earlier message and roll back to it.

In a git repository the agent snapshots your workspace as it works, so a rewind can restore the files too - not just the conversation. Outside a repository you get conversation-only rewind, which is the same behaviour minus the file restore.

This is the escape hatch when the agent goes down a wrong path: rather than arguing it back, rewind to before the turn that started it and rephrase.

Queueing

Type while the agent is working and your message is queued instead of dropped. It's sent as soon as the current turn ends, and the footer shows how many are waiting:

Esc cancels the turn that's running, which is separate from the queue.

Inspecting from the shell

Threads are readable without opening the console. Output is JSON, so it pipes into jq:

What's stored

Under <project>/.jan/agent/:

Add threads/ to .gitignore - those are personal transcripts. agent.toml, AGENT.md, and skills/ are worth committing.