Skip to main content
Pro feature. Requires a Pidgeon account with Post Pro entitlement. AI Triage ships with the Post desktop app and the licensed CLI, not the free dotnet tool install build.
Pass validation failures through an on-device model for root cause analysis, including vendor-specific context like “this is a common Epic-to-downstream mapping issue.” On-device is the default posture: $0 marginal cost, and no message content leaves your machine unless you explicitly opt into a cloud provider.

​
Setup

AI Triage runs on-device out of the box; no configuration is required. To opt into a cloud provider instead (BYOK, your keys, your cost control), set the egress policy and your provider key:
pidgeon ai egress (no arguments) shows the current PHI-egress policy. Every call that resolves to a non-local provider is audit-logged. See AI Commands for the full set of AI modes and providers.

​
Usage

Triage a message that fails validation:
You can also open a validated message in the Post desktop app and run triage from the AI Triage panel. Both drive the same on-device analysis.

​
Example Output

​
API

The Post Bridge exposes AI Triage at POST /api/loft/triage on localhost:5101. That route is unauthenticated because the Bridge is a single-user loopback sidecar: it only listens on localhost for the signed-in user, and the AI Triage feature itself stays gated behind Post Pro. See the API Reference for the request and response shape.