Fetching from the wire…
Public story · 2026-07-13 · high
Each instance reportedly uses about 3.75 kilobytes of memory, per Agno's own GitHub page, not third-party benchmarks.
Why now: The claim is surfacing as agent workflows scale to thousands of instances, which is exactly when per-instance overhead stops being trivia and starts being a spec.
Agno says its runtime spins up a new agent in under two microseconds, using about 3.75 kilobytes of memory per instance, according to the project's GitHub page.
That matters once a workflow is running thousands of agents instead of one. Startup time and memory footprint turn into a real cost line, not a rounding error next to which model you picked.
The catch: the numbers come only from Agno's own repo. There's no independent benchmark cited, no load test run by anyone outside the project, and no head-to-head against other agent frameworks doing the same job. Until someone outside Agno reproduces it, this is a single-source claim, not a verified spec.
The framing behind it is worth separating from the number itself. Most agent framework pitches compete on which model wins a benchmark. Agno is arguing the bottleneck moves somewhere else once you're spawning agents by the thousand: the cost of spawning itself becomes the constraint, not model quality.
If nobody outside Agno reproduces that microsecond figure under real load, it's a marketing number, not an architecture advantage. I'd rather see one team running Agno at swarm scale publish their own measurement than take GitHub's word for it.
Each link below shares sources, entities, or timing with this story.
MCPConfig.tools now accepts Agent, Team and Workflow instances plus Toolkit objects, exposing each as its own named MCP tool. You call chief, not run_agent(agent_id="chief"). Toolkits publish one MCP tool per registered method, narrowed by the toolkit's own enable/include/excl...
The community-maintained list at 91.4K stars now outstars nearly every actual agent framework, and activepieces/activepieces (23.4K, TypeScript) leads its description with the connector count as the headline feature (GitHub). When a curated markdown file outstars the framework...
3,364 stars since its August 17 creation. Every action against a computer, file, MCP server or UI component routes through a single gateway that resolves the target, decides it against policy, writes an audit row, then acts or refuses while naming the rule. Each bot gets its o...
A GitHub repo cataloging Claude Code tips doesn't normally warrant a top story. But shanraisshan/claude-code-best-practice at 53.4K stars isn't a tips list anymore. It's the de facto reference for how an entire generation of developers is learning to work with AI coding agents...
Triple-stream retrieval (BM25 keyword, vector embeddings, knowledge-graph traversal) fused via Reciprocal Rank Fusion on the iii engine, with SQLite for state and an in-memory vector index, no external database. The economic claim: ~170K tokens/year (~$10) versus ~650K tokens...
Released August 26, two days after 3.0.0 stable: tool schemas are derived once and cached across runs rather than rebuilt per run, and session history loads incrementally per turn so latency stays flat as a conversation grows. The fix list is mostly MCP and Gemini correctness,...
MindPattern daily
One email a day at 7 AM. Sources and a take on every story. Unsubscribe anytime.