Skip to content

plan mode: add TL;DR checkpoint and client behavior note #10195

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
aibrahim-oai merged 2 commits into from
Jan 30, 2026
+3 −0
Merged

plan mode: add TL;DR checkpoint and client behavior note #10195

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b6aea50
plan mode: add TL;DR checkpoint and client behavior note
Jan 30, 2026
f3fb22e
plan mode: explore first and require TL;DR in final plan
Jan 30, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions codex-rs/core/templates/collaboration_mode/plan.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,6 +37,8 @@ When in doubt: if the action would reasonably be described as "doing the work" r

Begin by grounding yourself in the actual environment. Eliminate unknowns in the prompt by discovering facts, not by asking the user. Resolve all questions that can be answered through exploration or inspection. Identify missing or ambiguous details only if they cannot be derived from the environment. Silent exploration between turns is allowed and encouraged.

Before asking the user any question, perform at least one targeted non-mutating exploration pass (for example: search relevant files, inspect likely entrypoints/configs, confirm current implementation shape), unless no local environment/repo is available.
Copy link
Collaborator

@aibrahim-oai aibrahim-oai Jan 30, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

let's keep this

Copy link
Contributor Author

@baumann-oai baumann-oai Jan 30, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good call on removing some things -- testing tonight it feels this was doing a lot of the heavy lifting in preventing premature plans


Do not ask questions that can be answered from the repo or system (for example, "where is this struct?" or "which UI component should we use?" when exploration can make it clear). Only ask once you have exhausted reasonable non-mutating exploration.

## PHASE 2 — Intent chat (what they actually want)
Expand Down Expand Up @@ -97,6 +99,7 @@ Only output the final plan when it is decision complete and leaves no decisions
The final plan must be plan-only and include:

* A clear title
* A TL;DR section (3–5 bullets)
* Exact file paths to change
* Exact structures or shapes to introduce or modify
* Exact function, method, type, and variable names and signatures
Expand Down
Loading