DeerFlow Skill

Interact with DeerFlow AI agent platform via its HTTP API.

by bytedance·MIT license·★ 83,473 Stars on the repo·GitHub ↗

Use now

Files of DeerFlow Skill

bytedance/main1 file shown
SKILL.md
Show the full text218 lines

DeerFlow Skill

Communicate with a running DeerFlow instance via its HTTP API. DeerFlow is an AI agent platform built on LangGraph that orchestrates sub-agents for research, code execution, web browsing, and more.

Architecture

DeerFlow exposes two API surfaces behind an Nginx reverse proxy:

Service Direct Port Via Proxy Purpose
Gateway API 8001 $DEERFLOW_GATEWAY_URL REST endpoints and embedded agent runtime
LangGraph-compatible API 8001 $DEERFLOW_LANGGRAPH_URL Agent threads, runs, streaming

Environment Variables

All URLs are configurable via environment variables. Read these env vars before making any request.

Variable Default Description
DEERFLOW_URL http://localhost:2026 Unified proxy base URL
DEERFLOW_GATEWAY_URL ${DEERFLOW_URL} Gateway API base (models, skills, memory, uploads)
DEERFLOW_LANGGRAPH_URL ${DEERFLOW_URL}/api/langgraph LangGraph API base (threads, runs)

When making curl calls, always resolve the URL like this:

# Resolve base URLs from env (do this FIRST before any API call)
DEERFLOW_URL="${DEERFLOW_URL:-http://localhost:2026}"
DEERFLOW_GATEWAY_URL="${DEERFLOW_GATEWAY_URL:-$DEERFLOW_URL}"
DEERFLOW_LANGGRAPH_URL="${DEERFLOW_LANGGRAPH_URL:-$DEERFLOW_URL/api/langgraph}"

Available Operations

1. Health Check

Verify DeerFlow is running:

curl -s "$DEERFLOW_GATEWAY_URL/health"
2. Send a Message (Streaming)

This is the primary operation. It creates a thread and streams the agent's response.

Step 1: Create a thread

curl -s -X POST "$DEERFLOW_LANGGRAPH_URL/threads" \
  -H "Content-Type: application/json" \
  -d '{}'

Response: {"thread_id": "<uuid>", ...}

Step 2: Stream a run

curl -s -N -X POST "$DEERFLOW_LANGGRAPH_URL/threads/<thread_id>/runs/stream" \
  -H "Content-Type: application/json" \
  -d '{
    "assistant_id": "lead_agent",
    "input": {
      "messages": [
        {
          "type": "human",
          "content": [{"type": "text", "text": "YOUR MESSAGE HERE"}]
        }
      ]
    },
    "stream_mode": ["values", "messages-tuple"],
    "stream_subgraphs": true,
    "config": {
      "recursion_limit": 1000
    },
    "context": {
      "thinking_enabled": true,
      "is_plan_mode": true,
      "subagent_enabled": true,
      "thread_id": "<thread_id>"
    }
  }'

The response is an SSE stream. Each event has the format:

event: <event_type>
data: <json_data>

Key event types:

  • metadata — run metadata including run_id
  • values — full state snapshot with messages array
  • messages-tuple — incremental message updates (AI text chunks, tool calls, tool results)
  • end — stream is complete

Context modes (set via context):

  • Flash mode: thinking_enabled: false, is_plan_mode: false, subagent_enabled: false
  • Standard mode: thinking_enabled: true, is_plan_mode: false, subagent_enabled: false
  • Pro mode: thinking_enabled: true, is_plan_mode: true, subagent_enabled: false
  • Ultra mode: thinking_enabled: true, is_plan_mode: true, subagent_enabled: true
3. Continue a Conversation

To send follow-up messages, reuse the same thread_id from step 2 and POST another run with the new message.

4. List Models
curl -s "$DEERFLOW_GATEWAY_URL/api/models"

Returns: {"models": [{"name": "...", "provider": "...", ...}, ...]}

5. List Skills
curl -s "$DEERFLOW_GATEWAY_URL/api/skills"

Returns: {"skills": [{"name": "...", "enabled": true, ...}, ...]}

6. Enable/Disable a Skill
curl -s -X PUT "$DEERFLOW_GATEWAY_URL/api/skills/<skill_name>" \
  -H "Content-Type: application/json" \
  -d '{"enabled": true}'
7. List Agents
curl -s "$DEERFLOW_GATEWAY_URL/api/agents"

Returns: {"agents": [{"name": "...", ...}, ...]}

8. Get Memory
curl -s "$DEERFLOW_GATEWAY_URL/api/memory"

Returns user context, facts, and conversation history summaries.

9. Upload Files to a Thread
curl -s -X POST "$DEERFLOW_GATEWAY_URL/api/threads/<thread_id>/uploads" \
  -F "files=@/path/to/file.pdf"

Supports PDF, PPTX, XLSX, DOCX — automatically converts to Markdown.

10. List Uploaded Files
curl -s "$DEERFLOW_GATEWAY_URL/api/threads/<thread_id>/uploads/list"
11. Get Thread History
curl -s "$DEERFLOW_LANGGRAPH_URL/threads/<thread_id>/history"
12. List Threads
curl -s -X POST "$DEERFLOW_LANGGRAPH_URL/threads/search" \
  -H "Content-Type: application/json" \
  -d '{"limit": 20, "sort_by": "updated_at", "sort_order": "desc"}'

Usage Script

For sending messages and collecting the full response, use the helper script:

bash /path/to/skills/claude-to-deerflow/scripts/chat.sh "Your question here"

See scripts/chat.sh for the implementation. The script:

  1. Checks health
  2. Creates a thread
  3. Streams the run and collects the final AI response
  4. Prints the result

Parsing SSE Output

The stream returns SSE events. To extract the final AI response from a values event:

  • Look for the last event: values block
  • Parse its data JSON
  • The messages array contains all messages; the last one with type: "ai" is the response
  • The content field of that message is the AI's text reply

Error Handling

  • If health check fails, DeerFlow is not running. Inform the user they need to start it.
  • If the stream returns an error event, extract and display the error message.
  • Common issues: port not open, services still starting up, config errors.

Tips

  • For quick questions, use flash mode (fastest, no planning).
  • For research tasks, use pro or ultra mode (enables planning and sub-agents).
  • You can upload files first, then reference them in your message.
  • Thread IDs persist — you can return to a conversation later.
1---
2name: claude-to-deerflow
3description: "Interact with DeerFlow AI agent platform via its HTTP API. Use this skill when the user wants to send messages or questions to DeerFlow for research/analysis, start a DeerFlow conversation thread, check DeerFlow status or health, list available models/skills/agents in DeerFlow, manage DeerFlow memory, upload files to DeerFlow threads, or delegate complex research tasks to DeerFlow. Also use when the user mentions deerflow, deer flow, or wants to run a deep research task that DeerFlow can handle."
4---
5 
6# DeerFlow Skill
7 
8Communicate with a running DeerFlow instance via its HTTP API. DeerFlow is an AI agent platform
9built on LangGraph that orchestrates sub-agents for research, code execution, web browsing, and more.
10 
11## Architecture
12 
13DeerFlow exposes two API surfaces behind an Nginx reverse proxy:
14 
15| Service | Direct Port | Via Proxy | Purpose |
16|----------------|-------------|----------------------------------|----------------------------------|
17| Gateway API | 8001 | `$DEERFLOW_GATEWAY_URL` | REST endpoints and embedded agent runtime |
18| LangGraph-compatible API | 8001 | `$DEERFLOW_LANGGRAPH_URL` | Agent threads, runs, streaming |
19 
20## Environment Variables
21 
22All URLs are configurable via environment variables. **Read these env vars before making any request.**
23 
24| Variable | Default | Description |
25|-------------------------|------------------------------------------|------------------------------------|
26| `DEERFLOW_URL` | `http://localhost:2026` | Unified proxy base URL |
27| `DEERFLOW_GATEWAY_URL` | `${DEERFLOW_URL}` | Gateway API base (models, skills, memory, uploads) |
28| `DEERFLOW_LANGGRAPH_URL`| `${DEERFLOW_URL}/api/langgraph` | LangGraph API base (threads, runs) |
29 
30When making curl calls, always resolve the URL like this:
31 
32```bash
33# Resolve base URLs from env (do this FIRST before any API call)
34DEERFLOW_URL="${DEERFLOW_URL:-http://localhost:2026}"
35DEERFLOW_GATEWAY_URL="${DEERFLOW_GATEWAY_URL:-$DEERFLOW_URL}"
36DEERFLOW_LANGGRAPH_URL="${DEERFLOW_LANGGRAPH_URL:-$DEERFLOW_URL/api/langgraph}"
37```
38 
39## Available Operations
40 
41### 1. Health Check
42 
43Verify DeerFlow is running:
44 
45```bash
46curl -s "$DEERFLOW_GATEWAY_URL/health"
47```
48 
49### 2. Send a Message (Streaming)
50 
51This is the primary operation. It creates a thread and streams the agent's response.
52 
53**Step 1: Create a thread**
54 
55```bash
56curl -s -X POST "$DEERFLOW_LANGGRAPH_URL/threads" \
57 -H "Content-Type: application/json" \
58 -d '{}'
59```
60 
61Response: `{"thread_id": "<uuid>", ...}`
62 
63**Step 2: Stream a run**
64 
65```bash
66curl -s -N -X POST "$DEERFLOW_LANGGRAPH_URL/threads/<thread_id>/runs/stream" \
67 -H "Content-Type: application/json" \
68 -d '{
69 "assistant_id": "lead_agent",
70 "input": {
71 "messages": [
72 {
73 "type": "human",
74 "content": [{"type": "text", "text": "YOUR MESSAGE HERE"}]
75 }
76 ]
77 },
78 "stream_mode": ["values", "messages-tuple"],
79 "stream_subgraphs": true,
80 "config": {
81 "recursion_limit": 1000
82 },
83 "context": {
84 "thinking_enabled": true,
85 "is_plan_mode": true,
86 "subagent_enabled": true,
87 "thread_id": "<thread_id>"
88 }
89 }'
90```
91 
92The response is an SSE stream. Each event has the format:
93```
94event: <event_type>
95data: <json_data>
96```
97 
98Key event types:
99- `metadata` — run metadata including `run_id`
100- `values` — full state snapshot with `messages` array
101- `messages-tuple` — incremental message updates (AI text chunks, tool calls, tool results)
102- `end` — stream is complete
103 
104**Context modes** (set via `context`):
105- Flash mode: `thinking_enabled: false, is_plan_mode: false, subagent_enabled: false`
106- Standard mode: `thinking_enabled: true, is_plan_mode: false, subagent_enabled: false`
107- Pro mode: `thinking_enabled: true, is_plan_mode: true, subagent_enabled: false`
108- Ultra mode: `thinking_enabled: true, is_plan_mode: true, subagent_enabled: true`
109 
110### 3. Continue a Conversation
111 
112To send follow-up messages, reuse the same `thread_id` from step 2 and POST another run
113with the new message.
114 
115### 4. List Models
116 
117```bash
118curl -s "$DEERFLOW_GATEWAY_URL/api/models"
119```
120 
121Returns: `{"models": [{"name": "...", "provider": "...", ...}, ...]}`
122 
123### 5. List Skills
124 
125```bash
126curl -s "$DEERFLOW_GATEWAY_URL/api/skills"
127```
128 
129Returns: `{"skills": [{"name": "...", "enabled": true, ...}, ...]}`
130 
131### 6. Enable/Disable a Skill
132 
133```bash
134curl -s -X PUT "$DEERFLOW_GATEWAY_URL/api/skills/<skill_name>" \
135 -H "Content-Type: application/json" \
136 -d '{"enabled": true}'
137```
138 
139### 7. List Agents
140 
141```bash
142curl -s "$DEERFLOW_GATEWAY_URL/api/agents"
143```
144 
145Returns: `{"agents": [{"name": "...", ...}, ...]}`
146 
147### 8. Get Memory
148 
149```bash
150curl -s "$DEERFLOW_GATEWAY_URL/api/memory"
151```
152 
153Returns user context, facts, and conversation history summaries.
154 
155### 9. Upload Files to a Thread
156 
157```bash
158curl -s -X POST "$DEERFLOW_GATEWAY_URL/api/threads/<thread_id>/uploads" \
159 -F "files=@/path/to/file.pdf"
160```
161 
162Supports PDF, PPTX, XLSX, DOCX — automatically converts to Markdown.
163 
164### 10. List Uploaded Files
165 
166```bash
167curl -s "$DEERFLOW_GATEWAY_URL/api/threads/<thread_id>/uploads/list"
168```
169 
170### 11. Get Thread History
171 
172```bash
173curl -s "$DEERFLOW_LANGGRAPH_URL/threads/<thread_id>/history"
174```
175 
176### 12. List Threads
177 
178```bash
179curl -s -X POST "$DEERFLOW_LANGGRAPH_URL/threads/search" \
180 -H "Content-Type: application/json" \
181 -d '{"limit": 20, "sort_by": "updated_at", "sort_order": "desc"}'
182```
183 
184## Usage Script
185 
186For sending messages and collecting the full response, use the helper script:
187 
188```bash
189bash /path/to/skills/claude-to-deerflow/scripts/chat.sh "Your question here"
190```
191 
192See `scripts/chat.sh` for the implementation. The script:
1931. Checks health
1942. Creates a thread
1953. Streams the run and collects the final AI response
1964. Prints the result
197 
198## Parsing SSE Output
199 
200The stream returns SSE events. To extract the final AI response from a `values` event:
201- Look for the last `event: values` block
202- Parse its `data` JSON
203- The `messages` array contains all messages; the last one with `type: "ai"` is the response
204- The `content` field of that message is the AI's text reply
205 
206## Error Handling
207 
208- If health check fails, DeerFlow is not running. Inform the user they need to start it.
209- If the stream returns an error event, extract and display the error message.
210- Common issues: port not open, services still starting up, config errors.
211 
212## Tips
213 
214- For quick questions, use flash mode (fastest, no planning).
215- For research tasks, use pro or ultra mode (enables planning and sub-agents).
216- You can upload files first, then reference them in your message.
217- Thread IDs persist — you can return to a conversation later.
218 

Discussion