Sessions And History

Anode saves local run events. That is what powers /resume, /threads, local thread search, and the thread tools.

Session Storage

By default, sessions are stored under:

~/.config/anode/sessions

The config keys are below. This example keeps the most recent 100 sessions per workspace; omit maxSessions or set it to 0 for unlimited retention.

{
  "session": {
    "autoSave": true,
    "maxSessions": 100,
    "storePath": "~/.config/anode/sessions"
  }
}

autoSave defaults to true. maxSessions defaults to 0, which means no configured retention limit.

Sessions are created lazily: opening the TUI or running a slash command will not produce an empty “New thread” row. A session row is written the first time you send a chat message, so accidental launches do not bloat the picker.

TUI Commands

Command	Use
`/sessions`	Browse saved sessions.
`/resume`	Resume a saved session.
`/threads`	Search and read local thread history.
`/new`	Start a fresh session.

Session picker keys

Inside /sessions:

Key	Action
`↑` / `↓` (or `k` / `j`)	Move selection.
`enter`	Resume the highlighted session.
`d`, `delete`, `backspace`	Ask to delete the highlighted session.
`y` or `enter` (during confirm)	Permanently delete it.
`n` or `esc` (during confirm)	Cancel the delete.
`esc`	Close the picker.

Deleting the currently-active session resets the in-memory transcript and clears the active pointer; the next message you send will lazy-create a fresh session. If the picker is emptied by a delete, the modal closes automatically.

Thread Tools

The agent can use:

Tool	Use
`find_thread`	Search local thread history.
`read_thread`	Read a saved thread by ID.

These tools read local Anode history. They do not fetch conversations from a remote service.

Repo Index And Memory

The TUI also exposes:

Command	Use
`/index`	Build or refresh the repository index.
`/repo`	Show the repository map.
`/memory`	Show or manage project memory.
`/context`	Show the current context pack summary.

The repo index cache lives under ~/.cache/anode/indexes. Project memory lives under ~/.config/anode/memory.

Privacy

Session data is local to your machine unless you copy it elsewhere. It may include prompts, model output, tool calls, file paths, command output, and other run event payloads.