Sessions

A session is one ongoing conversation, tied to the directory you start it in.

Three ways in

axom	The full-screen terminal session.
axom --plain	A plain scrollback prompt, for terminals that can't host a full screen.
axom ui	The browser UI: chat, projects, jobs, memory, personality, and settings.

All three talk to the same runtime, so a session started in one can be continued in another. In the browser, your chats and jobs sit in the sidebar: open one to pick it up, or delete it.

Several at once

With engine_sessions above 1 (see Settings), several sessions run at the same time on one loaded model: a chat, a research turn, and a background job, decoded together. Each keeps its own stream, so what runs beside a session never changes its answer.

Watching Axom work

Axom shows its work as it goes: each search, page read, file edit, and command appears as it happens, and the answer streams in as it's written. /trace (or Ctrl-T) toggles the full trace: every thought and observation.

Steering mid-turn

Anything you type while Axom is working is an interrupt. Axom reads it at its next step and changes course, even in the middle of writing an answer. Ctrl-C or /stop stops the turn outright.

Rating answers

/good and /bad rate the last reply; add a note to say why. Ratings are stored with the turn on your machine. See Files on disk.

Starting over

/new starts a fresh session for this directory. The old one isn't gone; Axom can still recall from it.

See every command in Slash commands.