deer-flow
DeerFlow (2.0) is an open-source long-horizon “super agent” harness that orchestrates sub-agents, memory, and sandboxed execution to perform complex tasks over minutes to hours, with extensible skills/tools and support for configurable model providers (Python/Node ecosystem) and integrations like MCP servers and messaging (IM) channels.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
README shows extensive credential configuration via environment variables and provider config, and indicates OAuth token flows for MCP servers and token-based auth for IM channels. However, the excerpt does not provide detailed security guarantees (e.g., TLS/HTTP enforcement specifics, secret redaction/logging behavior, or dependency/CVE posture). The presence of sandbox modes suggests an intended isolation layer, but operational misconfiguration remains a risk.
⚡ Reliability
Best When
You want a configurable agent orchestration framework that can manage multi-step work, tool usage, and isolated execution environments, and you can handle model/provider credentials securely.
Avoid When
You cannot control or constrain sandbox/tool access, or you require highly deterministic, low-latency interactions with minimal operational complexity.
Use Cases
- • Long-horizon agentic workflows (research, planning, coding) with sub-agents
- • Sandboxed tool execution (local, Docker, or Kubernetes) for safer runs
- • Integrating external capabilities via MCP servers/skills
- • Running agent entrypoints through IM channels (Telegram/Slack/Feishu)
- • Providing long-term memory with loadable/reviewable memory fixtures
Not For
- • Applications needing a simple single-purpose API wrapper
- • Environments requiring strict, documented operational SLAs without additional engineering
- • Use without careful security review when enabling external tool/sandbox integrations
Interface
Authentication
Auth mechanisms are configuration-driven. For MCP servers, README states OAuth token flows are supported for HTTP/SSE. For IM channels, tokens/credentials are configured in config.yaml/.env. No fine-grained scope granularity is described for DeerFlow’s own auth in the provided excerpt.
Pricing
Open-source project; costs depend on chosen model provider APIs and any optional external services (e.g., InfoQuest, tracing providers).
Agent Metadata
Known Gotchas
- ⚠ Sandbox execution mode selection (local vs Docker vs Kubernetes) affects isolation/security and operational behavior
- ⚠ Token-cap differences across provider adapters (e.g., Codex Responses endpoint rejecting certain token caps) may require configuration adjustments
- ⚠ Some CLI integrations require explicit credential export/handoff (e.g., Claude Code on macOS) and may not auto-detect Keychain
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for deer-flow.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-29.