Fix reasoning data lost when restoring conversation history#301
Conversation
|
Its works very well for me |
|
I can also confirm that this fixes the issue. We have run into this issue with reasoning models and this solves it. Any timeline on when it could be merged? |
It still error if function call more then one in one message. Fixed in PR 461 |
|
This doesn’t fix the issue, because all tool calls are still merged into a single message, while every provider requires two messages per tool call: #402 |
Yes this PR is a month old now, and since then this package has pulled in its own gateway functionality into the package natively, but at the time I also lodged prism-php/prism#971 upstream to fix the other issue in the Prism gateway. Been running both fixes using |
Issue laravel#361 (rehydrating reasoningId/reasoningSummary on ToolCall) is already resolved on 0.x via laravel#301. The remaining real bug this branch addresses is multi-turn message ordering loss in DatabaseConversationStore. Drop the unrelated OpenAI/xAI streaming changes so this PR stays focused.
Originally introduced in PR #203.
This fixes #271, by ensuring that reasoning_id and reasoning_summary are replayed from database conversations to OpenAI reasoning models.