Report · Issue 01
The State of AI Agents
What the agent ecosystem actually looks like when you count it — measured across 247 hand-curated tools, not scraped from a trending page. Who is building in the open, which languages own which territory, where the crowd is, and what is moving now.
The short version
The agent ecosystem is still overwhelmingly a public-repo ecosystem: 86% of the 247 tools we track are open source, and commercial products are a thin 14% layer on top. Python leads TypeScript 1.8:1 overall — but that headline hides the real story, which is territorial: TypeScript already owns the categories where the thing being automated is itself a web app. The most crowded arena is Coding Agents, at 37 tools, while the two categories closest to a paying customer — support and sales — hold just 9 open records between them.
247
Hand-curated, deduplicated, one record per tool.
86%
212 public repos · 35 commercial.
1.8:1
103 Python · 57 TypeScript projects.
3.43M
70% of repos pushed in the last 30 days.
What the numbers say
- 01
The ecosystem is 86% open source — the centre of gravity is still the repo, not the SaaS product.
212 of 247 tools ship as open source; only 17 are paid products and 18 freemium. For a category with this much venture attention, that ratio is unusual — and it means the practical constraint on adopting an agent stack is rarely licensing.
- 02
Python leads TypeScript 1.8:1 — but the split is territorial, not global.
Across 209 open-source projects that declare a primary language, Python takes 103 and TypeScript 57. Yet TypeScript is ahead in Coding Agents, Workflow & Productivity, Agent Infrastructure — the categories whose subject matter is itself JavaScript: editors, browsers, web workflows. MCP servers are split exactly evenly (10 each), which is what a genuinely new, still-unclaimed category looks like.
- 03
The most crowded category is Coding Agents — 37 tools.
Then Agent Frameworks (31), Voice Agents (29), MCP Servers (28). Crowding is not the same as maturity: it marks where the problem is legible enough that everyone attempts it, which is also where differentiation is hardest to find.
- 04
The most fragmented arena is Voice Agents — 29 tools and no dominant project.
Its most-starred entry, xiaozhi-esp32-server, has 10k stars — against 199k for n8n in Workflow & Productivity. When a category is busy but flat, nobody has found the shape of the answer yet; expect consolidation rather than a new entrant.
- 05
Customer-facing agents are where open source is thinnest — 9 records across support and sales.
These are the categories closest to a budget line, and they are the ones commercial vendors hold. The pattern repeats across the corpus: the further you get from a developer’s own machine, the more the open ecosystem thins out.
- 06
Momentum is concentrated in coding and web-data tools — jcode added 3,620 stars in 7 days.
Over the 27 July – 3 August 2026 refresh window, the fastest-growing records were jcode, firecrawl, deer-flow, n8n. Two sub-areas keep producing the movers: agents that write code, and the tooling that feeds agents the web.
Figure 1
Open source vs commercial
Every tracked tool by licensing posture. Open source dominates at 86%, and the commercial layer splits almost evenly between freemium and paid.
- 212 Open source (86%)
- 18 Freemium (7%)
- 17 Paid (7%)
Figure 2
Primary language, open-source corpus
Among the 209 open-source projects that declare a primary language. Python's lead is real, but three of the top five are JavaScript-family or systems languages.
- Python103 projects49%
- TypeScript57 projects27%
- JavaScript14 projects7%
- Go12 projects6%
- Rust10 projects5%
- Java3 projects1%
- Other (6 languages)10 projects5%
Figure 3
Category density, and who leads each
Tools per category, with the highest-adoption record in each. Categories with no adoption signal at all are marked commercial-led rather than ranked — we never present alphabetical order as a ranking.
- Coding Agents37 toolsgemini-cli · 106k
- Agent Frameworks31 toolslangchain · 143k
- Voice Agents29 toolsxiaozhi-esp32-server · 10k
- MCP Servers28 toolscontext7 · 60k
- Research & Data Agents27 toolsfirecrawl · 160k
- Agent Infrastructure23 toolsdaytona · 72k
- Workflow & Productivity22 toolsn8n · 199k
- Autonomous Agents21 toolsAutoGPT · 186k
- Browser & Computer Use20 toolsUI-TARS-desktop · 38k
- Customer Support Agents5 toolsMaxKB · 22k
- Sales & Marketing Agents4 toolscommercial-led
Figure 4
The language map is territorial
Python and TypeScript project counts per category, open-source records only. The overall ratio flips category by category — which language you should reach for depends entirely on what you are building.
| Category | Python | TypeScript | Leans |
|---|---|---|---|
| Coding Agents | 10 | 12 | TypeScript |
| Agent Frameworks | 21 | 4 | Python |
| Voice Agents | 14 | 3 | Python |
| MCP Servers | 10 | 10 | Even |
| Research & Data Agents | 19 | 2 | Python |
| Agent Infrastructure | 6 | 7 | TypeScript |
| Workflow & Productivity | 4 | 10 | TypeScript |
| Autonomous Agents | 9 | 3 | Python |
| Browser & Computer Use | 9 | 6 | Python |
Figure 5
What each of these things actually is
The corpus is not all “agents”. Nearly as much of it is the substrate — frameworks, SDKs, and infrastructure that other people's agents run on.
- Agents99 records40%
- Frameworks41 records17%
- Platforms35 records14%
- Infrastructure27 records11%
- SDKs25 records10%
- MCP servers19 records8%
- MCP clients1 records0%
Figure 6
Momentum this window
New GitHub stars between the two most recent index refreshes (27 July – 3 August 2026). This is the one figure on the page that changes every week.
How this was counted
Agent Search Engine is a hand-curated index of AI agents, frameworks, and MCP servers — every record reviewed and categorised by a person, not assembled by keyword scrape. Adoption figures are live GitHub stars, refreshed weekly by an automated pass; category and editorial judgments are ours. Records without a public repository carry no star signal and are never ranked as if they did. Rankings are not for sale — no placement in this report or anywhere on the site can be purchased. The full method is on the methodology page, and the entire corpus is machine-readable at /llms-full.txt.
Every figure above is computed from the live index when this page is served, not typed in by hand — so the report ages with the ecosystem instead of freezing at publication. The date under the headline is the last refresh it reflects.