openai / openai/codex

Session becomes unusable: Invalid input[N].id = fc_... (expected ctc) when replaying history

Open
#40,039 6 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

app bug session windows-os
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

What version of the Codex App are you using (From “About Codex” dialog)?

26.818.32112

What subscription do you have?

use openai api

What platform is your computer?

Microsoft Windows NT 10.0.22635.0 x64

What issue are you seeing?

Using OpenAI API to access Codex ++, the dialogue will now report this error every once in a while, resulting in the whole dialogue not being able to be used normally.

A new dialogue must be opened, but this error will also occur after a while in the new dialogue, which will make it impossible to use normally.

error example:
Invalid 'input[107].id': 'fc_08d2f9b0333b7690016a88ed74f82c87d0aa6bf2edc704ebc0'. Expected an ID that begins with 'ctc'. [trace_id=76843951e11a52345eaa4b2aba010e12]

Image
What steps can reproduce the bug?

This error occurs frequently in long sessions, but it can take a long time to open a new session.
Once this error occurs, it cannot continue and a new session must be opened.

What is the expected behavior?

No response

Additional information

No response

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

Start by reproducing the failure during a long Codex App session on Windows using the OpenAI API, then trace the history replay path that sends the invalid input ID. Done means an existing session can continue after history replay without rejecting an ID that begins with fc_.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
api
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.