Agno 3.2.0 moves A2A to v1.0 and rebuilds Slack on Bolt

Agno v3.2.0 was published on November 12, 2026 (20:47 Istanbul time), two weeks after 3.1.12. It is a minor version with real breaking changes: AgentOS and A2AClient move to the official a2a-sdk 1.x, the Slack interface is rewritten on Slack Bolt with stricter approval rules, and the OS Manager gets new defaults. On top of that come database-backed homepage metrics, stored ClaudeAgent and CodexAgent components, and a Super Agent that now does the work itself instead of handing requests to manager members.

Release facts

Check before upgrading

• Upgrade A2A server and client together. AgentOS and A2AClient now run on a2a-sdk 1.x, and the a2a extra requires a2a-sdk[http-server]>=1.2.2,<2. The /v1/message:* and /v1/tasks:* routes are gone; call each entity's own A2A endpoint. Stream events and artifacts follow the v1.0 shape. Standard v0.3 clients still connect through a compatibility wire, which is on by default.
• Slack runs on Bolt now. Run pip install -U "agno[slack]", which needs slack_bolt>=1.29.0,<2 and slack_sdk>=3.43.0,<4. Only the person who started a run can Approve or Deny it, unless they are listed in approvers= or mapped through users=. Internal helpers such as SlackEventHandler, HITLHandler and verify_slack_signature were removed.
• AgentOS can refuse to start. It stops at startup if Slack serves agent_os.manager under AgentOS(authorization=...) without users=, if OSManager(root=...) is combined with your own tools named read_file, list_files or search_content, or if Slack(...) has no token or signing secret.
• OS Manager defaults changed. tool_call_limit goes from 8 to 24 and num_history_runs from 7 to 5. Set them explicitly if you tuned costs around the old values.

What's new

• Super Agent uses tools directly. It lists and runs agents, teams and workflows, reads platform activity and schedules, and uses Company, docs, source-file and custom OS Manager tools. Platform Builder is its only member, and every tool keeps its own permission check.
• Company OS. Routines run on a restricted Mini Agent that cannot chat and is hidden from discovery, MCP and A2A. Tasks expose last_run and allowed_transitions, can be started directly, and Super Agent can start an accepted Task on the durable queue without blocking the conversation. Published Studio agents, teams and workflows can execute Tasks and Routines; drafts cannot.
• Homepage metrics. New tables back daily sessions, runs, tokens, users, models, cost, duration, time to first token and model latency under /os/metrics/*. Refreshes run in the background, rebuild only changed days and support ETags. Fresh installs no longer create the old agno_metrics table.
• Stored external agents. ClaudeAgent and CodexAgent can be saved, versioned, listed and run through the components API. Settings that cannot be serialized now fail loudly instead of being dropped.
• A2A tasks in the database. Send, stream, get, cancel, list and subscribe all work on stored tasks, human-in-the-loop pauses can continue, and Agent Cards advertise both v1.0 and v0.3.
• Slack agent view. Streaming replies with task cards, a Stop button that cancels Agents, Teams, Workflows and external agents, long runs that continue in a new message after nine minutes, and Claude or Codex approvals answered from Slack.
• Paginated session runs. GET /sessions/{session_id}/runs takes limit, before_run_index and after_run_index. Calls without limit still return a plain list.

Notable fixes

• Run and session token totals no longer double count and now include failed or cancelled external runs.
• Redis is optional for sandboxed agents on the durable queue; Postgres plus a shared checkpoint store handles cancellation and resume across replicas.
• Mistral streaming calls send the output schema again, and Hugging Face streams keep every tool call instead of only the first.
• Gemini Developer API features default to v1beta, and generation_config values are no longer overwritten.

Questions

Will Agno 3.2.0 break my deployment? It can if you use A2A routes under /v1/message:* or /v1/tasks:*, the Slack interface, or OSManager(root=...) with custom file tools. Check those first, then review the new OS Manager defaults.

Do old A2A clients still work? Standard v0.3 clients do, through the compatibility wire that is on by default. Agno's own A2AClient should be upgraded together with the server.

Who can approve a run in Slack now? The person who started it, plus anyone named in approvers= or mapped to the same AgentOS user with users=.

More on the Agno hub, the previous Agno 3.1.12 launch and the frameworks category. Weighing a switch? Read Agno alternatives, Agno vs CrewAI and Agno vs LangGraph.