Session Actions

When you select a session — either from the search TUI or via aichat menu — an action menu appears with operations you can perform on that session.

Available actions

Non-launch actions

These actions operate on the session file without starting a new Claude Code / Codex session:

Action	Description
Show session file path	Print the full path to the JSONL session file
Copy session file	Copy the session file to a destination path
Export to text file	Export the session as a readable `.txt` file
Query this session	Ask a question about the session content (uses an AI agent to read and summarize)

Launch actions

These actions start or continue a Claude Code or Codex session:

Action	Description
Resume/trim session	Opens the resume submenu

Resume submenu

When you select Resume/trim session, a submenu appears with these options:

Option	Description
Resume as-is	Open the session with `claude --resume`
Clone session and resume clone	Copy the file first, then resume the copy
Trim + resume	Truncate large tool outputs and optionally assistant messages, then resume
Smart trim + resume	Use an AI agent to decide what to trim, then resume
Rollover	Hand off work to a fresh session with lineage

See the Resume page for details on each strategy.

Select any session in the search TUI (aichat search) and the action menu appears automatically.

Pass a session ID directly to aichat menu:

aichat menu abc123-def456

Or use the shortcut (any unknown argument is treated as a session ID):

aichat abc123-def456

Run aichat with no arguments to show the action menu for the latest session(s) in the current project:

aichat

Query action

The Query this session action lets you ask arbitrary questions about a session. It uses a headless AI agent to read the session file and return a focused answer. The default query is:

Summarize what was accomplished in this session

You can replace this with any question, such as:

“What files were modified?”
“What was the final decision on the auth approach?”
“List all TODO items mentioned”

Export action

The Export to text file action converts the JSONL session into a human-readable .txt file. By default, exports go to:

<project>/exported-sessions/<date>-session-<id>.txt

You can specify a custom destination path when prompted.

Move action

aichat move <session> <new-project> re-homes a session on a different project directory. Both arguments are required, and the session may be named any way the shared lookup accepts:

aichat move session-finder ~/Git/other-repo
aichat move 2945d228 ~/Git/other-repo

It rewrites the working directory recorded on every line of the transcript, then:

Claude: relocates the transcript into the new project’s directory under the Claude home. The destination filename and the resume command it prints both come from the session id recorded inside the transcript, so a file you renamed yourself still lands as <session-id>.jsonl.
Codex: rewrites the rollout in place. Codex organizes sessions by date rather than by project, so the file itself does not move.

A name you set with /rename survives either way: a Claude name is recorded inside the transcript, and a Codex name lives in the home-level session_index.jsonl, keyed by a session id that move never changes. Afterwards move offers to switch to the new directory and resume the session.

Both rewrites are atomic: the new content is written to a temporary file beside the destination and then swapped into place, so a move interrupted partway cannot leave you with a truncated transcript.