Skip to main content
reopt Handbook
reopt Handbook
Advanced Codex Usage

Foundation

Setup and LoginConfigMemories

Safety and Operations

ApprovalsSecurity

Workflow

Slash CommandsPrompts and SkillsExec and AutomationThread LifecycleCloud TasksMulti-Agent Workflows

Extensions and IDE

Codex App and IDEMCP IntegrationModels and ReasoningGovernance and Rollout

Verification

VerificationUpdates
Handbook›Advanced Codex Usage›Codex App and IDE
한국어English

Codex App and IDE

Use Codex across the app, terminal, and IDE without losing context discipline.

Desktop 26.908 (September 11, 2026)

The unified changelog adds Pets Quick Chat and Windows Appshots in the ChatGPT desktop app. Open Quick Chat with Option+Space on macOS or Windows+Alt+P on Windows, using @ for context and $ for skills. On Windows, press both Alt keys to share the frontmost window screenshot and available text. These are desktop features, separate from CLI 0.154.0 commands.

Official changelog

Key takeaways

  • Match the interface to the task: terminal for builds, tests, git, and repository automation; IDE for navigation and targeted edits; Desktop app for long tasks, artifacts, and visual review.
  • Keep the repository as the source of truth and never let interface switching hide unfinished changes.
  • Use /app to move an active CLI thread into Codex Desktop, and codex app <path> to launch Desktop from the shell.
  • After a Desktop handoff, re-check active MCP servers, model and thinking mode, and remote host state.
  • Re-run verification after applying changes from another interface, and summarize the final state in files and commands rather than interface activity.

The best interface depends on the task. Terminal workflows are strong for repository work, while IDE and app workflows help with visual review, artifacts, and focused editing.

Interface Choice

InterfaceBest for
TerminalBuilds, tests, git, repository automation
IDELocal code navigation and targeted edits
Desktop appLong tasks, artifacts, browser, visual review
Browser-enabled flowLogged-in web app inspection when approved

Rules of Use

  • Keep the source of truth in the repository.
  • Do not let interface switching hide unfinished changes.
  • Use /app when the active CLI thread should move into Codex Desktop; use codex app <path> when launching Desktop from the shell.
  • Re-check active MCP servers, model/thinking mode, and remote host state after Desktop handoff.
  • Re-run verification after applying changes from another interface.
  • Use screenshots or browser checks for UI work.
  • Summarize the final state in terms of files and commands, not interface activity.

Related docs

Cmd. /app

Codex Command Master · Hand off the current CLI thread to Codex Desktop.

Cmd. /desktop

Claude Code Command Master · Continue the session in Claude Code Desktop (/app).

Cmd. /ide

Codex Command Master · Include open files, selections, and IDE context in the next prompt.

Cmd. /ide

Claude Code Command Master · Shows the current session's IDE connection and integration target. File edits occur through subsequent requests and tool calls.

Setup and Login

Standardize Codex installation, updates, identity, and local developer setup.

Multi-Agent Workflows

Split Codex work across bounded agents while preserving ownership and review.

MCP Integration

Connect Codex to MCP servers with explicit tool, data, and trust boundaries.

On this page

Desktop 26.908 (September 11, 2026)Interface ChoiceRules of Use