bytedance

deer-flow: Orchestrate Long-Running AI Agent Tasks

DeerFlow is a self-hosted harness for AI agents that coordinate subagents, memory, tools, and sandboxes on tasks that can run from minutes to hours. It suits teams building research, coding, and content workflows that need an extensible agent runtime.

View on GitHub Compare
Stars
83.4k
Forks
11.6k
Stars, last 30 days
+1,376

Our take

Health score

82/100

How it is scored
Activity
67
Community
92
Issues
88
Pull requests
79

+1,376 stars in the last 30 days

  • Merges more pull requests than 86% of the projects we track
  • Closes issues faster than 81% of the projects we track
  • More contributors than 78% of the projects we track

Project history

Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.

Selected snapshot

Stars

85,460

Forks

12,050

Change since Nov 17, 2026: +48 stars·+6 forks

Overview

DeerFlow is a super-agent harness for coordinating AI work that takes more than a single prompt-response cycle. A lead agent can delegate to subagents and use skills, tools, memory, and sandboxes to research, code, and create across longer tasks.

It is intended for developers and teams who want to run and extend an agent system, rather than adopt a narrowly scoped research library. The repository describes version 2.0 as a ground-up rewrite; the earlier framework remains on the main-1.x branch.

Key Features

  • Coordinates a lead agent with subagents for delegated work.
  • Provides sandbox modes for local, Docker, and Kubernetes-backed execution.
  • Extends agent capabilities through skills and configurable MCP servers.
  • Includes short-term context management and long-term memory features.
  • Offers web search and crawling integrations, with providers configured by the operator.
  • Supports a web interface, messaging channels, and a terminal workbench.
  • Provides Docker and local development startup paths, plus SQLite or PostgreSQL for persistent deployments.

Use Cases

  • Developers can build research workflows that gather and synthesize information across extended runs.
  • Engineering teams can delegate coding and repository tasks to agents with sandboxed execution.
  • Operators can offer a shared agent workspace with configurable models, skills, and tool integrations.
  • Teams can connect messaging channels so users can submit agent tasks through supported chat platforms.

Getting Started

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

The setup wizard configures an LLM provider and optional integrations. See the README for prerequisites, deployment options, configuration, and security guidance.

Alternatives

  • deepagents: Deep Agents provides planning, delegation, file access, and context management in a Python harness, while DeerFlow emphasizes self-hosted, long-running workflows with sandboxes and memory.
  • mcp-agent: mcp-agent centers on MCP server integrations and composable workflows, including Temporal execution, rather than DeerFlow’s broader self-hosted agent runtime.
  • OpenHuman: OpenHuman packages persistent agents as desktop, browser, and terminal apps as well as a library, while DeerFlow focuses on a self-hosted harness for extended tasks.
  • fast-agent: fast-agent emphasizes declarative multimodal agents and MCP workflows, while DeerFlow targets long-running tasks coordinated through subagents, memory, and sandboxes.
ProjectLanguageLicenseStarsStatus
deer-flowPythonMIT83.4kNot checked yet
deepagentsPythonMIT29.9kActive
mcp-agentPythonApache-2.08.6kQuiet
OpenHumanRustGPL-3.042.2kActive
fast-agentPythonApache-2.03.9kActive

Considerations

  • Running the system requires configuring an LLM provider, and optional search or tool integrations may require separate credentials.
  • The README lists Python 3.12+ and Node.js 22+ for the project, and recommends Docker for deployment.
  • Sandboxing and host access depend on configuration. Review the security guidance before exposing a deployment or enabling execution capabilities.
  • Version 2.0 is a ground-up rewrite, so users of the original framework should consult the main-1.x branch for that codebase.
  • The repository has 895 open issues, so evaluate current maintenance needs and compatibility for your intended deployment.

Found this useful?

Share it with someone who would like deer-flow.

Comparisons