github/deer-flow
1
0
Fork 0
mirror of https://github.com/bytedance/deer-flow.git synced 2026-09-12 06:59:07 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs(config): note use_previous_response_id in the Responses API example (#5359)

Browse Source 
`use_previous_response_id` is not a DeerFlow config field; it reaches
`ChatOpenAI` only because `ModelConfig` allows extra keys and the model
factory forwards them. It is easy to mistake for `use_responses_api`, but the
two are not equivalent: the former picks the endpoint, the latter switches
the Responses API from replaying the full history each turn to chaining on
`previous_response_id` with server-side state. Chained context is still
billed as input tokens, and client-side history rewrites are only honored
when the history is replayed. Document the key next to the Responses example
so operators know what it changes. Comment only, no schema change.
This commit is contained in:
Nan Gao 2026-09-11 15:22:26 +07:00 committed by GitHub
parent f52818fe5e
commit 0cf1762638
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
config.example.yaml
View File

@ -252,6 +252,12 @@ models:
# max_retries: 2
# use_responses_api: true
# output_version: responses/v1
# # Optional, forwarded to ChatOpenAI as-is (default false): send only the new
# # turn plus previous_response_id instead of replaying the full history. The
# # chained context is still billed as input tokens, and any client-side
# # history rewrite (e.g. blocked-write payload elision) is only honored when
# # the history is replayed.
# use_previous_response_id: false
# context_window: 400000
# supports_vision: true