> This page is for Postman Docs, version Latest (v12) (default).
> For other versions, use one of these documentation indexes:
> - Latest (v12) (default): https://learning.postman.com/latest-v-12/llms.txt
> - v11: https://learning.postman.com/v11/llms.txt

> For clean Markdown content of this page, append .md to this URL. For the complete documentation index, see https://learning.postman.com/llms.txt.

# Postman CLI basic commands

> Get help, check version info, update the Postman CLI, and send feedback using the update and feedback commands.

This topic covers basic Postman CLI commands for getting help, version information, and updating the CLI.

## `postman`

The base command of the Postman CLI is `postman`. Run this command with the syntax and options detailed below.

### Usage

```bash
postman [options]
```

### Options

**`--color <value>`** `'auto' | 'on' | 'off'` — default: auto

Controls colored output in the terminal. Accepts `auto`, `on`, or `off`. With `auto`, the Postman CLI attempts to turn colored output on or off based on the terminal's color support.

---

**`--help, -h`**

Returns information about Postman CLI commands and options.

---

**`--silent`**

Silences all terminal output.

---

**`--version, -v`**

Returns the version number for the Postman CLI.

---

> **Tip**
>
> You can run the `man postman` command to return a manual page with the Postman CLI commands and options.

### Examples

```bash
postman --help
postman -v
```

## `postman update`

Updates the Postman CLI to the latest version using the method you installed it with, such as npm, Homebrew, or the install script. Run it after a new release to upgrade in place. To check whether an update is available without installing it, pass `--check`.

The command checks for a newer version before it installs anything. If you're already on the latest version, it reports that and installs nothing. If the check fails or can't be read, the command runs the installer anyway.

After a successful update, the command checks the `postman/skills` folder in the current directory and updates any [agent skills](/docs/postman-cli/postman-cli-skills/) that are behind.

The Postman CLI also runs an automatic update check that reports when the agent skills in `postman/skills` are behind. The check runs at most once an hour, and setting the `POSTMAN_CLI_SKIP_UPDATE_CHECK` environment variable to `1` turns off both the skills check and the version check.

### Usage

```bash
postman update [options]
```

### Options

**`--check`**

Checks whether a later version of the Postman CLI is available, without installing it. If an update is available, the command tells you to run `postman update`. Otherwise, it reports that you're running the latest version. The command also reports whether the folder's agent skills are behind, without updating them.

---

**`--timeout <ms>`** — default: 30000

Sets how long the command waits for the version check, in milliseconds. Accepts a positive integer up to `2147483647`. A check that times out counts as a failed check, so the command runs the installer. An unusable value exits with code `2`.

---

## `postman status`

Shows the Postman CLI version, whether a folder contains Postman resources, the account or session the CLI is using, the state of the folder's [agent skills](/docs/postman-cli/postman-cli-skills/), and which coding agents have the Postman plugin installed. The command is read-only and doesn't require you to sign in.

### Usage

```bash
postman status [dir-path] [options]
```

**`[dir-path]`**

The folder to check. Defaults to the current directory. The command doesn't search parent folders.

---

### Options

**`--json`**

Prints the status as JSON with the `version`, `initialized`, `auth`, `skills`, and `agentPlugins` fields.

---

### Output

* **Postman resources** — Reports whether the folder contains both a `.postman` folder and a `postman` folder. If it doesn't, run [`postman init`](/docs/postman-cli/postman-cli-init/#postman-init).
* **Authentication** — Reports the same account, temporary-session, or signed-out details as [`postman whoami`](/docs/postman-cli/postman-cli-auth/#postman-whoami). When the `POSTMAN_API_KEY` environment variable is set, the command reports that the CLI is using it. The command doesn't print or validate the key.
* **Skills** — Reports `current`, `behind`, or `unknown`, with the same guidance as [`postman skills status`](/docs/postman-cli/postman-cli-skills/#postman-skills-status). The command checks the published skills even if the folder isn't initialized. It makes one request that doesn't require authentication. Set `POSTMAN_SKILLS_URL` to change where it checks, and `POSTMAN_SKILLS_TIMEOUT_MS` to change the five-second time limit.
* **Agent plugins** — Lists each detected coding agent and whether the [Postman plugin](/docs/postman-plugin/overview) is installed, not installed, or can't be determined. In `--json` output, `agentPlugins.agents` maps each agent to `installed`, `not_installed`, `agent_not_found`, or `unknown`, and `agentPlugins.installCommand` holds the command that installs the plugins, `npx @postman/postman-plugin`. The command checks each agent, and checks your system's configuration, not the folder's. The command respects the `CODEX_HOME` and `CLAUDE_CONFIG_DIR` environment variables.

### Exit codes

* `0` — The check completed, including when skills are behind.
* `1` — The command couldn't read the status, or couldn't reach the skills repository.
* `2` — The path isn't an existing folder.

### Examples

```bash
postman status

postman status ./services/api --json
```

## `postman feedback`

Submits feedback about the Postman CLI, such as usability issues, gaps, and improvement suggestions. You, or an AI agent, pass the feedback as text, which gives a structured way to send it from the command line.

### Usage

```bash
postman feedback <text> [options]
```

**`<text>`**

The feedback to submit.

---

### Options

**`--type <type>`** `'general' | 'cli_gap' | 'improvement_suggestion' | 'bug_report' | 'feature_request'` — default: general

The kind of feedback you're submitting.

---

**`--context <context>`**

The command or feature the feedback is about.

---

**`--json`**

Prints the result as JSON for machine-readable output.

---

### Examples

```bash
postman feedback "The performance run output is hard to read when piped"

postman feedback "Add a dry-run flag to workspace push" --type feature_request --context "workspace push"
```