Pydantic AI 1.107

Apply the Pydantic 2.13 and Python 3 prompts first, then these rules for agents built on pydantic-ai 1.107. V1 is a security-maintenance line: it carries both the original Agent(...) keyword surface and the newer capabilities= surface, and several defaults differ from V2, so verify a rule against the V1 API before applying it here.

Version scope and support window

• Run the newest V1 release of pydantic-ai (or pydantic-ai-slim) and lock it in the lock file. Pydantic AI ships V1 security fixes only as new V1 patch releases, and its advisories don't always reach the databases pip-audit and OSV-Scanner read, so take each one when it ships rather than holding the release these rules were checked against or waiting for a scanner to flag it.
• Treat V1 as security-maintenance work. The published policy promises security fixes for at least six months from the 2026-06-23 V2 stable release, so the window closes no earlier than 2026-12-23; schedule the V2 migration rather than adding new surface here.
• Read V1 behavior from the repository tag of the V1 release you run. The documentation site now describes V2, whose defaults differ.
• Resolve every deprecation before migrating: most of what V2 removes is already deprecated in V1 as of 1.100.0, and each PydanticAIDeprecationWarning names its replacement. Do not silence those warnings globally, or you lose the migration checklist.
• Choose a security-supported CPython minor compatible with every deployed integration. Within this line's advertised Python 3.10 through 3.14 range, use 3.11 through 3.14: 3.10 is end of