bug: of type 'function_call' was provided without its required

[dzianisv]

This issue just randomly happens when an agent work was interrupted by network issue or user
Investigate and fix
After that error happens - session unusable!

■ {
  "error": {
    "message": "Item 'fc_0b93c0bd600309580069c55d8a2014819385c54e03b5cdc873' of type 'function_call' was provided without its required
'reasoning' item: 'rs_0b93c0bd600309580069c55d832af0819385143a8aea1f2e7c'.",
    "type": "invalid_request_error",
    "param": "input",
    "code": null
  }
}

[OpenCodeEngineer]

Investigating now on a dedicated branch. I’m tracing how interrupted tool/agent turns rebuild response history, then I’ll add a regression test for the broken replay path and patch the session recovery logic.

[OpenCodeEngineer]

Implemented and validated a local fix on issue-47-recover-reasoning-items.

What changed:

• persist partial reasoning items from response.output_item.added into in-memory history immediately
• upsert completed reasoning items by id so the final item replaces the partial one instead of duplicating it
• always re-attach model item ids on /responses requests so reasoning/function-call lineage survives replay on the standard Responses path too
• rebuild retry prompts from live session history before a transport retry, so same-turn retries include any reasoning/tool items already recorded before the disconnect

Regression coverage added:

• interrupted tool turn now replays reasoning -> function_call -> function_call_output on the next request
• incomplete SSE retry now replays the interrupted reasoning/call chain on the retry request

Passing local validation:

• cargo test -p codex-core --lib context_manager::history::tests::record_items_replaces_reasoning_item_with_same_non_empty_id -- --exact
• cargo test -p codex-core --test all suite::abort_tasks::interrupt_tool_records_history_entries -- --exact
• cargo test -p codex-core --test all suite::stream_no_completed::retries_on_early_close -- --exact
• cargo test -p codex-core --test all suite::cli_stream::responses_mode_stream_cli -- --exact

Next step is pushing the branch and opening the PR linked to this issue.

[OpenCodeEngineer]

PR is open: #48

This carries the reasoning-lineage fix plus the interrupt/retry regressions and the codex CLI binary validation noted above.

[OpenCodeEngineer]

Reopening because the interrupted-session bug class is still reproducible on March 29, 2026 in the latest locally rebuilt binary.

After rebuilding and restarting Codex, pressing Esc to stop an active request and then continuing in the same session can still produce an invalid input sequencing error. The latest repro surfaced as the related reasoning variant tracked in #18:

{
  "error": {
    "message": "Item 'rs_043afd821d13d57b0069c88b2ce4b081908687d32a798efc60' of type 'reasoning' was provided without its required following item.",
    "type": "invalid_request_error",
    "param": "input",
    "code": null
  }
}

So the underlying interrupted/aborted-session recovery problem is not actually resolved yet.