0.1.0-beta.2.
What the free CLI includes
The community CLI ships 12 commands:generate, validate, deident, data, artifacts, lookup, find, path, run, session, completions, and capabilities. That covers synthetic message generation, spec validation, on-device de-identification, standards lookup, and data-package management.
conform, flock, loft, migrate, ai, diff, and config are delivered through the desktop apps, which are macOS and Windows only. If you install the CLI with dotnet tool on Linux and run pidgeon conform, it won’t be there. Run conformance from the CLI that ships with the desktop apps, or from the Conformance panel in Post.
Requirements
- A 64-bit Linux distribution (x64 or arm64)
- For the
dotnet toolinstall: the .NET 8 runtime or SDK - AI features are not part of the free CLI, so no extra RAM is required
Install with the .NET tool
Cross-platform, kept current through NuGet. Needs the .NET 8 runtime on the machine.1
Install the tool
2
Put the tools directory on your PATH
Global .NET tools install to
~/.dotnet/tools. If pidgeon isn’t found after install, add that directory to your shell profile:3
Verify
pidgeon runs but reports that it can’t find a runtime, set DOTNET_ROOT to your dotnet install path. See Troubleshooting for the exact fix.The
0.1.0-beta.2 GitHub release includes a signed Windows ZIP, but it does not
include a Linux archive. Use the published .NET tool on Linux until a Linux
self-contained artifact appears in a later release.The CLI runs the engine in-process. There is no Bridge sidecar and no local port on Linux. The loopback Bridge ports (Loft
5100, Post 5101, Flock 5102, Migrate 5103, Conform 5104) belong to the macOS and Windows desktop apps.Next steps
CLI Quickstart
Generate and validate your first message, then wire the exit codes into CI.
Capabilities
See the full command surface and global options.