Codex App and IDE

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

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.