codex plugin list panics when stdout pipe closes early
Open
Nobody has claimed this yet.
bug
CLI
skills
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What happened
codex plugin list panics when its stdout consumer exits early. This makes normal bounded inspection such as piping to head look like a Codex crash.
Reproduction
set -o pipefail
codex plugin list | head -n 1
Observed with codex-cli 0.153.4 on macOS:
Marketplace `openai-primary-runtime`
thread 'codex-main' (...) panicked at .../library/std/src/io/stdio.rs:1165:9:
failed printing to stdout: Broken pipe (os error 32)
Expected behavior
Treat a closed stdout pipe as a normal early consumer exit and terminate without a Rust panic/backtrace. This is especially useful for commands that can produce a large plugin catalog.
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 running codex plugin list | head -n 1 with pipefail and trace the codex plugin list output path. Verify the change by confirming that an early stdout close exits without a Rust panic, backtrace, or error output.
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
- Mostly clear
- Newbie friendliness
- 68/100