Item detail
github.com

bytedance/deer-flow

bytedance/deer-flow is an agent project in RepoRadar's Radar section, holding Gold tier and a 'try now' verdict. Its strongest signal is workflow potential, scored 10.0 out of 10.

Score8.6
Popularity8.7
Risklow
TierGold
Score breakdown
Usefulness8.0
Novelty8.0
Momentum9.0
Maturity6.9
Open-source/build8.4
Evidence7.2
Workflow potential10.0
Setup ease6.4

Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.

Why it matters

Useful for AI builders, research teams, and developers who want a self-hostable, long-horizon agent harness that can chain research, coding, and creative work in a single sandboxed run, instead of stitching together a hand-rolled multi-agent loop on top of an LLM API.

Who should use it

AI builders who want a long-horizon agent harness instead of a single-turn task runner research teams who want a self-hostable SuperAgent that can chain research, coding, and creative work developers who need sandboxed execution and persistent memory for multi-day agent workflows open-source contributors who want a well-maintained MIT-licensed alternative to closed-source agent SaaS

Who should skip it

Skip bytedance/deer-flow unless the captured evidence suggests it solves a problem you are actively working on.

About this signal

bytedance/deer-flow is tracked by RepoRadar as an agent project in the Radar section. First seen 2026-06-21; the source record was last checked on 2026-06-21. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. bytedance/deer-flow leads on workflow potential (10.0) and momentum (9.0); its lowest signal is setup ease (6.4), so factor that in before investing setup time. This page summarizes the public evidence on the linked source page and states where additional review is still needed.

How this item is evaluated

The bytedance/deer-flow record combines a 8.6/10 composite score with separate popularity (8.7), risk (low), and setup (moderate) signals. See the scoring methodology for the current weights and evidence definitions.

Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.

Risk explanation

It runs sandboxed code on your behalf and is intended to back long-horizon agent workflows, so scope the sandbox permissions, audit what gets persisted in agent memory, and confirm sensitive intermediate files are wiped between runs before promotion.

Evidence links
Closest alternatives / related signals
agent superagent long-horizon orchestration sandbox memory open-source bytedance
Verification record

What RepoRadar actually verified

Discovered

Automated discovery and source capture. Last checked 2026-08-13T20:20:15Z.

No editorial or hands-on review is claimed. This record remains at Discovered.

Verification sources

Longitudinal intelligence

How this decision record is moving

Raw history JSON →

44 dated snapshots retained from 2026-06-21 through 2026-08-13; see the snapshot index for explicit coverage gaps. Stars, version, release, pricing, integration, risk, maintenance, verdict, score, and momentum fields remain explicit even when a source has not reported them. Repository momentum is a normalized 0–10 RepoRadar signal; GitHub stars appear only where the popularity monitor retained exact timestamped observations.

RepoRadar score8.6 current · +0.0 net
Repository momentum9.6 current · +0.6 net
GitHub stars (observed)79,941 current · +3,027 net
GitHub stars79,941 exact observation
Versionv2.0.0
Last release2026-06-25T16:23:22Z
Maintenanceactive
Current risklow
Current verdicttry now
Pricing baselineNo structured commercial pricing baseline
Pricing checkedNot applicable or not recorded
Pricing freshnessNo dated commercial pricing review
Integrations baselineLangChain

Recent dated points

DateScoreMomentumStarsRiskVerdictMaintenance
2026-08-138.69.679,941lowtry nowactive
2026-08-128.69.679,846lowtry nowactive
2026-08-118.69.679,726lowtry nowactive
2026-08-108.69.679,654lowtry nowactive
2026-08-098.69.679,588lowtry nowactive
2026-08-088.69.679,553lowtry nowactive
2026-08-078.610.079,084lowtry nowactive
2026-08-068.69.0Not recordedlowtry nownot recorded
2026-08-058.69.0Not recordedlowtry nownot recorded
2026-08-048.610.079,084lowtry nowactive
2026-08-038.610.079,084lowtry nowactive
2026-08-028.610.078,884lowtry nowactive

Why the record changed

stars changed

Stars changed: 79846 → 79941.

stars changed

Stars changed: 79726 → 79846.

stars changed

Stars changed: 79654 → 79726.

stars changed

Stars changed: 79588 → 79654.

stars changed

Stars changed: 79553 → 79588.

stars changed

Stars changed: 79084 → 79553.

stars changed

Stars changed: 78884 → 79084.

stars changed

Stars changed: 78517 → 78884.

stars changed

Source-observed stars changed: 78449 → 78517. This reports the retained observation delta and does not infer why the upstream change occurred.

stars changed

Source-observed stars changed: 78442 → 78449. This reports the retained observation delta and does not infer why the upstream change occurred.

stars changed

Source-observed stars changed: 78439 → 78442. This reports the retained observation delta and does not infer why the upstream change occurred.

stars changed

Source-observed stars changed: 78437 → 78439. This reports the retained observation delta and does not infer why the upstream change occurred.