{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiaa5rw2rge6armmauz5sxoe5uz5hvogozaouqm3aumeheurmyvlku",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mjz4ayohctt2"
  },
  "path": "/t/hosted-shell-continuations-require-missing-shell-call-output/1375917#post_5",
  "publishedAt": "2026-04-21T12:00:40.000Z",
  "site": "https://community.openai.com",
  "textContent": "Hey everyone, Thanks for the detailed report. Are you still seeing this issue?\n\nIf yes, could you share the `x-request-id` from a failed continuation request and the execution timestamp, including timezone? Please share the failed request ID, not a later retry that succeeded.\n\nI tested the hosted shell flow with `previous_response_id` and wasn’t able to reproduce the failure: the first response included matching `shell_call` / `shell_call_output` items, and the follow-up completed successfully.\n\nOne workaround I verified is to avoid relying on stored history and replay the prior response output items explicitly, then reuse the returned shell container with `container_reference`. In other words: include the previous `response.output` in the next request’s `input`, append the next user message, and set the shell tool environment to the prior `container_id`. Hope this helps. Thank you!",
  "title": "Hosted `shell` Continuations Require Missing `shell_call_output`"
}