agentdock vs eko
TypeScript library giving a backend one agent runtime: session-scoped runs with streaming, approvals and cancel, a tool registry, injectable stores and a factory over nine AI SDK providers. — 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 are TypeScript-first agent frameworks you embed in a Node backend. Eko adds a planner and dependency-aware multi-agent workflows across browser and Node; AgentDock stops at a single run loop with a tool registry and leaves orchestration to your app.
| agentdock | eko | |
|---|---|---|
| Stars | 6 | 5.0k |
| Forks | 2 | 442 |
| Language | TypeScript | TypeScript |
| License | MIT | MIT |
| Last activity | 3 days ago | 6 months ago |
| Topics | agents | agents, orchestration |
| Curated connections | 5 | 5 |
agentdock — the curator's take
A deliberately thin agent loop for Node backends. The one decision worth copying is that sessions own their message history through an injected store, so a multi-tenant app stops threading transcripts through every call site. Set expectations accordingly: v0.1.0, single-digit stars, in-memory defaults, and it is a wrapper over the Vercel AI SDK, so anything the SDK cannot do it cannot do either. Use it if you want a runtime small enough to read end to end; use a real harness if you want planning, sub-agents, sandboxes or memory.
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.