CamelAGI
Self-hosted AI agent framework controlled via Telegram, supporting multi-agent management with Claude models and tool execution.
27 linking domains
Emerging
- For
- Developers building personal AI agents with Claude, self-hosted and controlled via Telegram.
- Price
- Price not read
- Activity
- Activity not read yet
- Company
- founding year not on record
- Runs as
- Self-hostedCLI
- Create and manage multiple AI agents from Telegram commands
- Run Claude code on local machines controlled remotely from phone
- Schedule automated AI tasks with cron jobs and daily summaries
- #4
PostHog
Ingests product data and runs AI agents to investigate issues and recommend product improvements.
24.7knot readFree plan2020 - #15
Kiro
Converts prompts into executable specifications and implements code with parallel agents that validate correctness.
32.7kActiveFrom $20/user/mo - #20
Devin
Executes software engineering tasks including code migrations, bug fixes, testing, and documentation generation across multiple repositories.
30.6kActiveFrom $20/mo - #23
TestMu AI (Formerly LambdaTest)
Runs automated tests on web and mobile applications using AI agents across browsers, devices, and environments at scale.
370kActiveFrom $17/mo2017 - #28
Replit
Builds and deploys web apps, websites, and agents from natural language descriptions.
278knot readFrom $20/mo - #33
V0 Dev
Deploys and runs applications and AI agents on serverless infrastructure with sandboxed environments and model gateways.
141knot readFrom $20/mo2015
What is CamelAGI?
Self-hosted AI agent framework controlled via Telegram, supporting multi-agent management with Claude models and tool execution.
Who is CamelAGI for?
Developers building personal AI agents with Claude, self-hosted and controlled via Telegram.
Do people use CamelAGI?
Emerging.
What are alternatives to CamelAGI?
In Developer tools, by use: PostHog, Kiro, Devin, TestMu AI (Formerly LambdaTest), Replit, V0 Dev.
How we read a tool
No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.
- Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
- Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
- Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
- The line and the use cases are written by us from the homepage, one row at a time, and refused when they repeat the vendor's marketing.
How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.