Digest / October 4, 2025
Codex Issues Digest — October 4, 2025
31 new issues filed ·
2 resolved in openai/codex (UTC day).
New issues (31)
- When I `resume` a session that was previously started with `--cd`; it should respect that original directory (or at least prompt me to confirm which I want)
- support for streamable HTTP MCP servers not working properly
- Context % not visible in 0.44
- Code review stops after finding only a few issues, requiring repeated reviews
- Codex exec terminates after making a plan (only when using gpt-5-codex)
- Are there any features such as adding global codebase indexes?
- Codex start coding instead of following spec-kit prompts.
- What to add '/' in VS Code Extension
- space after chinese characters would make the last letter unreadable black
- /read command: whole file addition
- "/n" bug
- Return non-zero exit code on SIGINT (Ctrl+C) in exec mode
- edit previous message bug after using /status command in 0.44
- Loss of session data/messages
- Codex 0.42.0 fails to run shell commands on AWS Lambda Python image (Operation not permitted (os error 1))
- Missing child.wait() after start_kill() creates zombie processes and prevents directory cleanup
- Let users rename sessions directly from the resume picker
- Confused: 272k context window or 400k?
- Token usage reporting in Codex to show Input token + Cache token in Token Usage
- Context runs out at 50% stream error
- Add streaming mode OFF
- Do not indent output
- Look for custom prompts in {project root}/.codex/prompts/ first
- Namespacing custom prompts
- Display ongoing thoughts to provide greater explainability
- Copied the large model's reply, only copied the text, lost the markdown format
- Incorrect context usage display in status bar
- Bug: input textarea background not rendering correctly in tmux session
- VS Code Codex Agent burns insane amount of tokens to run two git commands during a single commit (CLI v0.44, gpt-5-codex high, please reset tokens ;_; usage is way higher than usual)
- codex 0.44.0 breaks input on fish
- Pull requests only use the last message context for writing the PR title + description