openai / openai/codex

Codex CLI 0.154.0 regression: /rename submission silently fails

Open
#44,602 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

bug CLI session TUI
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

What version of Codex CLI is running?

codex-cli 0.154.0

What subscription do you have?

Unknown, authenticated through ChatGPT

Which model were you using?

No response

What platform is your computer?

Darwin 25.6.0 arm64 arm, macOS 26.6.2

What terminal emulator and version are you using (if applicable)?

No response

Codex doctor report

What issue are you seeing?

In Codex CLI 0.154.0, /rename opens the rename prompt and accepts a name, but submitting it produces no visible change or confirmation. The session name remains unchanged.

Relevant log:
codex_tui::bottom_pane::chat_composer: No such file or directory (os error 2)

This worked in 0.153.4 and began failing immediately after the upgrade.

What steps can reproduce the bug?
  1. Start an interactive Codex CLI session.
  2. Run /rename.
  3. Enter a new session name.
  4. Submit the name.
  5. Observe that no rename occurs and no confirmation appears.
What is the expected behavior?

The session is renamed to the submitted name and Codex displays a confirmation.

Additional information

Regression range: 0.153.4 worked; 0.154.0 fails.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the regression in Codex CLI by comparing 0.153.4 and 0.154.0 with the documented /rename steps. Start with the codex_tui::bottom_pane::chat_composer log, then verify that submitting a name changes the session name and displays confirmation without the reported error.

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
Clearly specified
Newbie friendliness
72/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.