Extremely annoying "Conversation recap" has not obvious way disable
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What version of Codex CLI is running?
latest
What subscription do you have?
medium
Which model were you using?
gpt-5.6
What platform is your computer?
Mac
What terminal emulator and version are you using (if applicable)?
vs code
Codex doctor report
N/A
What issue are you seeing?
Somebody come up with this "helpful" idea to generate recaps for users so agent literally prints work recap of what it did and then goes and creates it again annoying user to no limit
─ Conversation recap ──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
The user angrily requested a code-level review of how the I
And there is no obvious way to disable this trash.
Codex team, this command "codex doctor --json" inserts tons of private information into the output.
What steps can reproduce the bug?
ask it to do work
What is the expected behavior?
not to have conversation modifiers that impossible to disable
Additional information
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Codex CLI code that emits the “Conversation recap” and check how its display is controlled. Reproduce the behavior by asking the agent to do work, then define done as providing an obvious way to disable the recap without changing unrelated output; investigate the separate privacy concern about codex doctor --json independently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100