StackMap
Subscribe
Explore / eko
FellouAI

eko

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.

4,949 441 TypeScript MITupdated 5 months ago
agentsorchestration
View on GitHubDispute this mapping →
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.

Mapped by ShipWithAI editors · links verified
README.md

eko-logo
Eko - Build Production-ready Agentic Workflow with Natural Language

License Build Status Version

Eko (pronounced like 'echo') is a production-ready JavaScript framework that enables developers to create reliable agents, from simple commands to complex workflows. It provides a unified interface for running agents in both computer and browser environments.

News

  • 2025-11: Eko 4.0 supports chat conversations & optimizes agent logic.
  • 2025-09: Eko 3.0 introduces dependency-aware parallel agent execution.
  • 2025-09: New pause, resume, and interrupt controls with task_snapshot workflow recovery.
  • 2025-09: Monorepo tooling migrated to pnpm for consistent workspace management.

Upgrading to Eko 4.0

Follow these steps when moving an existing Eko 3.x project to 4.0:

  1. Update dependencies with pnpm up @eko-ai/eko @eko-ai/eko-nodejs @eko-ai/eko-web @eko-ai/eko-extension.
  2. Regenerate saved workflows or exported plans so they use the v3 schema and dependency graph format.
  3. Clean and reinstall using pnpm (rm -rf node_modules && pnpm install), then rebuild any browser or desktop bundles.
  4. Re-run automated demos and update documentation to reflect the new pause/interrupt APIs and parallel agent behavior.

Framework Comparison

Feature Eko Langchain Browser-use Dify.ai Coze
Supported Platform All platform Server side Browser Web Web
One sentence to multi-step workflow ✅ ❌ ✅ ❌ ❌
Intervenability ✅ ✅ ❌ ❌ ❌
Task Parallel ✅ ❌ ❌ ❌ ❌
Development Efficiency High Low Middle Middle Low
Task Complexity High High Low Middle Middle
Open-source ✅ ✅ ✅ ✅ ❌
Access to private web resources ✅ ❌ ❌ ❌ ❌

Features

  • Pure JavaScript: Built for browsers and Node.js.🚀
  • Multi-Agent: Unleash power with multiple Agents in one task.📈
  • Agent/Tool Flexibility: Customize new Agents and Tools in just one line.🎉
  • Native MCP: Connects seamlessly with Awesome MCP Servers.🔗
  • Dynamic LLM: Balance speed and performance with flexible model choices.⚙️
  • Human-in-the-loop: Intervene when it matters most.🤝
  • Stream Planning: Dynamic rendering made easy.🎨
  • Loop & Listener Tasks: Automate any repetitive task.🤖
  • Observable Chain: Coming soon
  • Native A2A: Coming soon

Quickstart

Note: Please refer to the Eko Quickstart guide guide for full instructions on how to run it.

Security Warning

DO NOT use API Keys in browser/frontend code!

This will expose your credentials and may lead to unauthorized usage.

Best Practices: Configure backend API proxy request through baseURL and request headers.

Please refer to the link: https://eko.fellou.ai/docs/getting-started/configuration#web-environment

const llms: LLMs = {
  default:

Continue your stack

What teams reach for next — and why each earns a place beside eko. Ranked by curator confidence.