Overview
Codex Session Recall is a local-first tool for recovering evidence from earlier Codex conversations. It reads the Codex catalog in read-only mode, parses conversation messages from rollout JSONL files, builds a disposable SQLite FTS5 index, and returns a bounded bundle of matching excerpts with session IDs and source line numbers. The project describes itself as a search-before-context layer for long-running AI work.
The tool separates processing old sessions from using recalled evidence later. It builds a safe, disposable index and lets an agent query it only when prior work may affect the answer. Raw sessions remain the source of truth; nothing is uploaded, and the tool does not write to the Codex state database or the original transcripts.
Multi-term recall is strict first, preferring a single message containing all query terms. If that produces no match, it may fall back to coverage across multiple messages from the same session, while keeping evidence lines separate and marking the result as term_coverage_fallback. Results from different sessions are never merged. An optional assess command exposes a friction trigger for integrations and returns a structured should_recall decision.
Status is 0.2.0-alpha research preview. It requires Python 3.10+ with SQLite FTS5 and a local Codex installation. The runtime has no third-party dependency. Limitations include Codex adapter only, lexical recall rather than semantic/vector search, and no automatic model summarization or memory-palace writeback.
Pricing
Free
Detailed plans have not been confirmed in our catalog. Check the official website for current limits and billing terms.
Visit WebsitePrices and limits may change. Confirm the currency, billing period, seat minimum and usage caps on the official website.
Use Cases
- Teams use Codex Session Recall to recover earlier decisions, accepted fixes, debugging lessons, or failed attempts when a current task depends on them.
- Teams use it to search local Codex conversation history without uploading data.
- Teams use it to build or incrementally refresh a local derived index.
- Teams use it to return a bounded context bundle with evidence from canonical JSONL files.
- Teams use it to check a new machine before indexing.
- Teams use it to install an optional Codex skill from a source checkout.
- Teams use it to exclude the current active session from recall.
- Teams use it to override local roots when integrating another host or adapter.
Features
Search local Codex conversation history
Recover evidence of earlier decisions
Build a disposable session index
Refresh the index as sessions grow
Return excerpts with source line numbers
Keep evidence from separate sessions distinct
Check whether prior context warrants recall
Reviews
No reviews yet. Be the first to share your experience!