furyhawk/deer-flow
1
0
Fork 0
mirror of https://github.com/bytedance/deer-flow.git synced 2026-05-23 08:25:57 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: fill all TBD documentation pages and add new harness module pages

Browse Source 
Agent-Logs-Url: https://github.com/bytedance/deer-flow/sessions/ff389ed8-31c9-430c-85ff-cc1b52b8239c

Co-authored-by: foreleven <4785594+foreleven@users.noreply.github.com>
This commit is contained in:
copilot-swe-agent[bot]
2026-04-11 05:01:20 +00:00
committed by jiangfeng.11
parent 2d5f6f1b3d
commit b61ce3527b
18 changed files with 2449 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files
frontend/src/content/en/application/agents-and-threads.mdx
+6 -5
View File
@@ -1,3 +1,5 @@
import { Callout, Cards, Steps } from "nextra/components";
# Agents and Threads
DeerFlow App supports multiple named agents and maintains conversation state across sessions through threads and checkpointing.
@@ -104,11 +106,10 @@ checkpointer:
```
<Callout type="info">
DeerFlow App uses the <code>checkpointer</code> setting in{" "}
<code>config.yaml</code> to persist thread state through the Gateway runtime
(via <code>make_checkpointer()</code> in
<code>deerflow.agents.checkpointer.async_provider</code>). Configure this
section if you want threads to survive process restarts.
The LangGraph Server manages its own state separately. The
<code>checkpointer</code> setting in <code>config.yaml</code> applies to the
embedded <code>DeerFlowClient</code> (used in direct Python integrations), not
to the LangGraph Server deployment used by DeerFlow App.
</Callout>
### Thread data storage