deer-workflow vs eko
Graph-engineering runtime where TypeScript owns control flow and replaceable coding-agent CLIs — Codex, Claude Code, Pi — do the semantic work inside each node. Pilot for DeerFlow 3.0. — versus — Production JavaScript framework for agentic workflows: one sentence becomes a dependency-aware multi-agent plan that runs in browser, Node, or extension — with pause/resume and snapshot recovery.
Both turn one sentence into a runnable multi-agent plan in TypeScript. Eko builds the dependency graph at runtime and executes it in browser, Node or extension with pause/resume; deer-workflow emits the graph as a source file you review and commit first. Runtime planning vs auditable artifact.
| deer-workflow | eko | |
|---|---|---|
| Stars | 487 | 5.0k |
| Forks | 52 | 442 |
| Language | TypeScript | TypeScript |
| License | MIT | MIT |
| Last activity | 15 days ago | 5 months ago |
| Topics | orchestration, coding | agents, orchestration |
| Curated connections | 3 | 3 |
deer-workflow — the curator's take
Pick it when the orchestration itself has to be reviewable: phases, inputs, retries and failure handling live in TypeScript you diff in a PR, not in a prompt that hopes the agent remembers the plan. The generator is the hook — `deer-workflow create "<description>"` has Codex apply the bundled workflow-creator skill and prints a runnable module you then edit as normal code, and `--print` streams one JSON event per line so CI can consume a run. Caveats worth knowing before adopting: Bun-only, requires an installed and signed-in agent CLI, ships two examples, and is explicitly a pilot for ByteDance's DeerFlow 3.0 — expect the API to move.
eko — the curator's take
The JS-native, runs-anywhere bet is the differentiator: the same workflow executes in a browser extension, a web page or a server, which no Python framework offers — and 4.0's pause/interrupt/snapshot controls are production concerns most frameworks defer. When NOT: the deep ecosystem (integrations, community patterns, papers) still lives in Python — teams already on LangGraph gain little; and Fellou the company steers the roadmap, so watch for platform gravity.