Unlocking Codex’s Full Potential: Expert Tips from the Official Team

01 Persistent Threads

Persistent threads run for long periods and retain work context across multiple sessions. Fixed threads are a convenient way to store reusable workflows such as staff‑assistant threads, release threads, document‑review threads, and external‑monitoring threads. These threads act as continuous workspaces rather than temporary chats, allowing Codex to recall prior decisions, preferences, and context without rebuilding from scratch.

Shortcut keys Command‑1 to Command‑9 jump directly to saved threads.

02 Voice Input

Voice input captures raw, unrefined ideas, which is valuable for users who think verbally but type awkwardly. It enables quick articulation of vague initial requirements, meeting transcriptions, and brainstorming sessions, preserving uncertainty, tone, and unfinished thoughts for later refinement.

03 Task Correction and Queuing

Correction interrupts the current step with a new instruction, adjusting direction before completion. Queuing adds subsequent tasks after the current step finishes, without interrupting it. Both keep the user involved throughout execution.

Example correction: "Make this smaller" or "Adjust the spacing between these two elements".

Example queuing: "After the work is done, send the preview link to Slack for review."

04 Tools and Scope

Codex can extend its capabilities outward through tools: $browser: Built‑in side‑panel browser for viewing and annotating web pages. @chrome: Uses the logged‑in Chrome environment for workflows that depend on the browser. @computer: Executes tasks that require a desktop GUI.

MCP services and connectors bring Slack, Gmail, calendar, and other messaging or inbox tasks into the workflow. Verified workflows can be packaged as reusable skills.

05 Work Anywhere

The mobile Codex app lets users start tasks on a configured Mac (with files, permissions, and environment) and continue from their phone, enabling fragmented work such as reviewing long‑running tasks, approving next steps, or adjusting thread direction while away from the desk.

06 Automation

Automation lets Codex execute tasks on schedule:

Timed automation for recurring tasks like daily reports or repository checks.

Thread automation that wakes a specific thread at intervals, preserving context for periodic work.

Example: a staff thread runs every 30 minutes to check Slack and Gmail for unread messages, prioritize them, and draft replies without sending them automatically.

07 Targeted Tasks

Targeted tasks are long‑running Codex jobs with clear completion criteria. Ineffective targets lack measurable success; effective ones include concrete goals such as migrating an internal tool from Python to Rust, where the task finishes only when unit tests pass.

Verification methods include test suites, benchmarks, bug reproduction, validation matrices, and end‑to‑end workflows that must continuously succeed.

08 Side Panel

The side panel displays generated work products—code, documents, presentations, PDFs, webpages, tables—next to the conversation, allowing in‑place review and annotation without context switching.

Typical operations:

Viewing work products.

Annotating needed changes.

Interacting with web interfaces.

Reviewing and approving changes.

Images illustrate the side‑panel UI and its annotation capabilities.

09 Shared Memory

Shared memory stores persistent context outside a single thread, enabling later threads to continue from a well‑defined, reviewable state. A practical pattern links a persistent thread to an Obsidian vault (or any synced folder) containing structured notes such as TODOs, people, projects, agents, and general notes.

vault/
├── TODO.md
├── people/
├── projects/
├── agent/
└── notes/

An AGENTS.md file can define how Codex should update the workspace after learning about personnel, projects, decisions, and tasks.

10 Extending Beyond Code

While Codex still starts from code, it now orchestrates the entire workflow—including MCP services, browser interfaces, desktop control, thread automation, and reviewable outputs—changing the control model: correction interrupts current work, queuing schedules follow‑up tasks, automation keeps threads alive when users are away, and target tasks give Codex a clear end goal. Consequently, Codex can manage end‑to‑end workflows that go beyond the code repository.