Skip to content

Responses API item-not-found loop when continuing session #8746

Closed

Description

@Muadiv

Summary

When using the TUI, a session started returning the error:
Item with id "rs_0e72389746f679bd01696959a2a9e48191a92a10f669c60875" not found. Items are not persisted when store is set to false.
After the first occurrence, every subsequent message in the session repeats the same error and the session is stuck.

Steps to Reproduce

  1. Run opencode v1.1.21.
  2. Start a session and send prompts that include tool calls.
  3. After some time, send another message or type "continue".

Expected

The client should not reference response item IDs when store is false, or it should set store: true whenever it relies on item IDs. Ideally expose a config flag to control this.

Actual

The session loops on the error above for every message.

Activity

  1. github-actions commented on Jan 15, 2026

    @github-actions
    Contributor

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

    Feel free to ignore if none of these address your specific case.

  2. rekram1-node commented on Jan 15, 2026

    @rekram1-node
    Contributor

    This is fixed in 1.1.22 (release going out rn)

  3. KeroRisin commented on Jan 15, 2026

    @KeroRisin

    @rekram1-node Item with id 'rs_01cc8622c815e389016969726a26408199b18b5313a5a07bf3' 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

    still happening

  4. KeroRisin commented on Jan 15, 2026

    @KeroRisin

    im on version 1.1.23

  5. rekram1-node commented on Jan 15, 2026

    @rekram1-node
    Contributor

    @KeroRisin can u share your session? opencode export > session.json

  6. KeroRisin commented on Jan 16, 2026

    @KeroRisin

    @rekram1-node after i fully uninstalled opencode and reinstalled it, the past 2 hours its working good now, not sure why, but it works fine now

  7. rekram1-node commented on Jan 16, 2026

    @rekram1-node
    Contributor

    I found 1 case where it could have been erroring, should rreally be fixed in next release for sure:
    d475107

    If not then there is something going on at a lower level that I need to read into more

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions