`Agno` `2.x` migration lands for travel planner agents after `CVE-2026-35002`

A critical eval injection issue forces agno agent teams off 1.x. If you copied older multi-agent patterns, this is a patch-now upgrade, not a cosmetic refactor.

[ KEY POINTS ]

The travel planner team moved from agno 1.x to 2.x to remediate critical CVE-2026-35002, so older examples are no longer safe defaults.
Several APIs were renamed: add_datetime_to_instructions to add_datetime_to_context, add_member_tools_to_system_message to add_member_tools_to_context, and enable_agentic_context to enable_agentic_state.
A few knobs disappeared entirely: show_tool_calls and success_criteria were removed, which can break copied templates even if the agent logic stays the same.
This matters if your codebase inherited agno sample apps. Budget time for API churn and re-test prompt/context behavior after the upgrade.

Originalgithub.com/Shubhamsaboo/awesome-llm-apps/commit/644957619a0a7e522a3290af63facb626b36ad20Read original →

// related

#0001
#0001Agents & tools Google AI Forum37 minutes ago
`Antigravity 2.0` Install/Update Bug Workaround: Roll Back to `1.23.2`
40radar
AntigravityAI coding agent IDE — integrated with Google tooling
Rollback first, then disable background updates. Until the installer stabilizes, manual updates are the practical path.
- Download 1.23.2 from previous releases instead of installing 2.0; this is a rollback workaround, not a permanent fix.
- After opening Antigravity, go to Editor Settings > Application > Update and disable Windows Background Updates.
- Switch update mode to Manual Mode and restart. This avoids being pushed back into the broken update path.
Source: discuss.ai.google.dev/t/solution-for-antigravity-2-0-insRead original →
FIG-0011:1
40radar
FIG-0011:1
#0002
#0002Agents & tools Google AI Forum1 hour ago
`Antigravity` agent sessions hit template mismatch blocker
40radar
AntigravityAI coding agent IDE — built around Google's stack
Prompt generation fails before a new agent session starts. Treat it as a blocker, not a workflow tweak.
- The failure happens in PlannerGenerator / CascadeManager, before the agent session reaches useful work.
- communication_style calls CascadeConfig.GetSupportsLatexRendering, but the current protobuf type lacks that field.
- Impact is complete session creation failure. If your workflow depends on Antigravity, keep a fallback agent ready.
Source: discuss.ai.google.dev/t/agent-executor-error-communicatiRead original →
FIG-0021:1
40radar
FIG-0021:1
#0003
#0003Agents & tools Google AI Forum1 hour ago
`Antigravity` paid user reports forced update broke workspace
50radar
AntigravityAI coding IDE — Google's agent-based dev environment
A forced IDE update allegedly scattered projects, split threads, and wiped settings. Treat agent IDEs as volatile infra: pin versions and keep rollback paths ready.
- Ultra costs $200/month, yet the reported update shipped with no email, warning, migration path, or visible rollback.
- Breakage hit core state: projects, conversations, settings, and config. Back up .vscode-style config and agent history separately.
- Users are reportedly reverting to 1.23.2 and disabling auto-update. Version pinning becomes part of production workflow.
Source: discuss.ai.google.dev/t/200-month-subscriber-and-this-upRead original →
FIG-0031:1
50radar
FIG-0031:1

`Agno` `2.x` migration lands for travel planner agents after `CVE-2026-35002`

// related

`Antigravity 2.0` Install/Update Bug Workaround: Roll Back to `1.23.2`

`Antigravity` agent sessions hit template mismatch blocker

`Antigravity` paid user reports forced update broke workspace