codex - 💡(How to fix) Fix Add way to hide tool calls/output in TUI [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#18396Fetched 2026-04-18 05:54:56
View on GitHub
Comments
0
Participants
1
Timeline
5
Reactions
0
Author
Participants
Timeline (top)
labeled ×3renamed ×1unlabeled ×1

Code Example

The handover file is written and the skill now documents the “reply ok or provide replacement filename” workflow. I’ll run the handover listing helper once to confirm the file
  appears newest-first.

 Explored
Read git-review-sidebar-scroll-handover-skill.md

Ran /usr/bin/python3 /Users/ma/.codex/skills/handover/scripts/list-handovers.py
  └ git-review-sidebar-scroll-handover-skill.md

Ran rg -n "reply with `ok`|replacement filename|path separators" /Users/ma/.codex/skills/handover/SKILL.md
  └ zsh:1: command not found: ok
    35:3. Ask the user to reply with `ok` to accept the proposed filename or send a replacement filename.
    36:4. If the user sends a replacement filename, normalize and validate it before writing:
    40:   - Do not allow path separators; handovers must stay inside `./.codex/handover`.

 Called
  └ ram.node.create({"body":"Decision: created project handover at .codex/handover/git-review-sidebar-scroll-handover-skill.md and updated /Users/ma/.codex/skills/handover/
        SKILL.md to use the explicit filename workflow: propose filename, user replies ok or replacement, normalize/validate, then write.","branchId":"B-
        00016","conversationId":"C-00006","provenance":"assistant","stability":"stable","state":"completed","type":"decision"})
    {"record": {"body": "Decision: created project handover at .codex/handover/git-review-sidebar-scroll-handover-skill.md and updated /Users/ma/.codex/skills/handover/SKILL.md to
        use the explicit filename workflow: propose filename, user replies ok or replacement, normalize/validate, then write.", "conversationID": "C-00006", "createdAt": "2026-04-
        17T20:27:55Z", "homeBranchID": "B-00016", "id": "D-00356", "kind": "decision", "provenance": {"kind": "assistant"}, "stability": "stable", "state": "completed",
        "updatedAt": "2026-04-17T20:27:55Z"}, "recordType": "node"}
RAW_BUFFERClick to expand / collapse

What variant of Codex are you using?

codex-cli 0.121.0

What feature would you like to see?

This is how my terminal look after every other command.

• The handover file is written and the skill now documents the “reply ok or provide replacement filename” workflow. I’ll run the handover listing helper once to confirm the file
  appears newest-first.

• Explored
  └ Read git-review-sidebar-scroll-handover-skill.md

• Ran /usr/bin/python3 /Users/ma/.codex/skills/handover/scripts/list-handovers.py
  └ git-review-sidebar-scroll-handover-skill.md

• Ran rg -n "reply with `ok`|replacement filename|path separators" /Users/ma/.codex/skills/handover/SKILL.md
  └ zsh:1: command not found: ok
    35:3. Ask the user to reply with `ok` to accept the proposed filename or send a replacement filename.
    36:4. If the user sends a replacement filename, normalize and validate it before writing:
    40:   - Do not allow path separators; handovers must stay inside `./.codex/handover`.

• Called
  └ ram.node.create({"body":"Decision: created project handover at .codex/handover/git-review-sidebar-scroll-handover-skill.md and updated /Users/ma/.codex/skills/handover/
        SKILL.md to use the explicit filename workflow: propose filename, user replies ok or replacement, normalize/validate, then write.","branchId":"B-
        00016","conversationId":"C-00006","provenance":"assistant","stability":"stable","state":"completed","type":"decision"})
    {"record": {"body": "Decision: created project handover at .codex/handover/git-review-sidebar-scroll-handover-skill.md and updated /Users/ma/.codex/skills/handover/SKILL.md to
        use the explicit filename workflow: propose filename, user replies ok or replacement, normalize/validate, then write.", "conversationID": "C-00006", "createdAt": "2026-04-
        17T20:27:55Z", "homeBranchID": "B-00016", "id": "D-00356", "kind": "decision", "provenance": {"kind": "assistant"}, "stability": "stable", "state": "completed",
        "updatedAt": "2026-04-17T20:27:55Z"}, "recordType": "node"}

Trying to parse the content from the tools output is a pain. Any way we can collapse those lines by default?

Additional information

No response

extent analysis

TL;DR

The issue can be addressed by modifying the output formatting of the Codex tool to collapse similar lines by default.

Guidance

  • Investigate the configuration options of the Codex tool, specifically codex-cli 0.121.0, to see if there are any settings that control output formatting.
  • Check the documentation of the list-handovers.py script and the rg command to understand how their output is generated and if it can be customized.
  • Consider using a custom output parser or formatter to process the tool's output and collapse similar lines.
  • Look into the possibility of submitting a feature request to the Codex developers to add a built-in option for collapsing similar lines in the tool's output.

Notes

The provided information does not include the exact code or configuration used by the Codex tool, so a precise solution cannot be given. The guidance provided is based on general principles of output formatting and customization.

Recommendation

Apply workaround: Modify the output formatting of the Codex tool or use a custom output parser to collapse similar lines, as the current version of the tool may not have a built-in option for this feature.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING