Agno（原 Phidata）Agno (formerly Phidata)
Agno（原 Phidata）把「框架 + 控制平面」做成一体（Apache-2.0）：库侧定义 agent/team/workflow， AgentOS 控制平面侧跑起来、观测、调度（「self-driving agent platform」）。发版高频 （v3.1.12，2026-10-29）、changelog 当日有条目——活跃线。
Agno (formerly Phidata) ships framework + control plane as one: define agents/teams/workflows in code, AgentOS runs, observes and schedules them ("self-driving agent platform"). Frequent releases (v3.1.12, 2026-10-29) — an active line.
适合与不适合When to use it, when not to
适合：框架+控制平面一体选型、Python 生态、要活跃维护。 不适合：只要薄库、TS 生态。
Fits: framework + control plane as one (run/observe/schedule), Python ecosystem, active-maintenance selections. Not a fit: wanting only a thin library, the TS ecosystem.
中文生态China availability 国产 / 国内可直接用 / 备案状态 · 快照domestic / direct access / CAC filing · snapshot 2026-10-31
- 出品属地Origin
- 国外出品foreign-made Agno Inc.（页脚「Agno Inc. All rights reserved」在册；条款页挂 os.agno.com/legal/）。Agno Inc. (footer "Agno Inc. All rights reserved" on record; terms hosted at os.agno.com/legal/).
- 国内使用Direct access
- 大陆可直连direct OK agno.com / docs.agno.com / os.agno.com/legal/tos 直连实测均 200（2026-10-31）；GitHub 仓大陆直连波动（同日代理可达）。agno.com, docs.agno.com and os.agno.com/legal/tos all measured 200 direct (2026-10-31); the GitHub repo's mainland reachability fluctuates (200 via proxy the same day).
- 备案状态CAC filing
- 未见于备案名单not in filing list：未见于网信办公示名单（2026-10-31 检索）；该产品未面向大陆公众提供服务，备案不适用。not in the CAC public registry (searched 2026-10-31); the product does not serve the mainland public, so filing does not apply.
备案信息以网信办《生成式人工智能服务已备案信息》公示名单为准（按批次滚动更新，本站只抄编号不解读）；「大陆可直连」是本站从大陆网络直连实测的结果，不是厂商承诺。GitHub 类站点当日实测有波动，口径写在依据里。Filing status is quoted from the CAC public registry (updated batch by batch; this site copies the number and does not interpret it). "Direct access" is this site's own reachability measurement from a mainland network, not a vendor promise. GitHub-hosted sites fluctuated on the measurement day — the note says so.
固定坐标系Fixed coordinate system
8 个维度dimensions, 与同分区其他对象逐项可比each comparable item by item against others in the same section.
- 模型与开放条件Model & openness
多模型接入（各家 API 与本地线，未逐条清点）；定位语「The self-driving agent platform」 （官方仓描述）——框架库 + 控制平面（AgentOS）两层。
Multi-model access (each vendor's API and local lines, not itemized); the positioning line is "The self-driving agent platform" (official repo description) — two layers: a framework library + a control plane (AgentOS).
- 运行位置Where it runs
Python 框架 + AgentOS 运行时：库侧定义 agent/team/workflow，控制平面侧跑与观测。 GitHub agno-agi/agno 42,981★、最近推送 2026-10-30（API 核验，高活跃）； releases 高频（v3.1.12，2026-10-29）；官网 changelog 最新条目 2026-10-30。
A Python framework + the AgentOS runtime: the library side defines agents/teams/workflows, the control-plane side runs and observes them. GitHub agno-agi/agno 42,981 stars, last push 2026-10-30 (API verified, highly active); releases are frequent (v3.1.12, 2026-10-29); the site changelog's latest entry is 2026-10-30.
- 本地文件Local files
库与 AgentOS 可自托管（「runs in your cloud」官方口径）；托管控制平面是另一产品面（os.agno.com）。
The library and AgentOS can be self-hosted ("runs in your cloud", official wording); the hosted control plane is a separate product surface (os.agno.com).
- 关机后的任务Tasks after shutdown
AgentOS 控制平面自带常驻运行与观测语义（agent 跑在平面里、任务可调度）； 纯库用法则是普通进程内调用。
The AgentOS control plane carries resident-running and observability semantics by itself (agents run inside the plane, tasks can be scheduled); pure library usage is ordinary in-process calls.
- 工具与扩展Tools & extensions
工具/知识库/记忆组件线内置（框架自带 memory+knowledge 组件是卖点）；MCP 支持状态未逐条核验。
Built-in tool / knowledge-base / memory component lines (framework-native memory + knowledge components are the selling point); MCP support status not itemized.
- 上下文与记忆Context & memory
内置记忆与知识组件（agent memory、knowledge/RAG 面）是产品叙事一部分；细节未逐条核验。
Built-in memory and knowledge components (agent memory, knowledge/RAG surfaces) are part of the product narrative; details not itemized.
- 权限与限制Permissions & limits
控制平面持凭据跑 agent 与工具——自托管平面的鉴权与隔离是运维责任； 托管面（os.agno.com）数据在厂商侧。
The control plane holds credentials and runs agents and tools — authentication and isolation of a self-hosted plane are operational duties; on the hosted surface (os.agno.com) data sits vendor-side.
- 适合什么任务Best for
适合：要「框架+控制平面」一体（跑起来+观测+调度）、Python 生态、要高频发版的活跃选型。 不适合：只要薄库不要平面、TS 生态（Python 为主）。
Fits: wanting "framework + control plane" as one (run + observe + schedule), the Python ecosystem, selections that need frequent releases and active maintenance. Does not fit: wanting only a thin library without a plane, the TS ecosystem (Python-first).
头号误解Top misconception
- 改名史两段：Phidata → Agno（2025 年初改名）——旧教程/旧包名 phidata 与现 agno 是同一线，检索时两词都要查Two-stage rename history: Phidata → Agno (renamed early 2025) — old tutorials/the old package name phidata and the current agno are the same line; search both words
- 条款挂在 os.agno.com/legal/（tos+privacy 200 在册），主站 /terms /privacy 404——条款面在控制平面子域，不在营销主域Terms live on os.agno.com/legal/ (tos + privacy 200 on record); the main site's /terms /privacy are 404 — the terms surface sits on the control-plane subdomain, not the marketing domain
- 库/平面两分：Apache-2.0 是库仓许可；托管控制平面（os.agno.com）是商业服务面——许可与商用条款按面分开看Library/plane split: Apache-2.0 is the library repo's license; the hosted control plane (os.agno.com) is a commercial service surface — read license and commercial terms per surface
未知项清单Known unknowns
- MCP 支持状态（未逐条核验）
- 托管控制平面（os.agno.com）与自托管 AgentOS 的能力差异表（未逐条对照）
- 条款页主体行未在抓到的 HTML 明文解析出（页脚 Agno Inc. 在册；签约主体细节未逐字核）
- MCP support status (not itemized)
- A capability-difference table between the hosted control plane (os.agno.com) and self-hosted AgentOS (not compared item by item)
- The signing-entity line was not parsed in plain text from the fetched terms HTML (footer "Agno Inc." on record; entity details not verified word by word)
证据来源Evidence sources
判断可回到以下一手源复核。本站核验日Every judgement can be rechecked against the primary sources below. Verified on 2026-10-31，内容更新日content updated on 2026-10-31。
| 类型Type | 名称Name | 链接Link |
|---|---|---|
| repo | agno-agi/agno · 仓库（Apache-2.0；42,981★，最近推送 2026-10-30，GitHub API 核验）agno-agi/agno · repository (Apache-2.0; 42,981 stars, last push 2026-10-30, GitHub API verified) | https://github.com/agno-agi/agno |
| docs | Agno · 官方文档（docs.agno.com，主站 /docs 308 目标）Agno · official docs (docs.agno.com, the 308 target of the main site's /docs) | https://docs.agno.com/ |
| changelog | Agno · 官方 changelog（最新条目 2026-10-30）Agno · official changelog (latest entry 2026-10-30) | https://www.agno.com/changelog |
| terms | Agno · 条款（os.agno.com/legal/tos，主体 Agno Inc.）Agno · terms (os.agno.com/legal/tos, entity Agno Inc.) | https://os.agno.com/legal/tos |
实测记录Measured runs
本档未跑集成与性能实测；结论只覆盖 API 与官方文档披露的能力面。
This site has not completed measured runs. The test protocol is at protocols/framework/_protocol.md.
相关条目Related entries
- LangGraphLangGraph同大类对照：LangGraph 给图与状态机制让你搭平面，Agno 把平面（AgentOS）直接给你——搭与给的分野。Same-category contrast: LangGraph gives you graphs and state mechanisms so you build the plane; Agno hands you the plane (AgentOS) directly — build vs. given.
- LettaLetta / MemGPT同大类对照：Letta 的记忆是 agent 自编辑本体（服务器形态），Agno 的记忆是框架内置组件（平面观测形态）。Same-category contrast: Letta's memory is the agent-self-edited core (server form); Agno's memory is a framework-built-in component (plane-observability form).
- DifyDify跨大类对照：Dify 低代码可视化搭 agent 应用，Agno 代码定义 agent 再交给平面跑——automation 与 framework 的边界样本。Cross-category contrast: Dify builds agent apps visually with low-code; Agno defines agents in code and hands them to a plane to run — a boundary sample between automation and framework.
本页由This page is generated from the ai-handbook 数据层生成（CC BY 4.0）。data layer (CC BY 4.0).
方法论与坐标系定义见仓库内For the methodology and coordinate definitions, see METHODOLOGY.md.