FellouAI / eko
Eko (Eko Keeps Operating) - Build Production-ready Agentic Workflow with Natural Language - eko.fellou.ai
AI Architecture Analysis
This repository is indexed by RepoMind. By analyzing FellouAI/eko in our AI interface, you can instantly generate complete architecture diagrams, visualize control flows, and perform automated security audits across the entire codebase.
Our Agentic Context Augmented Generation (Agentic CAG) engine loads full source files into context on-demand, avoiding the fragmentation of traditional RAG systems. Ask questions about the architecture, dependencies, or specific features to see it in action.
Repository Overview (README excerpt)
Crawler viewEko - Build Production-ready Agentic Workflow with Natural Language 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 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: • Update dependencies with . • Regenerate saved workflows or exported plans so they use the v3 schema and dependency graph format. • Clean and reinstall using pnpm ( ), then rebuild any browser or desktop bundles. • 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 | Middle | | **Open-source** | ✅ | ✅ | ✅ | ✅ | ❌ | | **Access to private web resources** | ✅ | ❌ | ❌ | ❌ | ❌ | Features • [x] Pure JavaScript: Built for browsers and Node.js.🚀 • [x] Multi-Agent: Unleash power with multiple Agents in one task.📈 • [x] Agent/Tool Flexibility: Customize new Agents and Tools in just one line.🎉 • [x] Native MCP: Connects seamlessly with Awesome MCP Servers.🔗 • [x] Dynamic LLM: Balance speed and performance with flexible model choices.⚙️ • [x] Human-in-the-loop: Intervene when it matters most.🤝 • [x] Stream Planning: Dynamic rendering made easy.🎨 • [x] 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 Example Projects The repository ships with three workspace examples under the folder. Prerequisites Before running any example, install dependencies and build the core packages from the root directory: Browser Extension ( ) Load the generated directory via → Developer Mode → Load unpacked. Configure your API key in the extension options before running the automation task. Node.js Automation ( ) The Node.js demo drives Playwright through Eko; provide at least one model API key before running it. Web Login Demo ( ) This starts a React dev server on the default port with a simple login flow that you can automate with the browser or web agents. Use Cases • Browser automation and web scraping • System file and process management • Workflow automation • Data processing and organization • GUI automation • Multi-step task orchestration Documentation Visit our documentation site for: • Getting started guide • API reference • Usage examples • Best practices • Configuration options Development Environments Eko can be used in multiple environments: • Browser Extension • Web Applications • Node.js Applications Community and Support • Report issues on GitHub Issues License Eko is released under the MIT License. See the LICENSE file for details.