Skip to content
/

Eigent

eigent · eigent-ai/eigent · ★ 14k · last commit 2026-05-26

Primitive shape 9 total
Subagents 4 MCP tools 5
00

Summary

Eigent — Summary

Eigent is an open-source Electron + React desktop application ("cowork desktop") built on the CAMEL-AI framework. It presents multi-agent workflows as a visual desktop environment where a workforce of specialized agents (Developer, Browser, Document, Multi-Modal) execute tasks in parallel with human-in-the-loop checkpoints. The backend is a Python FastAPI server using CAMEL-AI and Qdrant for vector memory; the frontend is an Electron+Vite+React application with a full workflow visualization UI. Users can deploy locally (fully standalone with local LLMs) or connect to Eigent cloud services.

The project targets the "cowork platform" positioning: instead of a CLI agent that takes instructions, Eigent presents an AI workforce that autonomously breaks down tasks, assigns subtasks to specialist agents, and runs them in parallel. Human-in-the-loop gates pause execution when an agent encounters uncertainty. Compared to claude-flow (closest seed), Eigent's distinguishing feature is the Electron desktop UI as the primary interface — no CLI, no terminal sessions — and the CAMEL-AI Python orchestration layer rather than an MCP toolserver.

01

Overview

Eigent — Overview

Origin

Eigent is built by Eigent AI on top of the CAMEL-AI open-source framework (camel-ai[eigent]==0.2.91a3). CAMEL-AI is a multi-agent AI research framework from a dedicated team. Eigent packages the framework as a consumer desktop product with cloud deployment and enterprise SSO options. 14,121 stars, 30+ contributors as of 2026-05-26.

Philosophy

The README's opening: "Eigent is the open source Cowork desktop application, empowering you to build, manage, and deploy a custom AI workforce that can turn your most complex workflows into automated tasks."

The "cowork" framing positions agents as team members in an organizational structure rather than tools. Pre-defined agent archetypes (Developer, Browser, Document, Multi-Modal) correspond to job functions. The stated goal is "exceptional productivity" through parallelism and specialization.

Key principles from README:

  • "Multi-Agent Workforce that boosts productivity through parallel execution, customization, and privacy protection"
  • "Zero Setup — No technical configuration required" (for cloud-connected mode)
  • "100% Open Source from day one"
  • Human-in-the-Loop: "If a task gets stuck or encounters uncertainty, Eigent will automatically request human input"

Tech Stack Origin

Backend: CAMEL-AI (Python, multi-agent research framework) + FastAPI + Qdrant (vector search) Frontend: Electron + Vite + React (TypeScript)

02

Architecture

Eigent — Architecture

Distribution

  • Type: Electron desktop application (packaged + source)
  • Install (local): git clone + npm install + npm run dev
  • Install (cloud): Download pre-built app from eigent.ai/download
  • Backend: Python FastAPI server bundled with the Electron app (backend/ directory)

Directory Tree

eigent/
├── src/                  # React frontend (Vite + TypeScript)
│   ├── App.tsx
│   ├── pages/            # UI pages/views
│   ├── components/
│   ├── api/              # API client
│   └── store/            # Zustand state
├── backend/              # Python FastAPI backend
│   ├── app/              # CAMEL-AI agent logic
│   ├── cli.py            # CLI entry point
│   ├── main.py           # FastAPI main
│   └── pyproject.toml    # Python deps (CAMEL-AI, Qdrant, FastAPI)
├── electron/             # Electron main process
├── electron-builder.json # Desktop packaging config
├── vite.config.ts
└── package.json          # Frontend deps

Required Runtime

  • Node.js 18-22 (for frontend/Electron)
  • Python >=3.11, <3.12 (for backend)
  • uv (Python package manager) for backend deps
  • Optional: Ollama/vLLM/LM Studio (for local LLMs)
  • Qdrant (for vector memory, bundled or external)

Target AI Tools

Eigent controls its own agent workforce — it does NOT wrap Claude Code or Codex. Instead it uses LLM APIs (OpenAI, Anthropic, local models via CAMEL-AI) to power its own agent runtime. The agent "Developer" can execute terminal commands (code execution).

Key Dependencies

  • camel-ai[eigent]==0.2.91a3 — multi-agent orchestration
  • fastapi — backend API
  • qdrant-client — vector search memory
  • Electron + React + Vite — desktop UI
  • OpenTelemetry — observability
03

Components

Eigent — Components

Pre-Defined Agent Workers (Subagents)

Agent Purpose
Developer Agent Writes and executes code, runs terminal commands
Browser Agent Searches the web and extracts content
Document Agent Creates and manages documents
Multi-Modal Agent Processes images and audio

These are defined as CAMEL-AI agent classes in the Python backend.

Backend Modules (from backend/app/)

Module Purpose
CAMEL-AI workforce orchestrator Dynamically breaks down tasks, assigns subtasks to workers
FastAPI REST API Bridge between Electron frontend and Python orchestration
Qdrant vector store Semantic memory for agent context retrieval
OpenTelemetry instrumentation Tracing and observability

Frontend Pages (from src/pages/)

Page Purpose
Workforce view Visualize parallel agent execution
Task input Define and submit tasks
Agent monitor Watch individual agent progress
Settings Model selection, API keys

Built-in MCP Tools

Eigent's README advertises "massive built-in MCP tools" including web browsing, code execution, Notion, Google Suite, Slack, plus user-installable custom tools. The MCP tool count is not enumerable from the source tree directly.

CLI (backend)

python backend/cli.py — Python CLI for the backend service (not a user-facing command line tool; primarily for dev/testing).

05

Prompts

Eigent — Prompts

Eigent's prompt files are part of the CAMEL-AI Python backend. Direct access to backend/app/ agent definitions is via the repo. No SKILL.md or Claude Code skill files are present.

Verbatim excerpt 1 — Developer Agent description (from README)

Developer Agent: Writes and executes code, runs terminal commands.

Prompting technique: Role-based persona definition. The agent name maps to a persona with bounded responsibilities. This is the BMAD-style persona pattern, implemented as a Python/CAMEL-AI class rather than a Markdown file.

Verbatim excerpt 2 — CAMEL-AI Workforce framing (from README)

Employs a team of specialized AI agents that collaborate to solve complex tasks.
Eigent's open-source Cowork dynamically breaks down tasks and activates multiple
agents to work in parallel.

Prompting technique: Task decomposition via workforce orchestrator. The LLM orchestrator receives the full task and is prompted to produce a subtask tree, then dispatch subtasks to workers by role. This is a programmatic prompt-chaining pattern where the orchestrator's output directly becomes worker inputs.

Verbatim excerpt 3 — Human-in-the-Loop trigger (from README)

If a task gets stuck or encounters uncertainty, Eigent will automatically request human input.

Prompting technique: Uncertainty-triggered gate. The worker agents are prompted to explicitly signal uncertainty (rather than hallucinating solutions), which causes the orchestrator to pause execution. This is a fail-safe prompting pattern encouraging agents to prefer asking over guessing.

09

Uniqueness

Eigent — Uniqueness & Positioning

differs_from_seeds

Eigent is architecturally closest to claude-flow (both implement hierarchical multi-agent workforce orchestration with specialist roles) but differs in three key dimensions: (1) Eigent is a full Electron desktop application while claude-flow has no UI at all; (2) Eigent's orchestration layer is CAMEL-AI Python code-classes while claude-flow uses an MCP toolserver with 305 discrete tools; (3) Eigent is model-agnostic (local LLMs, OpenAI, Anthropic, any CAMEL-compatible provider) while claude-flow targets claude-code as primary tool. No other seed in the corpus ships a consumer-grade Electron desktop application as the primary interface. The closest is kiro (a VS Code fork with IDE-native primitives) but kiro is a development environment, not an agent workforce dashboard. Eigent's "zero setup, download and run" positioning contrasts with all seeds which require CLI installation.

Positioning

  • Compared to claude-flow: Same goal, opposite implementation approach (Electron GUI vs CLI/MCP).
  • Compared to BMAD-METHOD: BMAD defines personas and phases in Markdown; Eigent defines specialist agents as Python classes with real tool execution.
  • Compared to superpowers: superpowers enhances a human's Claude Code session; Eigent replaces the human coding loop with an autonomous workforce.
  • Enterprise tier: Eigent offers SSO + enterprise support, unique in this batch.

Observable Failure Modes

  1. Python version lock: Requires exactly Python >=3.11, <3.12 — other versions may fail silently.
  2. CAMEL-AI coupling: Version pinned to camel-ai[eigent]==0.2.91a3; breaking changes in CAMEL-AI affect Eigent without upgrade path.
  3. Local LLM quality: "Zero setup" local deployment depends on locally available model quality; weak local models produce poor task decomposition.
  4. GUI-only: No headless/CLI mode for server deployments or automation pipelines.
  5. Cloud dependency: Cloud-connected quick start requires account registration; privacy-conscious users must use the more complex local deployment path.
04

Workflow

Eigent — Workflow

Phase Flow

Phase Description Artifact
1. Task Definition User describes goal in the desktop UI Task specification
2. Task Decomposition CAMEL-AI orchestrator breaks task into subtasks Subtask tree
3. Agent Assignment Orchestrator assigns subtasks to specialist workers (Developer, Browser, Document, Multi-Modal) Assignment manifest
4. Parallel Execution Workers execute in parallel Results
5. Human-in-the-Loop Gate If a worker gets stuck or encounters uncertainty, execution pauses and requests human input Human approval
6. Result Synthesis Workers' outputs are aggregated Final result

Approval Gates

  • Human-in-the-Loop: Automatic pause when uncertainty detected. Worker explicitly signals it needs input; the desktop UI surfaces the question to the human.

Execution Details

  • Parallelism is built into CAMEL-AI's workforce module
  • Each worker is an independent agent with its own system prompt and tool access
  • The orchestrator maintains the task decomposition tree and routes subtask results back
06

Memory Context

Eigent — Memory & Context

Memory Type

Vector DB (Qdrant). The backend uses qdrant-client for semantic search over agent memories.

Memory Persistence

Global / project — Qdrant stores vector embeddings that persist across sessions.

State Files

  • Qdrant collections (external service or local Docker)
  • Backend SQLite or file-based state (inferred from CAMEL-AI defaults)

Cross-Session Handoff

Not explicitly documented. Qdrant persistence means relevant context can be retrieved by semantic query in a new session.

Context Compaction

Not explicitly addressed. CAMEL-AI's workforce manages context windows per-agent.

Streaming

FastAPI streams results to the Electron frontend via REST/WebSocket. The README shows animated GIFs of real-time agent execution progress in the UI.

07

Orchestration

Eigent — Orchestration

Multi-Agent Pattern

Parallel fan-out with hierarchical task decomposition. The CAMEL-AI orchestrator receives a task, decomposes it into subtasks, and dispatches subtasks to specialist workers in parallel. Workers report results back to the orchestrator.

Subagent Definition Format

code-class. Workers are Python classes in the CAMEL-AI framework (Developer, Browser, Document, Multi-Modal agents defined as class instances).

Execution Mode

Interactive-loop. User submits a task in the desktop UI; the orchestrator runs until completion or human-in-the-loop pause; user reviews and resumes.

Multi-Model

Yes — CAMEL-AI supports routing different tasks to different models. The backend pyproject.toml includes openai>=1.99.3 and CAMEL-AI supports Anthropic, OpenAI, and local models (Ollama, vLLM, LM Studio). Each worker agent can be configured with a different model class.

Isolation

None (process-level only). Workers share the Python process; no git-branch or container isolation.

MCP Integration

The README advertises built-in MCP tools (browser, code execution, Notion, Google Suite, Slack) plus user-installable custom tools. MCP tools augment agent capabilities rather than constituting the orchestration layer itself.

Consensus

None. Orchestrator is the authority on task routing; no Byzantine or quorum mechanisms.

Max Concurrent Agents

Not specified. Limited by CAMEL-AI thread model and LLM rate limits.

08

Ui Cli Surface

Eigent — UI / CLI Surface

CLI Binary

  • Exists: Marginal — python backend/cli.py is a developer-facing backend launcher, not a user CLI
  • Binary name: none (no user-facing CLI binary)
  • Is thin wrapper: N/A

Local UI Surface

Desktop App (Primary)

  • Type: Electron desktop application
  • Distribution: Pre-built binaries from eigent.ai/download (macOS, Windows, Linux planned)
  • Tech stack: Electron + Vite + React (TypeScript) frontend; Python FastAPI backend bundled in Electron
  • Port: Backend runs on local port (not specified in README; typical FastAPI default 8000)

Features (from README + GIFs)

  • Workforce view: Visual display of active agents and task progress in parallel
  • Task input: Describe a task in natural language; submit to workforce
  • Agent activity monitor: Real-time status of each worker (what tool it's using, current step)
  • Human-in-the-Loop dialog: Pauses execution and presents question to user
  • Model selection: Switch between local models (Ollama, vLLM) or cloud providers
  • MCP tool manager: Add/remove MCP tools for agents
  • Settings: API key management, model configuration

IDE Integration

None. Eigent is a standalone desktop application.

Observability

  • OpenTelemetry: Backend is instrumented with OTel for tracing
  • Agent activity GIFs: The README shows real-time animated execution visualizations in the UI
  • No audit log: Not explicitly documented

Comparison with CLAUDE-FLOW UI

Claude-flow has no local UI — all interaction is via Claude Code terminal commands. Eigent inverts this entirely: it is a full Electron desktop application with a visual workforce dashboard. The CAMEL-AI orchestration layer is equivalent in function to claude-flow's MCP toolserver (both decompose tasks and dispatch to workers) but Eigent's interaction model is GUI-first while claude-flow's is CLI-first. Eigent also supports local LLM deployment whereas claude-flow targets cloud APIs exclusively.

Related frameworks

same archetype · same primary tool · same memory type

Goose (Block/AAIF) ★ 46k

General-purpose AI agent (not just code) with security-first tool inspection, recipe-based shareable configurations, and 15+ LLM…

Vibe Kanban ★ 27k

Eliminate the overhead of planning, switching between agent terminals, and reviewing diffs by providing a single web dashboard…

1Code ★ 5.5k

Cursor-like desktop experience for Claude Code and Codex with cloud background agents, event-driven automations, and a full…

Crystal (stravu) ★ 3.1k

Manage multiple parallel AI coding sessions in isolated git worktrees from a single desktop GUI.

Maestro (RunMaestro) ★ 3.0k

Orchestrate unlimited parallel AI agent sessions with a keyboard-first desktop app including Group Chat coordination and Auto Run…

AgentsMesh ★ 2.1k

Multi-tenant workforce platform that gives every team member a squad of AI coding agents coordinated through channels, pod…