Agno v3.1.0
Agno v3.1.0 introduces RBAC for AgentOS, a database-backed filesystem, and AIMLAPITools, alongside breaking schema changes for DbFileSystem and opt-in MCP tools.
Why this signal matters
Agno v3.1.0 brings major additions to the AgentOS ecosystem, including a role-based access control (RBAC) package (agno.os.authz) supporting pluggable native and fine-grained authorization (FGA) engines, audit logs, and admin routers. It introduces DbFileSystem under agno.fs with dedicated API routes, and a new AIMLAPITools toolkit for media generation and transcription via AI/ML API. Breaking changes include a re-key of the agno fs filesystem table to (namespace, user id, path) . Existing tables will fail with SchemaOutdatedError until migrated manually via the provided PostgreSQL or SQLite scripts while the application is stopped. Additionally, MCPConfig(tools=...) now strictly serves only the explicitly listed tools, making default and lifecycle tools (e.g., continue/cancel run) opt-in.
Actionable summary
Agno v3.1.0 adds agno.os.authz for RBAC, introduces agno.fs (DbFileSystem), and refreshes MCP config/auth. Breaking changes require manual database migration for DbFileSystem tables re-keyed to (namespace, user id, path) and make MCP default and lifecycle tools strictly opt-in.
- Agent usefulness
- 94/100
- Confidence
- 96%
- Canonical data
- JSON + Markdown
What builders should check
- If using DbFileSystem, stop the application and run the appropriate database migration script (libs/agno/migrations/migrate filesystem postgres.py or migrate filesystem sqlite.py) to resolve the SchemaOutdatedError.
- Review MCPConfig declarations; explicitly configure default and lifecycle tools if your agents rely on built-in tools or run lifecycle actions (continue run/cancel run).