Agno 3.0.7 fixes a Python 3.13 leak that pinned agents in memory

Agno 3.0.7 patches a memory leak specific to Python 3.13. Pydantic's validate_call decorator stores the caller's f_locals on the wrapper function it builds, and Agno's Function class caches those wrappers for the life of the process. On 3.13, that combination kept every cached tool holding a reference to its Agent, session, and run state indefinitely, according to the release notes.

For anyone running long-lived agent processes, that's not a cosmetic bug. Every tool call adds another wrapper the garbage collector can't touch, so memory climbs until the process gets killed or restarted. If your agents run for hours or days rather than single requests, you were bleeding memory without any error to point at.

The same release fixes something more urgent for two providers: a signature drift in _format_message was crashing runs on Meta Llama and AIMLAPI outright, not degrading them. If you're on either, this upgrade isn't optional.

3.0.7 also ships two additions unrelated to the fixes. PublicSurface lets you serve a chosen set of agents with shared quotas and bounds on request and output size, aimed at exposing agents without exposing your whole backend. There's also a read-only page filesystem toolkit that's bounded by design: it can't shell out and can't write, which matters if you're giving a tool filesystem access and don't want it to become a shell.

The leak is a reminder that caching decisions inside a framework you didn't write can outlive the assumptions you made about them. Agno cached wrappers assuming they'd be cheap; Pydantic's decorator made them expensive on newer Python with no version bump anywhere warning either project's users. Check whether other cached-wrapper patterns in your stack make the same assumption.