mirror of
https://github.com/openai/codex.git
synced 2026-11-18 22:20:48 +00:00
## Why Legacy rollout migration rewrites rolled-back history and can disrupt the realtime stream. Enroll local threads once they use paginated history so the stream stays intact. ## What changed - Add the off-by-default `features.realtime_frames_local` flag for paginated local threads with a state database. Accept runtime updates through the app server and keep threads enrolled once they have a persisted canonical session start. - Add thread-store APIs to recover a realtime session and look up the latest session ID from durable history. Route frame completion through a store seal so completion acknowledges durable writes. - Add a local seal for accepted model input that writes source frames before the input and lets callers retry an uncertain flush without appending the input twice. ## Testing Cover enrollment for legacy and paginated threads, continued enrollment after disabling the flag, and retrying a local input seal after a failed directory sync. GitOrigin-RevId: 2012feeca3857da90f9b026f077b31a26d15191b
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.