Third-Party Capabilities
Capabilities are the recommended way for third-party packages to extend Pydantic AI, since they can bundle tools with hooks, instructions, and model settings. See Extensibility for the full ecosystem, including third-party toolsets that can also be wrapped as capabilities.
Many of the use cases below are also covered by first-party capabilities in Pydantic AI itself or Pydantic AI Harness, the official capability library. Where that’s the case, we point to the built-in option first, and list the community packages as alternatives.
For model-owned task planning and progress tracking, Pydantic AI Harness ships Planning, a cache-friendly self-updating task plan. As a community alternative with subtask, dependency, and PostgreSQL persistence support:
pydantic-ai-todo-TodoCapabilitywithadd_todo,read_todos,write_todos,update_todo_status, andremove_todotools. Supports subtasks, dependencies, and PostgreSQL persistence. Also available as a lower-levelTodoToolset.
Pydantic AI has built-in compaction — provider-native APIs and model-agnostic history summarization — and Pydantic AI Harness adds a full menu of compaction strategies. As a community alternative:
summarization-pydantic-ai- Four capabilities for managing long conversations:ContextManagerCapability(real-time token tracking, auto-compression at a configurable threshold, and large tool-output truncation);SummarizationCapability(LLM-powered history compression);SlidingWindowCapability(zero-cost message trimming);LimitWarnerCapability(injects a finish-soon hint before hard context limits). Also available as standalonehistory_processors:SummarizationProcessor,SlidingWindowProcessor, andLimitWarnerProcessor.
Pydantic AI supports multi-agent patterns directly, and Pydantic AI Harness ships SubAgents for delegating self-contained tasks to named child agents. As a community alternative:
subagents-pydantic-ai-SubAgentCapabilityadds tools for multi-agent delegation:task(spawn a subagent),check_task,wait_tasks,list_active_tasks,soft_cancel_task,hard_cancel_task, andanswer_subagent. Supports sync, async, and auto-execution modes, nested subagents, and runtime agent creation. Also available as a lower-level toolset viacreate_subagent_toolset.
Pydantic AI Harness provides input and output guardrails that validate or block requests and responses, and Pydantic AI enforces usage, token, and request limits via UsageLimits. As a community alternative bundling several ready-made shields, including USD cost tracking:
pydantic-ai-shields- Ready-to-use guardrail capabilities:CostTracking(tracks token usage and USD cost per run, raisesBudgetExceededErroron budget overrun);ToolGuard(block or require approval for specific tools);InputGuardandOutputGuard(custom sync or async validation functions);PromptInjection,PiiDetector,SecretRedaction,BlockedKeywords, andNoRefusalscontent shields.
Pydantic AI Harness ships sandboxed FileSystem and Shell capabilities, plus CodeMode for running tool calls as sandboxed Python. As a community alternative:
pydantic-ai-backend-ConsoleCapabilityregistersls,read_file,write_file,edit_file,glob,grep, andexecutetools with a fine-grained permission system. Backends includeStateBackend(in-memory, for testing),LocalBackend(real filesystem),DockerSandbox(isolated container execution), andCompositeBackend(routing across backends). Also available as a lower-levelConsoleToolset.
Pydantic AI supports Agent Skills natively through on-demand capabilities, which collapse a skill to a one-line catalog entry until the model loads it. As a community alternative:
pydantic-ai-skills-SkillsCapabilityimplements Agent Skills support with progressive disclosure (load skills on-demand to reduce tokens). Supports filesystem and programmatic skills; compatible with agentskills.io.
Capabilities for querying and analyzing structured data help agents answer questions over files and databases:
pydantic-ai-chdb-ChDBCapabilitygives agents analytical SQL over local files (Parquet/CSV/JSON), object storage, and remote databases with chDB, the in-process ClickHouse engine — the engine itself needs no server or connection string to run (remote sources are reached via ClickHouse table functions, which take their own credentials). Registersrun_select_query(read-only ClickHouse SQL with parameter binding),list_databases,list_tables,describe_table,get_sample_data,list_functions, andattach_file(opt-in writable sessions) tools plus schema-first instructions. Sessions default to the engine-levelreadonly=2setting with capped results, and typed engine errors are mapped toModelRetryso the model can correct its queries. Works with agent specs out of the box, so it can be loaded viafrom_spec/Agent.from_spec. Also available as a lower-level toolset viaChDBCapability(...).get_toolset().
To add your package to this page, open a pull request.
To publish your own capability package, see Publishing capabilities and Extensibility.