🦌 DeerFlow - 2.0

English | 中文 | 日本語 | Français | Русский | Português | 한국어

On February 28th, 2026, DeerFlow claimed the 🏆 #1 spot on GitHub Trending following the launch of version 2. Thanks a million to our incredible community — you made this happen! 💪🔥

DeerFlow (Deep Exploration and Efficient Research Flow) is an open-source super agent harness that orchestrates sub-agents, memory, and sandboxes to do almost anything — powered by extensible skills.

https://github.com/user-attachments/assets/a8bcadc4-e040-4cf2-8fda-dd768b999c18

[!NOTE] DeerFlow 2.0 is a ground-up rewrite. It shares no code with v1. If you're looking for the original Deep Research framework, it's maintained on the 1.x branch — contributions there are still welcome. Active development has moved to 2.0.

Official Website

Learn more and see real demos on our official website. The landing-page case studies open as allowlisted, read-only showcases without requiring a sign-in.

Sister Projects

• LLM Space - Meet our secret weapon behind DeerFlow — one desktop tool to prototype agent ideas, inspect each harness step, replay failures, and benchmark performance.

Coding Plan from ByteDance Volcengine

• We strongly recommend using Doubao-Seed-2.0-Code, DeepSeek v3.2 and Kimi 2.5 to run DeerFlow
• Learn more
• 中国大陆地区的开发者请点击这里

InfoQuest

InfoQuest reader, web search, and image search use a 30-second HTTP connect/read inactivity timeout. The crawl timeout and navigation_timeout settings remain separate server-side options; they do not control the local HTTP timeout.

DeerFlow has newly integrated the intelligent search and crawling toolset independently developed by BytePlus — InfoQuest (supports free online experience)

Table of Contents

• 🦌 DeerFlow - 2.0
• Official Website
• Sister Projects
• Coding Plan from ByteDance Volcengine
• InfoQuest
• Table of Contents
• One-Line Agent Setup
• Quick Start
  • Configuration
  • Running the Application
  • Deployment Sizing
  • Option 1: Docker (Recommended)
  • Upgrading an existing checkout
  • Option 2: Local Development
  • Startup Modes
  • LangGraph Studio (Optional)
  • Docker Production Deployment
  • Advanced
  • Sandbox Mode
  • MCP Server
  • IM Channels
  • Request Trace Correlation
  • LangSmith Tracing
  • Langfuse Tracing
  • Monocle Tracing
  • Using Multiple Providers
  • Existing-Run Stream Actions
  • Personal Access Tokens
• From Deep Research to Super Agent Harness
• Core Features
  • Skills \& Tools
  • Exporting Custom Skills
  • Claude Code Integration
  • Private Knowledge Retrieval (RAGFlow)
  • Chat Archive
  • Session Goals
  • Manual Context Compaction
  • Sub-Agents
  • Sandbox \& File System
  • Agentic Browser Control
  • Context Engineering
  • Reading a Referenced Conversation
  • Current Task Notes
  • Long-Term Memory
• Recommended Models
• Embedded Python Client
• Projects
  • Project instructions
  • Document shelf
  • Archive read semantics
  • Trash
• Scheduled Tasks
  • Preview cron occurrences through the API
  • Upgrade Notes
• Terminal Workbench (TUI)
• Documentation
• ⚠️ Security Notice
  • Improper Deployment May Introduce Security Risks
  • Gateway Admin Is Equivalent to Code Execution
  • External Chat Message Roles
  • Deployment Defaults
  • Security Recommendations
• Contributing
• License
• Acknowledgments
  • Key Contributors
• Star History

One-Line Agent Setup

If you use Claude Code, Codex, Cursor, Windsurf, or another coding agent, you can hand it the setup instructions in one sentence:

Help me clone DeerFlow if needed, then bootstrap it for local development by following https://raw.githubusercontent.com/bytedance/deer-flow/main/Install.md

That prompt is intended for coding agents. It tells the agent to clone the repo if needed, choose Docker when available, and stop with the exact next command plus any missing config the user still needs to provide.

Quick Start

Configuration

With run_events.backend: db, caller-supplied ISO 8601 event timestamps are normalized to UTC before storage, preserving their instant when SQLite drops timezone information. Timestamps without an offset are treated as UTC. Previously stored timestamps are not rewritten.

Run event streams include run.terminal for the owning worker's confirmed final Run status, while run.end continues to describe each root graph completion. Terminal publication is best effort; event persistence failure does not undo the Run outcome or prevent stream completion. Recovery with built-in SQL Run and Event stores sharing an engine uses one pooled connection for each guarded event write, so it can publish with only one pool slot available. See Run Event Stream.

Operators can extend lead-agent, subagent, and DeerMem extraction prompts with literal prepend/append configuration without editing source templates. See prompt overlays.

Optional per-model request_admission paces requests to help stay within provider request-per-minute limits. It is disabled by default; see the linked guide to enable it. Enabling it disables exposed SDK retries and the Claude and Codex adapters' internal retry loops so middleware retries pass through request admission again. Middleware retries also cover HTTP 529 overload responses. A warning identifies retry_max_attempts values overridden by admission.

For Google's official Gemini OpenAI-compatible endpoint, use the Gemini reasoning profile.

For MindIE XML tool calls, see the argument parsing and newline compatibility guide. Both synchronous and asynchronous streams retain this compatibility: tool-enabled streams simulate chunks from a non-streaming response, while no-tool streams stay native. Newline compatibility preserves literal escapes inside backtick and tilde code fences, including unclosed fences, in complete and streamed replies.

1. Clone the DeerFlow repository

bash git clone https://github.com/bytedance/deer-flow.git cd deer-flow

2. Run the setup wizard

From the project root directory (deer-flow/), run:

bash make setup

This launches an interactive wizard that guides you through choosing an LLM provider, optional web search, and execution/safety preferences such as sandbox mode, bash access, and file-write tools. It generates a minimal config.yaml and writes your keys to .env. Takes about 2 minutes.

The wizard also lets you configure an optional web search provider, or skip it for now.

Brave web search preserves valid entries in mixed result lists. Malformed response containers or lists containing no usable entries return a structured format error; missing, null, or empty results ke