> interactive sessions
An interactive Codex session is the default TUI you get by running codex: a composer where you describe tasks and watch the agent work, with a header showing the active model, directory, and approval mode. This section covers resuming and forking past sessions, choosing a model, feeding in images, and pointing Codex at the right directory. Sessions are saved under ~/.codex/sessions/, scoped to the repo you launched from.
// interactive sessions
6 commands$ codex resume$ codex fork$ codex -m gpt-5.6-sol "refactor the auth module"$ codex -i mockup.png "build this screen"$ codex -C ~/projects/api "review this service"$ codex --search "find the current recommended way to configure Vite"// faq
How do I get back into a session I closed?
codex resume opens a picker of recent sessions in the current repo; codex resume --last jumps straight to the most recent, and codex resume --all spans every directory. You can append a prompt to continue immediately, for example codex resume --last "keep going".
What is the difference between resume and fork?
Resuming continues the same session, appending new turns to its transcript. Forking (codex fork) copies the transcript into a new session so you can try a different direction while the original stays intact — the same idea as /fork inside the TUI. Fork branches the chat, not your files on disk.
Which Codex model should I pick?
gpt-5.6-sol is the flagship for the hardest coding, research, and security work; gpt-5.6-terra is the balanced everyday choice; gpt-5.6-luna is fastest and cheapest for light tasks. Switch with -m at launch or /model mid-session. Note that gpt-5.2 and gpt-5.3-codex are deprecated for ChatGPT sign-in.
Can Codex look at screenshots or mockups?
Yes. Attach images to the initial prompt with -i/--image (comma-separate several, e.g. codex -i a.png,b.png "compare these"), or drag files into the TUI composer once you are in a session. It is useful for error screenshots, UI mockups, and diagrams.