Skip to main content
pidgeon ai is a Post Pro feature and is hardware dependent. It ships with the Post desktop app and the licensed CLI, not the free dotnet tool install build. Every AI operation runs on-device by default; nothing leaves the machine without an explicit opt-in.
The ai family manages the on-device model, configures an optional cloud provider (BYOK), sets the egress policy that governs where inference is allowed to run, and runs message operations (triage a failure, explain a message, apply field-level fixes).

Model management

On-device inference needs a local model. Set one up in one step:
Or manage models directly:

On-device models

Two bundled models are validated today: Run pidgeon ai list --available for the full downloadable catalog on your machine.
Gemma 4 support (gemma4-e4b, gemma4-12b) is being validated and may appear in the catalog. Confirm availability with pidgeon ai list --available before relying on it.

Provider configuration (BYOK)

Point the AI operations at a cloud provider instead of the on-device model. Bring your own key, so cost control stays with you.
Supported providers: openai, anthropic, openrouter, ollama, azure, gemini, or any OpenAI-compatible endpoint (openai-compatible). For an OpenAI-compatible server, pass --endpoint and --model; many in-tenant servers are keyless. Use --locus in-network for a server you run yourself and --locus cloud for a compatibility-API SaaS. The locus is declared, never inferred from the address.

Message operations

Each verb takes a message file (HL7, FHIR JSON, or NCPDP XML):

PHI-egress policy

pidgeon ai egress views or sets where inference is allowed to run. The default keeps all content on-device; nothing goes off-device without an explicit opt-in.
Every call that resolves to a non-local provider is audit-logged with the provider, deployment mode, and content length.

Health and policy

Next steps