Codex TUI thread rename fails over VS Code SSH with thread/name/set failed

Resolved 💬 1 comment Opened Jun 5, 2026 by yangshuo-1 Closed Jun 10, 2026

What version of Codex CLI is running?

v0.137.0

What subscription do you have?

API

Which model were you using?

gpt=5.5

What platform is your computer?

Linux 5.4.0-156-generic x86_64 x86_64

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

zellij

Codex doctor report

What issue are you seeing?

Codex TUI fails to rename a thread.

Full error message:

```text
Error: thread/name/set failed in TUI

Environment/context:

  • I am using VS Code SSH to connect to a remote Linux server.
  • The error happens in the VS Code integrated terminal.
  • The same error also happens when running Codex inside a zellij terminal session on the same remote server.
  • PII redacted.

What steps can reproduce the bug?

  1. Connect to a remote Linux server using VS Code SSH.
  2. Open Codex TUI in the VS Code integrated terminal.
  3. Open an existing thread.
  4. Try to rename the thread.
  5. Confirm the new name.

Actual result:

```text
Error: thread/name/set failed in TUI

The same issue can also be reproduced by running Codex inside zellij on the same remote Linux server and trying to rename a thread.

Expected result:

The thread name should be updated successfully.

Thread id: TODO, if applicable.

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗