Who Maintains the Deer-Flow Project? ByteDance Engineering Team and Core Contributors

The deer-flow project is actively maintained by the ByteDance engineering team, led by principal contributors Daniel Walnut and Henry Li, who oversee the multi-agent framework's development across the main 2.0 branch and legacy 1.x branch.

Deer-flow is an open-source, multi-agent research-automation framework developed by ByteDance. Understanding who maintains deer-flow is essential for contributors and enterprise adopters seeking to engage with the project roadmap, security policies, and release cycles. The maintenance structure reflects a hybrid model combining corporate oversight with individual contributor leadership.

ByteDance Engineering Team Oversight

The deer-flow repository operates under the ByteDance organization, with the engineering team providing institutional resources for infrastructure, security review, and release management. As documented in the repository root, the project follows enterprise-grade maintenance standards including continuous integration pipelines and formal security disclosure processes.

According to the source code in README.md (lines 71-74), the project lists explicit "Key Contributors" who serve as the primary points of contact for technical direction and community governance.

Principal Contributors and Roles

The day-to-day maintenance of deer-flow centers on two individuals responsible for architectural decisions, pull request reviews, and version releases.

Daniel Walnut – Lead Architect and Primary Maintainer

Daniel Walnut serves as the lead architect and primary maintainer of deer-flow. He directs the project's technical roadmap, including the major "2.0" rewrite that modernized the framework's core architecture. Walnut's GitHub profile (hetaoBackend) is referenced in the contributor documentation as the principal authority for merging significant changes and coordinating release cycles.

Henry Li – Co-Maintainer and Major Contributor

Henry Li operates as the co-maintainer and major contributor, complementing Walnut's architectural leadership with feature development and community coordination. Li's GitHub handle (magiccube) appears alongside Walnut's in the "Key Contributors" section of README.md, indicating equal responsibility for repository governance and long-term project sustainability.

Branch Maintenance Strategy

The deer-flow maintainers manage two concurrent branches to support both legacy users and modern deployments:

• Main branch: Contains the "2.0" rewrite with breaking architectural changes and new multi-agent capabilities
• 1.x branch: Preserves legacy code for existing production deployments requiring stability

This dual-branch strategy is explicitly acknowledged in SECURITY.md, which states the project has "two branches to maintain," requiring the maintainers to backport security fixes and coordinate releases across both codebases. The 1.x branch reference appears in README.md lines 10-12, documenting the legacy support commitment.

How to Identify Maintainers Programmatically

You can extract current maintainer information directly from the repository's README.md without manual inspection. The following Python script parses the "Key Contributors" section using regular expressions:

import re, pathlib, json

def get_maintainers(readme_path: str = "README.md"):
    text = pathlib.Path(readme_path).read_text(encoding="utf-8")
    # Look for the "Key Contributors" section

    m = re.search(r"### Key Contributors(.*?)---", text, re.S)

    if not m:
        return []
    block = m.group(1)
    # Extract markdown links of the form [Name](url)

    return re.findall(r"\*\*\[(.+?)\]\((.+?)\)\*\*", block)

print(json.dumps(get_maintainers(), indent=2))

When executed against the deer-flow source tree, this script returns the structured maintainer data:

[
  {
    "name": "Daniel Walnut",
    "url": "https://github.com/hetaoBackend/"
  },
  {
    "name": "Henry Li",
    "url": "https://github.com/magiccube/"
  }
]

This approach ensures automated tooling can always access the definitive list of deer-flow maintainers as encoded in the repository's own documentation.

Key Files for Maintenance Information

Several critical files in the repository define the maintenance structure and responsibilities:

• README.md – Contains the "Key Contributors" section (lines 71-74) listing Daniel Walnut and Henry Li as primary maintainers, plus references to the legacy 1.x branch (lines 10-12)
• SECURITY.md – Confirms the dual-branch maintenance obligation, stating the project maintains security updates across both the 2.0 and 1.x branches
• backend/README.md – Provides backend-specific contribution guidelines followed by the maintainer team for code review standards
• .github/workflows/backend-unit-tests.yml – CI workflow overseen by the maintainers to enforce quality gates on all contributions

These files collectively document the governance model and technical standards enforced by the deer-flow maintenance team.

Summary

• Daniel Walnut (GitHub: hetaoBackend) serves as lead architect and primary deer-flow maintainer, directing the 2.0 rewrite
• Henry Li (GitHub: magiccube) operates as co-maintainer, managing feature development and community contributions
• The ByteDance engineering team provides institutional oversight, infrastructure, and release management resources
• Maintainers support two active branches: the main 2.0 branch and the legacy 1.x branch for backward compatibility
• Maintainer identities are programmatically accessible from the README.md "Key Contributors" section

Frequently Asked Questions

Who is the lead maintainer of deer-flow?

Daniel Walnut is the lead architect and primary maintainer of the deer-flow project. According to the repository's README.md (lines 71-74), Walnut directs the framework's technical roadmap and oversees the major 2.0 architectural rewrite under the ByteDance engineering organization.

Does deer-flow have multiple maintainers?

Yes, deer-flow operates with a dual-maintainer structure. Daniel Walnut serves as the primary maintainer while Henry Li acts as co-maintainer and major contributor. This partnership ensures continuous coverage for pull request reviews, security updates, and community support across the project's two active branches.

What branches do the deer-flow maintainers support?

The maintainers actively support two branches: the main branch containing the modern 2.0 rewrite and the 1.x branch preserving legacy code. As documented in SECURITY.md, this dual-branch strategy requires the maintainers to manage security patches and stability updates for both legacy users and modern deployments.

How can I contact the deer-flow maintainers?

You can identify the current maintainers by examining the "Key Contributors" section in README.md at the repository root, which lists Daniel Walnut and Henry Li with their respective GitHub profiles (hetaoBackend and magiccube). For security issues, follow the disclosure process outlined in SECURITY.md, which routes directly to the ByteDance engineering team's maintenance infrastructure.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}