13 comments

[ 3.3 ms ] story [ 40.2 ms ] thread
Hi HN, I’m Guohao Li, founder of CAMEL-AI.org and Eigent.AI.

We’ve just launched Eigent, a fully open source desktop application for building and managing multi-agent AI workflows, either locally or in the cloud.

Eigent is built on top of the CAMEL-AI framework and designed specifically for developers, researchers, and teams who want increased control, privacy, and flexibility in their AI operations.

Key features include:

- Multi-agent workflows with parallel execution - Integration of 200+ Model Context Protocol (MCP) tools or custom integrations - Local deployment and “Bring Your Own Key” support for custom models - Optional human-in-the-loop interaction - Complete data ownership and privacy: data remains local unless explicitly shared

If you're interested in multi-agent systems, workflow automation, or maintaining full control over your AI agent infrastructure, we’d love your feedback.

→ GitHub: https://github.com/eigent-ai/eigent

→ Website: https://www.eigent.ai

I’m here and happy to discuss the technical details, architecture, or any questions you might have.

Just tried it yesterday, too good to be open sourced.

Congrats on the launch!!

(comment deleted)
CAMEL-AI has always been my best known open-source community.Its really good to see you guys doing such a great progress. Btw congrats on the launch.
I think i saw it on X, what's the tech stack behind it??
(comment deleted)
(comment deleted)
While playing Minecraft (and coincidentally finding the perfect NVMe SSD for my ASRock B450M/ac motherboard), I started wondering — how does Eigent manage shared memory/state consistency between agents on the same local desktop?
So what makes it any different compared to Manus or Crewai?
No other reasoning model other than Gemini-2.5 Pro? The pricing tiers on the website list only 3 models, one being Gemini and other 2 being GPT-4 artifacts, Perhaps, one can highlight there that one can bring their own API key?, if thats the case. Also, does it support Clade-Opus 4?
How many agent workers of each type is gonna be spun for any task? How do you come up with an optimal number for a task when the more workers there are, the higher the token usage would be, making it more expensive?