frequent malformed commands
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?
154
What subscription do you have?
Business Pro
Which model were you using?
gpt-5.6-sol medium
What platform is your computer?
Windows 11 25H2
What terminal emulator and version are you using (if applicable)?
PowerShell
Codex doctor report
• codex doctor --json completed with overall status: fail.
The actionable findings are:
- Rollout database parity warning
- 26 active rollout files
- 1,321 active database rows
- 1,295 stale rows referencing missing/unusable rollout files
- 0 missing database rows for files that still exist
- No duplicate paths, duplicate thread IDs, malformed filenames, or scan errors
This matches the missing session JSON problem you described. The stale database references—not missing data reconstruction—need cleanup.
- Terminal environment failure
- TERM=dumb
- NO_COLOR=1
- Standard input/output are non-terminal
This is expected when Doctor runs through this non-interactive command channel. It is not evidence of the strange cerc or E:\ siècles command fragments.
Everything else passed, including authentication, configuration, runtime provenance, MCP connectivity, provider HTTP/WebSocket connectivity, SQLite integrity, bundled rg, disk capacity, and sandbox configuration.
Codex CLI is current at 0.154.0. A desktop application update is available: installed 26.903.9818.0, latest 26.908.4561.0.
What issue are you seeing?
thread ID 01a096e6-800d-7103-a4a9-c0c0aee4b68b
in the provided thread submitted via feedback are multiple instances of strange malformed words or attempted commands
What steps can reproduce the bug?
Uploaded thread: 01a096e6-800d-7103-a4a9-c0c0aee4b68b
What is the expected behavior?
this occurs randomly while codex is working
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 inspecting the uploaded thread 01a096e6-800d-7103-a4a9-c0c0aee4b68b and the reported malformed words or attempted commands. Reproduce on Windows 11 in PowerShell with Codex CLI 0.154.0, using the provided doctor report for environment context. Done means the cause is identified and random malformed commands no longer occur, with evidence from a repeatable test or reproduction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell, rust
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100