Session History

Nikolai MarchenkoThread ManagementNew
Get it for macOS

See every Claude Code, Codex and Qwen Code session you ran outside BB, under the titles the agents gave them. The new-thread screen lists the sessions from the selected project's folders, and a Sessions page lists all of them with agent filters and search. Open any session to read its transcript, show its tool calls, or copy the command that resumes it in a terminal. Session files are read on the machine that runs BB and are never uploaded or changed.

Overview

View source

What you get

  • Past sessions on the new-thread screen. It lists the sessions that ran in the selected project's folders. All folders shows the rest.
  • Sessions in the sidebar. It lists every session, newest first, with a filter per agent and a search over title, first prompt and folder.
  • A read-only transcript for each session: your prompts, the agent's replies and, on request, its tool calls. One button copies the command that resumes the session in a terminal (claude --resume, codex resume or qwen --resume).
  • bb session-history list and bb session-history show for the terminal, plus a skill that lets agents in BB look up an earlier session.

Where the titles come from

Each session keeps the name its agent shows. Claude Code uses your custom title or its own generated title. Codex uses the thread name from its local state database, the same one its VS Code extension shows, and hides subagent threads. Qwen Code stores no title, so its first prompt stands in.

Requirements

Sessions are read from the machine that runs the BB server: ~/.claude/projects, ~/.codex (or CODEX_HOME) and ~/.qwen/projects. Files are only read; nothing is uploaded or changed. The interface follows the browser language, Russian or English.

More in Thread Management 38

Find, identify, organize, or archive threads.

View all