postman-cli-completion

Shell completion scripts for the Postman CLI (postman) on zsh, bash, and fish.

Completes:

• All top-level commands (login, collection, spec, monitor, workspace, flows, etc.) and their subcommands.
• Flags for each (sub)command.
• Local file arguments such as *.json (collections, manifests) and *.yaml/*.yml (specs, simulate scenarios).

Dynamic completion of remote IDs (collection / workspace / monitor IDs) is not supported — paste those yourself.

Install

Via npm (recommended)

npm install -g postman-cli-completion

This installs a postman-completion helper command — it does not shadow the real postman CLI (install that separately via npm i -g postman-cli). The helper prints the completion script for your shell to stdout; wire it in as follows.

zsh — quick test in the current shell (requires compinit already initialised, see the note below):

source <(postman-completion zsh)

zsh — persistent. Add the packaged completions dir to fpath in ~/.zshrc:

fpath=("$(postman-completion path zsh --dir)" $fpath)
autoload -Uz compinit && compinit

bash — add to ~/.bashrc (requires bash 4+; see the bash note below):

source <(postman-completion bash)

fish — source it in the current session, or install it persistently:

postman-completion fish | source
# persistent:
ln -sf "$(postman-completion path fish)" ~/.config/fish/completions/postman.fish

From source

Clone this repo somewhere, e.g. ~/.postman-cli-completion:

git clone https://github.com/yokawasa/postman-cli-completion.git ~/.postman-cli-completion

zsh

Add the completions directory to fpath and rerun compinit. Put this in ~/.zshrc:

fpath=(~/.postman-cli-completion/completions/zsh $fpath)
autoload -Uz compinit && compinit

Or, for a quick test in the current shell:

source ~/.postman-cli-completion/completions/zsh/_postman

Note: compinit must already be initialised in your shell for source to register the completion. Most zsh setups (oh-my-zsh, prezto, or a plain .zshrc that runs autoload -Uz compinit && compinit) do this automatically. If postman <TAB> still does nothing after sourcing, run autoload -Uz compinit && compinit first and try again.

bash

Add to ~/.bashrc (or ~/.bash_profile on macOS):

source ~/.postman-cli-completion/completions/bash/postman.bash

Requires bash 4+ (shopt -s extglob). On macOS the system bash is 3.2 — install a newer bash via Homebrew (brew install bash) if needed.

fish

Copy or symlink into fish's completion directory:

ln -s ~/.postman-cli-completion/completions/fish/postman.fish \
      ~/.config/fish/completions/postman.fish

Or source it in the current session:

source ~/.postman-cli-completion/completions/fish/postman.fish

Verify (manual checklist)

After installing for your shell, open a fresh terminal and check each:

Input	Expected
postman <TAB>	All top-level commands appear
postman col<TAB>	Completes to collection
postman collection <TAB>	migrate, lint, run
postman collection run <TAB>	*.json files in the current directory
postman collection run --<TAB>	Flag list (--environment, --iteration-data, --reporters, …)
postman collection run -r <TAB>	cli, json, junit, html
postman request <TAB>	GET, POST, PUT, DELETE, PATCH, HEAD, OPTIONS
postman spec lint <TAB>	*.yaml / *.yml / *.json files
postman flows <TAB>	list, trigger, deploy, run, update, list-runs, get-run
postman --<TAB>	--silent, --color, --version, --help

Versioning

The completion scripts are auto-generated from a single source of truth (spec/commands.json) and tracked against the upstream Postman CLI by two GitHub Actions workflows:

• catchup.yml runs daily, queries npm for the latest postman-cli version, introspects its --help surface, regenerates the spec and the three completion scripts, and opens an auto-merging PR whenever something changed.
• release.yml fires when spec/commands.json lands on main and publishes a matching GitHub Release (e.g. tag v1.39.0 mirrors Postman CLI 1.39.0).

So this repo follows the latest published Postman CLI version automatically — pull the latest main (or grab the matching tag) and the completions will match whatever Postman CLI version you have installed.

Suspicious catchup diffs (≥30 % flag drop, a known fixed command missing, semver regression) are blocked by scripts/validate-diff.mjs and stay open for human review instead of auto-merging.

To check the version the committed spec was generated against:

node -p "require('./spec/commands.json').postmanCliVersion"

And your installed Postman CLI:

postman --version

License

MIT — see the LICENSE file.