Latest in AI
Codex CLI 0.171: Review Files and Subagents Without Losing Your Thread
Use the new default terminal workspace to inspect documents and subagents, keep drafts with the right thread and review edits made before and after steering.
Reviewing an agent's work gets harder when every useful detail pulls you away from the conversation you were following. A generated document lives elsewhere, a subagent has its own transcript, and a correction arrives while code is still changing.
Codex CLI 0.171.0, published November 20, enables the terminal workspace by default. It brings document previews, image previews and subagent transcripts alongside the main conversation. It also fixes thread-input preservation and aggregate diffs across steering.
The useful workflow is a review loop: inspect the evidence beside the task, send a specific correction to the right conversation, then check the complete result. Here is how I would apply it to a small feature change that includes code, a README update and a generated screenshot.
Start with one reviewable outcome
Define the acceptance criteria before delegating work. For this example, the feature must handle an empty result, document its new option and show the correct empty-state screen. Ask for the changed files and the checks performed, not just a summary saying everything is finished.
That creates three separate review targets. The code needs behavioral checks, the README needs accurate instructions, and the screenshot needs visual inspection. None is a substitute for the others.
The release makes these materials easier to keep in view. It does not establish that a previewed document is correct, a screenshot represents the latest build, or a test covered the requirement you actually care about.
Inspect the document before sending another prompt
The document-preview change adds search, keyboard and mouse selection, Markdown copying, zoom and contextual footer hints. Within a document preview, Tab and Shift+Tab navigate links, and Enter opens the selected link. Web links open in the browser; file links resolve relative to the current document.
For the README, search for the new option and read its surrounding example. Check whether the example matches the intended default and what happens when the option is omitted. Follow a relevant local link when the explanation depends on another file.
Use the displayed footer hints for controls rather than borrowing shortcuts from another editor. A concrete correction such as “the example enables the option, but the preceding paragraph says it is disabled” gives the agent something testable to fix.
For the screenshot, verify the visible state against the acceptance criteria. If the image's provenance is unclear, ask which build or command produced it before treating it as evidence.
Read a subagent without changing the active task
The subagent-sidebar implementation changes an important navigation behavior. Selecting a subagent opens its transcript alongside the parent conversation instead of switching the active conversation to that agent. Parent-owned subagents appear in a watch-only reader with navigation, search and selection. Esc returns from that reader to the subagent list with the same agent selected.
Use that view to answer a narrow question: did the reviewer inspect the empty-result path, or only the happy path? Read the evidence behind its conclusion rather than equating a completed status with a completed review.
Keep the correction in the parent task when it changes the overall requirement. For example, ask the main conversation to reconcile the reviewer's finding with the implementation. A watch-only transcript is a place to inspect work, not a second prompt composer.
Switch threads without duplicating follow-ups
The input-preservation fix keeps drafts, queued follow-ups and interrupted steering retries with their original thread across session resumes. It also reconciles delivery receipts before advancing uncertain submitted input and dispatches eligible queued input when the resumed thread is idle.
The practical consequence is to check what is already present before typing the same correction again. An unsent draft, a queued message and a delivered instruction are different states.
Before leaving the feature task, make the follow-up self-contained. On returning, confirm the active thread and inspect the existing input. Do not assume navigation cancelled work, or that a preserved draft has already been sent. These checks are especially useful when two tasks have similar filenames or goals.
Review the whole turn after steering
The aggregate-diff fix retains the diff tracker across steering within a turn. Earlier edits are no longer discarded from that aggregate when sampling restarts, and the final aggregate diff is emitted before turn completion.
That matters when you first request an implementation and then narrow it while work is underway. Review the earlier changes as well as the latest correction. Confirm that the original behavior you no longer wanted was actually removed.
For the example, check code behavior, README wording and screenshot consistency again after the correction. A more complete diff improves visibility; it does not run the application or replace your acceptance checks. Finish the review with an explicit account of what passed and what remains unchecked.
I'm Paras. I work at the intersection of AI, engineering and distribution.
I help developer-tool teams explain product changes and practical workflows through clear technical writing and storytelling.