coder/coderd/database/migrations/000450_chat_messages_provider_response_id.up.sql at f22d4e2cbb064dfe3dae11b9097dca3f6065bda1 - coder - Gitea: Git with a cup of tea

shishantbiswas/coder

mirror of https://github.com/coder/coder.git synced 2026-06-02 20:48:20 +00:00

Files

T

Michael Suchacz 02356c61f6 fix: use previous_response_id chaining for OpenAI store=true follow-ups (#23450 )

OpenAI Responses follow-up turns were replaying full assistant/tool
history even when `store=true`, which breaks after reasoning +
provider-executed `web_search` output.

This change persists the OpenAI response ID on assistant messages, then
in `coderd/x/chatd` switches `store=true` follow-ups to
`previous_response_id` chaining with a system + new-user-only prompt.
`store=false` and missing-ID cases still fall back to manual replay.

It also updates the fake OpenAI server and integration coverage for the
chaining contract, and carries the rebased path move to `coderd/x/chatd`
plus the migration renumber needed after rebasing onto `main`.

2026-03-24 14:57:40 +01:00

2 lines

64 B

SQL

Raw Blame History

ALTER TABLE chat_messages ADD COLUMN provider_response_id TEXT;