Codex History ViewerBrowse, search, organize, and resume past Codex CLI / Claude Code sessions through the official VS Code extensions. Latest release: 2.6.0 (2026-06-12).
Why Use This Extension?Codex and Claude Code sessions can become hard to revisit once they are no longer active in the editor. Codex History Viewer keeps those local session files useful by turning them into a searchable, chat-like history browser inside VS Code. Use it to find past prompts, reuse useful answers, inspect file changes, organize sessions with tags and notes, resume same-source sessions, and prepare handoff context for other AI tools. Highlights
Quick Start
History and Pinned OrganizationHistory and Pinned separate project organization into display and scope controls. Display can switch between List and Project views, while scope can switch between All and Current Project Group. Project matching is case-insensitive across platforms. Project views preserve the existing layout choice: session-list history becomes Project folders can have extension-local aliases from the History or Pinned project context menu. Aliases are stored in VS Code extension state without changing Codex or Claude Code history files. When set, aliases appear in project headings, session descriptions, tooltips, filter summaries, Status, and Search scope/session display while the original path remains available in detailed metadata. Project associations can link another project's history into the current project display or group related projects together without moving the original history files. Associations are available from project context menus and are reflected in History, Pinned, Search, File AI Change History, and handoff content. Pinned has its own project scope, source, archive visibility, date, tag filters, and saved sort preference. It does not follow History/Search filter state, so saved sessions can stay focused on a different project or source while you browse and search elsewhere. History can sort by started date, last activity date, or name. Pinned can sort by pinned time, started date, last activity date, or name. Chat ViewerThe chat viewer renders local session files as readable conversation timelines. It supports Markdown, syntax-highlighted fenced code blocks, KaTeX-compatible math, assistant usage metadata, environment snapshots, tool execution metadata, and grouped file-change cards from patch activity. Large histories can use the Chat tabs preserve useful state across reload and auto-refresh, including scroll position, selected message, expanded cards/diffs, detail visibility, diff wrapping, and in-page search state. The experimental opt-in Restore Webview Tabs After Reload setting can also restore chat and file-change history panels after Developer: Reload Window or VS Code restart. It is disabled by default because VS Code can defer Webview restoration and may occasionally create duplicate tabs when the same history is opened again. Chat history can keep the current user prompt visible at the top while you scroll. Codex memory citation information is rendered as a collapsible section instead of being left as raw metadata in the message body. Attachments and ReferencesThe chat viewer keeps attachments and file references out of the message body and renders them as cards instead.
SearchSearch is local, cancellable, and backed by an incremental search index. It can search conversation text, configured tool metadata, titles, tags, notes, and attachment metadata. Supported query forms include normal substring search, Search follows the current History target, including date, project scope, project filter, source, archive visibility, and tags. It does not follow Pinned filters, and it does not create Search results from filters alone. The global search input combines manual search and search history. Search history is shared with in-page search in the chat viewer and File AI Change History, stores only query text, and can be selected to run or removed individually with the trash button. Saved searches also store and reuse only query text; role filters and case sensitivity are taken from the current settings when the saved search is run, and saved searches can be removed individually from the run picker. Opening a Search result can pass the same query into the chat viewer's in-page search. In-page search in the chat viewer and File AI Change History supports the same query forms, including exact matching and regular expressions, and can show search-history suggestions below the search input. Project aliases are shown in Search scope and result display, but they are not added to the search index or treated as searchable hit text. The search index can be tuned with
Attachment indexing includes labels, paths, MIME types, file kinds, and bounded text from Claude text documents. PDF / Office / binary / base64 document contents and Codex referenced-file contents are not indexed. Codex Archived SessionsCodex History Viewer can optionally read Codex Archive and restore operations prefer the official Codex provider. Moving archived sessions back to normal Codex history can fall back to a filesystem move when the official provider is unavailable. Pins, annotations, bookmarks, and saved chat positions are relocated when the session path changes. Handoff to Other AIHandoff actions appear under Handoff to Other AI for visible Codex / Claude sessions when Handoff files are stored in this extension's VS Code global storage and include a tail-prioritized transcript excerpt, the latest user request, the source session path, recoverable file changes, and attachment summaries. Tool calls, tool outputs, and binary attachment payloads are intentionally omitted. When project associations are configured, handoff generation follows the associated project display and includes path mapping context for the receiving AI. File AI Change HistoryFile AI Change History starts from a workspace file and shows the Codex / Claude changes that touched that file over time.
Use it when you want to answer questions such as:
The Explorer file context menu entry is opt-in. Enable File Change History > Explorer Context Menu: Enabled, then right-click a file in VS Code Explorer and run Show File AI Change History. The view is scoped to the current workspace and selected file. It supports Codex / Claude source toggles, in-page search with shared query history and richer query syntax, incremental Load more, previous/next navigation, and Open in History links back to the matching diff card in the original session. File AI Change History follows project associations when resolving related history, so associated project displays and path mappings are reflected when possible. ConfigurationMost settings are available from VS Code Settings under Codex History Viewer. Common settings include:
Suggested SettingsThe defaults are designed for regular use. These settings are useful starting points when you want a lighter UI, richer search, or more active refresh behavior:
If history or search results look stale, run Control > Rebuild Cache. It recreates both the history cache and search index after confirmation. CommandsMost actions are available from view title buttons and tree context menus. For the full command list with per-command descriptions, see: OpenAI Codex Integration Notes
What's New in 2.6.0
ChangelogSee CHANGELOG. SecuritySee SECURITY. Use the latest release whenever possible; do not install or redistribute v1.2.1 or earlier VSIX files. PrivacyThis extension reads local session files and renders them inside VS Code. It does not implement any network communication and does not send session content anywhere. If you use Copy Quick Prompt or Copy Handoff Prompt to Clipboard, this extension copies session context to your clipboard. Data is only sent externally if you paste it into another tool or extension. When you open a session as a Markdown transcript, the generated transcript includes local paths such as the session file path and CWD. Review before sharing. DisclaimerCodex History Viewer is an independent project and is not affiliated with, endorsed by, or officially associated with OpenAI, Anthropic, Codex, or Claude. This extension works with locally stored session and history files created by official tools and extensions. Their file formats and internal behaviors may change without notice, which may affect compatibility. Archive, restore, delete, import, and other file operations are designed to be conservative, but they may move or modify local files and extension-managed metadata. The author and contributors cannot guarantee recovery of lost or corrupted data. Please keep backups of important session data. |

