Codex tip: don’t let one “while you’re at it…” derail a main task that’s already going well. Once a local Codex task is running, press ⌘ + ⌥ + S on Mac or Ctrl + Alt + S on Windows. You can also type /side. It opens a temporary Side Chat beside the main task and picks up the current context. The main thread keeps running, so you don’t have to wait for it to finish or start a whole new task for one small question. Here are two ways to use it: 1. While the main thread is still working on a feature, have Side Chat map the flow. “Starting from [BUTTON / USER FLOW], generate a clickable map that covers only this path. Clicking any node should show its components, callers, dependencies, APIs, data paths, related tests, and source locations. Create only output/sidechat-flow-map.html. Do not modify the project code.” 2. While the page is still being built, have Side Chat catch problems before they become rework. “Open the real app and walk through [CORE FLOW] using ux-audit, impeccable, and transitions-dev. Inspect only this flow. Return: → Annotated desktop and mobile screenshots → The 3 issues that most affect understanding, trust, or conversion → The files or components each issue is likely to involve → A copy-paste prompt the main thread can use to make the changes Do not modify any files in this pass.” Side Chats are temporary. My rule is simple: Send one-off questions to Side Chat. If the result is worth keeping, use Fork chat. Keep only decisions that affect the project in the main task. The main thread keeps moving instead of getting longer every time another side question comes up.