pog 🤯

Appearance

pog 🤯

Nix-Powered CLI tools

Declare complete Bash CLIs in Nix, with rich parsing, portable outputs, and native completion across shells

Get Started
Shell Completions
Portable Outputs
View on GitHub
🚀

Pure Nix Power

Create comprehensive CLI tools using pure Nix, leveraging the vast nixpkgs ecosystem

📖

Automatic Documentation

Generated help, positional documentation, recursive command groups, aliases, and usage text

🎯

Rich Flag System

Strict or pass-through parsing with defaults, prompts, repeatable values, and persistent or exclusive flags

🔄

Native Shell Completion

One Carapace spec generates Bash, Fish, Zsh, Nushell, PowerShell, and six other adapters

Build programmable providers

🎨

Terminal Enhancement

Rich terminal colors, styling, and interactive features like spinners and prompts

🛠

Developer Friendly

Helper functions, runtime input management, verbose mode, and automatic shellcheck

âš¡

Quick Integration

Easy to integrate with existing Nix projects through overlays or direct imports

📦

Portable Distribution

Turn one pog definition into a host script, an Arx bundle, or an AppImage

Explore portable outputs

Define once, choose how to ship ​

A normal pog package can also produce three opt-in, single-file outputs:

OutputDependency modelGood fit
toHostScriptUses commands already installed on the hostBootstrap scripts and managed fleets
toArxCarries the Nix closure inside an experimental Linux bundleInternal tools that need exact Nix dependencies
toAppImageCarries the Nix closure inside an AppImageDistributing a Linux CLI as one familiar artifact

The normal Nix package stays unchanged until one of these outputs is requested. Each format uses the same flags, commands, help, runtime inputs, and script definition.

See the portable outputs guide →

Quick Example ​

nix
pog {
  name = "deploy";                                     # derivation/script name
  description = "Deploy application to cloud";         # used in the help doc
  flags = [
    pog._.flags.aws.region                             # a flag with shell completion, included in pog
    {
      name = "environment";
      short = "e";                                     # defaults to the first character of the name
      description = "deployment environment";          # used in the help doc
      required = true;                                 # forces the user to specify, or prompts for it
      completion = [ "dev" "staging" "prod" ];       # shell-neutral tab completion
    }
  ];
  script = helpers: ''
    green "Deploying to $environment in $region..."
    ${helpers.spinner {
      command = "kubectl apply -f ./manifests/";
      title = "Deploying...";
    }}
  '';
}