codex - 💡(How to fix) Fix Codex TUI thread rename fails over VS Code SSH with thread/name/set failed

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Error Message

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:

Code Example



---

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:
RAW_BUFFERClick to expand / collapse

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:

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_

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING