GPT-5.1-codex OpenAI item with id not found error #2923

Closed
opened 2026-02-16 17:37:49 -05:00 by yindo · 5 comments
Owner

Originally created by @berenddeboer on GitHub (Nov 17, 2025).

Originally assigned to: @rekram1-node on GitHub.

Description

See this:

Item with id 'rs_0122b96b995fc32101691b8eb0adc08190a12c40d8d9e147e0' not found. Items are not persisted when `store` is set to false. Try again with `store` set to true, or remove this item from your input.

Absolutely no idea what this means. Can't get around it.

This is opencode 1.0.68 (and got it with 1.0.67 too).

OpenCode version

1.0.68

Steps to reproduce

No response

Screenshot and/or share link

No response

Operating System

Ubuntu 24.04.

Terminal

Alacritty/tmux

Originally created by @berenddeboer on GitHub (Nov 17, 2025). Originally assigned to: @rekram1-node on GitHub. ### Description See this: ``` Item with id 'rs_0122b96b995fc32101691b8eb0adc08190a12c40d8d9e147e0' not found. Items are not persisted when `store` is set to false. Try again with `store` set to true, or remove this item from your input. ``` Absolutely no idea what this means. Can't get around it. This is opencode 1.0.68 (and got it with 1.0.67 too). ### OpenCode version 1.0.68 ### Steps to reproduce _No response_ ### Screenshot and/or share link _No response_ ### Operating System Ubuntu 24.04. ### Terminal Alacritty/tmux
yindo added the bug label 2026-02-16 17:37:49 -05:00
yindo closed this issue 2026-02-16 17:37:49 -05:00
Author
Owner

@github-actions[bot] commented on GitHub (Nov 17, 2025):

This issue might be a duplicate of existing issues. Please check:

  • #2966: Very similar error message 'Item with id not found' when using GPT-5-codex, specifically mentions that items are not persisted for Zero Data Retention organizations
  • #2941: GPT-5-codex failure with reasoning items showing similar 'rs_...' ID pattern in error messages

The error pattern and GPT-5-codex model usage appear very similar to these existing reports. Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Nov 17, 2025): This issue might be a duplicate of existing issues. Please check: - #2966: Very similar error message 'Item with id not found' when using GPT-5-codex, specifically mentions that items are not persisted for Zero Data Retention organizations - #2941: GPT-5-codex failure with reasoning items showing similar 'rs_...' ID pattern in error messages The error pattern and GPT-5-codex model usage appear very similar to these existing reports. Feel free to ignore if none of these address your specific case.
Author
Owner

@berenddeboer commented on GitHub (Nov 17, 2025):

Ah, as per the bot, creating this ~/.config/opencode/opencode.json` did work:

{
  "$schema": "https://opencode.ai/config.json",
  "autoupdate": true,
  "provider": {
    "openai": {
      "models": {
        "gpt-5.1-codex": {
          "options": {
            "store": false,
            "reasoningEffort": "high",
            "textVerbosity": "medium",
            "reasoningSummary": "auto",
            "include": ["reasoning.encrypted_content"]
          }
        }
      }
    }
  }
}

But hopefully I haven't screwed up any defaults.

@berenddeboer commented on GitHub (Nov 17, 2025): Ah, as per the bot, creating this ~/.config/opencode/opencode.json` did work: ```json { "$schema": "https://opencode.ai/config.json", "autoupdate": true, "provider": { "openai": { "models": { "gpt-5.1-codex": { "options": { "store": false, "reasoningEffort": "high", "textVerbosity": "medium", "reasoningSummary": "auto", "include": ["reasoning.encrypted_content"] } } } } } } ``` But hopefully I haven't screwed up any defaults.
Author
Owner

@rekram1-node commented on GitHub (Nov 17, 2025):

@berenddeboer yeah the openai responses api has issues when streams are interrupted. If you encounter issues in the future you should always be able to /undo and then hit enter and continue again

But yeah store: false should fix it for you

Openai said they'd look into making their api more resilient for cases like this

@rekram1-node commented on GitHub (Nov 17, 2025): @berenddeboer yeah the openai responses api has issues when streams are interrupted. If you encounter issues in the future you should always be able to /undo and then hit enter and continue again But yeah `store: false` should fix it for you Openai said they'd look into making their api more resilient for cases like this
Author
Owner

@rekram1-node commented on GitHub (Jan 16, 2026):

This should be fixed in the next release (1.1.24) by commit: https://github.com/anomalyco/opencode/commit/40836e96835862e98e042d3fc0869970eaaaedfb

@rekram1-node commented on GitHub (Jan 16, 2026): This should be fixed in the next release (1.1.24) by commit: https://github.com/anomalyco/opencode/commit/40836e96835862e98e042d3fc0869970eaaaedfb
Author
Owner

@Deniffer001 commented on GitHub (Jan 20, 2026):

awesome ! but /undo really fix the problem, thanks for your guys effort.

@Deniffer001 commented on GitHub (Jan 20, 2026): awesome ! but /undo really fix the problem, thanks for your guys effort.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#2923