mirror of
https://github.com/openai/codex.git
synced 2026-11-20 22:40:37 +00:00
## Why The fixed retention window can discard assistant messages before elastic Guardian reviews can use them as context for a user's reply. ## What changed Apply the thread's Guardian retention policy when recording assistant messages, including confirmed messages sent through the user messaging tool. Keep full text within the configured record limit and the overall assistant history byte budget. Preserve an incomplete marker when a confirmed delivery exceeds the record limit. Recover the thread's retention settings from saved history and compaction checkpoints. Fixed-budget reviews continue to use the fixed retention window. ## Testing Add coverage for record limits during capture and restore, thread-owned settings recovery, and replay of oversized confirmed deliveries. GitOrigin-RevId: e828f06824ce6712910a9cc5ef42a438d1ddf27e
Thread Store
codex-thread-store is the storage boundary for Codex threads. It defines the
ThreadStore trait plus local and in-memory implementations. Other storage
implementations may live outside this repository.
Responsibilities
ThreadStore::append_itemsis the raw canonical history append API. It does not infer metadata from item contents.ThreadStore::update_thread_metadatais the only thread metadata write API. It accepts a single literal metadata patch shape, regardless of whether the caller is applying a user/API mutation or facts derived above the store from appended history.LiveThreadis the preferred API for active session persistence. It owns a per-thread metadata sync helper, applies the rollout persistence policy, appends canonical history, and then sends metadata patches throughThreadStore::update_thread_metadata.ThreadManagerroutes metadata mutations for loaded and cold threads through one entrypoint. Loaded threads use theirLiveThread; cold threads go directly to the store.LocalThreadStorepersists history throughcodex-rolloutJSONL files and persists queryable metadata through the SQLite state database when available. Local explicit metadata mutations also maintain JSONL/name-index compatibility so reading old or SQLite-less local storage keeps working.RolloutRecorderis the local JSONL writer. It writes already-canonical items forThreadStore::append_items; it no longer decides metadata updates for live thread-store appends.core/sessioncreates or resumesLiveThreadhandles and does not need to know whether persistence is backed by local files or another store.
Direction
New metadata observation semantics should live above ThreadStore. Stores
persist explicit metadata fields, but raw history appends remain history-only.