Codex runtime mapping

Use native task history and verified rollout paths, not ~/.cursor/projects. Preserve the scope window, distinct own-history/shared-record sweep, citations, live-state readback and capsule format. Apply the standing model router to optional read-only delegation.

Recall

Before you start or resume work, you rebuild the user's recent working context and hand back a tight capsule of where things stand now and what to do next.

Keep it tight and on-topic. Read only what the in-scope threads need, then stop.

Your context lives in two records. Your own chat history holds what you did and decided. The shared record holds everything that happened around the same code under other names: the symptoms users keep reporting, the fixes that shipped and got reverted, the errors still firing in prod. That second record is what cursor-why searches, across source control, the issue tracker, chat and issue channels, long-form docs, and error tracking. A feature with a long bug tail keeps most of its story there, so don't reconstruct it from your transcripts alone.

In Codex, discover accessible prior tasks with the native thread list/read tools. Local rollout JSONL may provide full tool history when a verified rollout path is available; its filesystem layout varies by host. Do not infer a Cursor transcript path or read a different project without the user’s scope.