postman-cli 1.60.0 → 1.63.0

package/bin/postman.js

@@ -1,5 +1,7 @@
 #!/usr/bin/env node
 
+const { constants } = require('os');
+
 // Keep this wrapper alive while the native binary handles shutdown gracefully.
 process.on('SIGINT', function () {});
 process.on('SIGTERM', function () {});
@@ -10,5 +12,22 @@ try {
     run(...process.argv.slice(2));
 }
 catch (error) {
+    // The CLI's exit codes are a documented contract (`postman init` returns 2 for
+    // ambiguous specs and 4 for a refusal, for instance), so the binary's own code has
+    // to survive this wrapper. execFileSync throws on any non-zero exit and carries
+    // the code as `status`; collapsing that to 1 made a recoverable refusal
+    // indistinguishable from a crash.
+    if (typeof error.status === 'number') {
+        process.exit(error.status);
+    }
+
+    // A signalled child has no status. Report it the way a shell does.
+    if (error.signal) {
+        process.exit(128 + (constants.signals[error.signal] || 0));
+    }
+
+    // Spawning the binary failed outright (missing platform package, not executable).
+    // The message never reached the user before, leaving a silent exit 1.
+    process.stderr.write(`${error.message || error}\n`);
     process.exit(1);
 }

package/man/postman.1

@@ -1,4 +1,4 @@
-.TH POSTMAN 1 "2026-09-21" "v1.60.0" "Postman CLI Manual"
+.TH POSTMAN 1 "2026-09-23" "v1.63.0" "Postman CLI Manual"
 .SH NAME
 postman \- Command\-line companion utility for Postman
 .SH SYNOPSIS
@@ -94,7 +94,7 @@ Use the skills bundled with this CLI instead of fetching the latest
 Which spec is authoritative, when more than one could be
 .TP
 .B \-\-visibility <status>
-Create and bind a workspace non\-interactively (personal or team)
+Create and bind a workspace non\-interactively (personal, team)
 .TP
 .B \-\-no\-cloud
 Skip the workspace step entirely
@@ -120,11 +120,21 @@ Exit codes:
 
 Code 5 needs \-\-visibility: without it no workspace was requested, so nothing
 can fail for not getting one. It does not mean re\-run init \- the local files
-are already written.
-
-Under \-\-json, read `exitCode` and `refusal` from the payload rather than
-matching the messages on stderr. `refusal.kind` is one of
-foreign\-postman\-dir, bound\-spec\-missing, spec\-hint\-unmatched.
+are already written. A \-\-visibility that is not personal, team is code 5 on
+every path, including \-\-json, CI and \-\-no\-cloud: none of them makes the value
+usable, so none of them should report success for it.
+
+Under \-\-json, read `exitCode`, `refusal`, `usageError` and `cloud` from the
+payload rather than matching the messages on stderr. `refusal.kind` is one of
+foreign\-postman\-dir, bound\-spec\-missing, spec\-hint\-unmatched. `usageError`
+names the flag whose value init could not use. `cloud` says what happened to
+the workspace step, including why it was skipped.
+
+\-\-json with \-\-visibility creates the workspace, same as without it: stdout
+carries the payload and everything meant for a person goes to stderr. It used
+to skip the step and exit 0, so a missing `origin` remote or a failed bind
+went unreported. Without \-\-visibility, \-\-json still skips \- there is nothing
+to create and init may not prompt.
 
 Examples:
   $ postman init
@@ -145,6 +155,23 @@ Show the Postman account or guest session this CLI session is using.
 .B \-\-json
 Print current identity as machine\-readable JSON.
 
+.SS "feedback"
+Submit feedback about CLI usability, gaps, and improvement suggestions.
+
+.B Usage:
+[options] <text>
+
+.B Options:
+.TP
+.B \-\-type <type>
+Feedback type: cli_gap, improvement_suggestion, bug_report, feature_request, general (default: general)
+.TP
+.B \-\-context <context>
+Command or feature context this feedback is about
+.TP
+.B \-\-json
+Print result as machine\-readable JSON
+
 .SS "update"
 Update Postman CLI using the original installation method.
 
@@ -266,6 +293,12 @@ Score a Postman collection for AI readiness by ID, local file path, or local\-mo
 .B collection get
 Fetch a Postman collection in the V3 format and print it.
 .TP
+.B collection request
+Add, update, or remove requests in a local v3 collection.
+.TP
+.B collection folder
+Add, update, or remove folders in a local v3 collection.
+.TP
 .B collection list
 List collections: your local project's collections by default, or a Postman cloud workspace's collections with \-\-workspace.
 .TP
@@ -302,8 +335,8 @@ Examples:
 Without \-\-workspace this writes postman/collections/<name>/.resources/definition.yaml
 in the current directory, which must be a local Postman workspace (a directory holding
 \&.postman/ or postman/). Add requests as <request\-name>.request.yaml files beside it, then
-publish with `postman workspace push`. Creating a collection in a workspace requires
-authentication.
+publish with `postman workspace push`. Creating a collection in a workspace works with a
+signed\-in credential or with the guest session `postman init` mints.
 
 
 
@@ -377,6 +410,282 @@ Eg. postman collection get 12345\-33823532ab9e41c9b6fd12d0fd459b8b
     postman collection get 0123456789abcdef01234567 \-\-json
 
 
+.SS "collection request"
+Add, update, or remove requests in a local v3 collection.
+
+.B Usage:
+[options] [command]
+
+.B Subcommands:
+.TP
+.B collection request add
+Add an empty request to a local v3 collection (set its details later with `update`).
+.TP
+.B collection request update
+Update a request in a v3 collection (only the fields you pass).
+.TP
+.B collection request rm
+Remove a request (any type) from a v3 collection.
+
+.SS "collection request add"
+Add an empty request to a local v3 collection (set its details later with `update`).
+
+.B Usage:
+[options] [request\-name]
+
+.B Options:
+.TP
+.B \-\-collection <id|name>
+Target collection: name, directory, id, cloud id, or path. Required.
+.TP
+.B \-\-folder <id|name|path>
+Folder within the collection, e.g. "Users/Admin". Defaults to the root.
+.TP
+.B \-\-type <type>
+Request type: http, graphql, grpc, websocket, socketio. (default: http)
+.TP
+.B \-w, \-\-workspace <id>
+Target a Postman cloud workspace by id (cloud mode).
+.TP
+.B \-\-json
+JSON output.
+
+.TP Examples:
+
+Creates an empty request (name + type only). Configure it with `collection request update`.
+
+Examples:
+  postman collection request add "Get user" \-\-collection "My API"
+  postman collection request add \-\-collection "My API"            # named "New request"
+  postman collection request add "List" \-\-collection "My API" \-\-folder Users \-\-type http
+
+
+
+.SS "collection request update"
+Update a request in a v3 collection (only the fields you pass).
+
+.B Usage:
+[options] <request>
+
+.B Options:
+.TP
+.B \-\-collection <id|name>
+Target collection: name, directory, id, cloud id, or path (cloud: id only). Required.
+.TP
+.B \-\-folder <id|name|path>
+Folder to scope the request selector, e.g. "Users/Admin" (local: name/path; cloud: id).
+.TP
+.B \-\-rename <name>
+Rename the request (moves its file). Any request type.
+.TP
+.B \-\-url <url>
+Request URL. Any request type.
+.TP
+.B \-\-method <method>
+HTTP method (http requests only).
+.TP
+.B \-\-param <key:value>
+Replace query parameters. Repeatable (http requests only). (default: )
+.TP
+.B \-d, \-\-body <body>
+Request payload (inline, @file, or \- for stdin), interpreted by request type. For http, an optional "<type>:" prefix picks the content type: json/text/xml/html/javascript, file:<path>, urlencoded:key=v&k2=v2, or formdata:key=v&file=@path.
+.TP
+.B \-\-variables <json>
+GraphQL variables JSON (graphql requests only).
+.TP
+.B \-\-description <text>
+Request description.
+.TP
+.B \-\-headers <key:value>
+Replace request headers. Repeatable; any request type with headers. (default: )
+.TP
+.B \-\-auth <spec>
+Request auth: none, inherit, bearer:TOKEN, basic:USER:PASS, apikey:KEY:VALUE[:header|query], oauth2:TOKEN. Any request type.
+.TP
+.B \-\-scripts <event:script>
+Replace scripts. event is prerequest or test; script is @file, \- for stdin, or inline. Repeatable; any request type. (default: )
+.TP
+.B \-w, \-\-workspace <id>
+Target a Postman cloud workspace by id (cloud mode).
+.TP
+.B \-\-type <type>
+Request type for cloud mode: http, graphql, grpc, websocket, socketio. (default: http)
+.TP
+.B \-\-json
+JSON output.
+
+.TP Examples:
+
+Works on any request type; \-\-rename/\-\-url/\-\-description/\-\-headers/\-\-auth/\-\-scripts apply to all, while \-\-method/\-\-param/\-\-body are http\-only. Select the request by the <request> selector: local — a name or "Folder/Name" path (or \-\-folder to scope a bare name); cloud (\-\-workspace) — a request id, with \-\-collection an id too.
+
+Examples:
+  postman collection request update "Get user" \-\-collection "My API" \-\-url "{{baseUrl}}/users/:id"
+  postman collection request update "Get user" \-\-collection "My API" \-\-folder Users \-\-rename "Fetch user"
+  postman collection request update "Get user" \-\-collection "My API" \-\-headers "Authorization:Bearer x" \-\-auth bearer:TOKEN \-\-scripts "test:@check.js"
+  postman collection request update <requestId> \-\-collection <collectionId> \-\-url "..." \-w <workspaceId>
+
+
+
+.SS "collection request rm"
+Remove a request (any type) from a v3 collection.
+
+.B Usage:
+[options] <request>
+
+.B Options:
+.TP
+.B \-\-collection <id|name>
+Target collection: name, directory, id, cloud id, or path (cloud: id only). Required.
+.TP
+.B \-\-folder <id|name|path>
+Folder to scope the request selector, e.g. "Users/Admin" (local: name/path; cloud: id).
+.TP
+.B \-w, \-\-workspace <id>
+Target a Postman cloud workspace by id (cloud mode).
+.TP
+.B \-\-type <type>
+Request type for cloud mode: http, graphql, grpc, websocket, socketio. (default: http)
+.TP
+.B \-\-json
+JSON output.
+
+.TP Examples:
+
+Select the request by the <request> selector: local — a name or "Folder/Name" path (or \-\-folder to scope a bare name); cloud (\-\-workspace) — a request id, with \-\-collection an id too.
+
+Examples:
+  postman collection request rm "Get user" \-\-collection "My API"
+  postman collection request rm "Get user" \-\-collection "My API" \-\-folder Users
+  postman collection request rm <requestId> \-\-collection <collectionId> \-w <workspaceId>
+
+
+
+.SS "collection folder"
+Add, update, or remove folders in a local v3 collection.
+
+.B Usage:
+[options] [command]
+
+.B Subcommands:
+.TP
+.B collection folder add
+Add an empty folder to a local v3 collection (set its details later with `update`).
+.TP
+.B collection folder update
+Update a folder in a v3 collection (only the fields you pass).
+.TP
+.B collection folder rm
+Remove a folder from a v3 collection (recursive: removes everything inside it).
+
+.SS "collection folder add"
+Add an empty folder to a local v3 collection (set its details later with `update`).
+
+.B Usage:
+[options] [folder\-name]
+
+.B Options:
+.TP
+.B \-\-collection <id|name>
+Target collection: name, directory, id, cloud id, or path. Required.
+.TP
+.B \-\-folder <id|name|path>
+Parent folder within the collection, e.g. "Users/Admin". Defaults to the root.
+.TP
+.B \-w, \-\-workspace <id>
+Target a Postman cloud workspace by id (cloud mode).
+.TP
+.B \-\-json
+JSON output.
+
+.TP Examples:
+
+Creates an empty folder (name only); set its description with `collection folder update`. Nest it with \-\-folder.
+
+Examples:
+  postman collection folder add Users \-\-collection "My API"
+  postman collection folder add \-\-collection "My API"            # named "New folder"
+  postman collection folder add Admin \-\-collection "My API" \-\-folder Users
+
+
+
+.SS "collection folder update"
+Update a folder in a v3 collection (only the fields you pass).
+
+.B Usage:
+[options] <folder>
+
+.B Options:
+.TP
+.B \-\-collection <id|name>
+Target collection: name, directory, id, cloud id, or path (cloud: id only). Required.
+.TP
+.B \-\-folder <id|name|path>
+Parent folder to scope the selector, e.g. "Users" (local: name/path; cloud: id).
+.TP
+.B \-\-name <name>
+Rename the folder (moves its directory).
+.TP
+.B \-\-description <text>
+Folder description.
+.TP
+.B \-\-auth <spec>
+Folder auth: none, inherit, bearer:TOKEN, basic:USER:PASS, apikey:KEY:VALUE[:header|query], oauth2:TOKEN.
+.TP
+.B \-\-scripts <event:script>
+Replace folder scripts. event is prerequest or test; script is @file, \- for stdin, or inline. Repeatable. (default: )
+.TP
+.B \-w, \-\-workspace <id>
+Target a Postman cloud workspace by id (cloud mode).
+.TP
+.B \-\-json
+JSON output.
+
+.TP Examples:
+
+Select the folder by the <folder> selector: local — a name or "Parent/Name" path (or \-\-folder to scope a bare name); cloud (\-\-workspace) — a folder id, with \-\-collection an id too.
+
+Examples:
+  postman collection folder update Users \-\-collection "My API" \-\-name Accounts
+  postman collection folder update "Users/Admin" \-\-collection "My API" \-\-description "Admin endpoints"
+  postman collection folder update Admin \-\-collection "My API" \-\-folder Users \-\-auth bearer:TOKEN
+  postman collection folder update <folderId> \-\-collection <collectionId> \-\-name Accounts \-w <workspaceId>
+
+
+
+.SS "collection folder rm"
+Remove a folder from a v3 collection (recursive: removes everything inside it).
+
+.B Usage:
+[options] <folder>
+
+.B Options:
+.TP
+.B \-\-collection <id|name>
+Target collection: name, directory, id, cloud id, or path (cloud: id only). Required.
+.TP
+.B \-\-folder <id|name|path>
+Parent folder to scope the selector, e.g. "Users" (local: name/path; cloud: id).
+.TP
+.B \-y, \-\-yes
+Skip the confirmation prompt (required when stdout is not a TTY).
+.TP
+.B \-w, \-\-workspace <id>
+Target a Postman cloud workspace by id (cloud mode).
+.TP
+.B \-\-json
+JSON output.
+
+.TP Examples:
+
+Removal is recursive. Select the folder by the <folder> selector: local — a name or "Parent/Name" path (or \-\-folder to scope a bare name); cloud (\-\-workspace) — a folder id, with \-\-collection an id too.
+
+Examples:
+  postman collection folder rm Users \-\-collection "My API" \-\-yes
+  postman collection folder rm "Users/Admin" \-\-collection "My API" \-y
+  postman collection folder rm <folderId> \-\-collection <collectionId> \-y \-w <workspaceId>
+
+
+
 .SS "collection list"
 List collections: your local project's collections by default, or a Postman cloud workspace's collections with \-\-workspace.
 
@@ -1358,7 +1667,7 @@ Invoke a monitor run and display results.
 .B Options:
 .TP
 .B \-\-api\-key <key>
-Postman API key (defaults to POSTMAN_API_KEY, then the `postman login` session)
+Postman API key (defaults to POSTMAN_API_KEY, then the `postman login` session, then a guest session)
 .TP
 .B \-x, \-\-suppress\-exit\-code
 Specify whether or not to override the default exit code for the current run
@@ -1444,7 +1753,7 @@ How iteration data is consumed, for example round_robin, repeat_last or stop_at_
 Do not trigger an immediate run after creating the monitor
 .TP
 .B \-\-api\-key <key>
-Postman API key (defaults to POSTMAN_API_KEY, then the `postman login` session)
+Postman API key (defaults to POSTMAN_API_KEY, then the `postman login` session, then a guest session)
 .TP
 .B \-\-json
 Output as JSON instead of a table
@@ -1528,7 +1837,7 @@ Number of iterations to run
 How iteration data is consumed, for example round_robin, repeat_last or stop_at_end (requires \-\-iteration\-count, \-\-dataset\-id and \-\-dataset\-view\-id)
 .TP
 .B \-\-api\-key <key>
-Postman API key (defaults to POSTMAN_API_KEY, then the `postman login` session)
+Postman API key (defaults to POSTMAN_API_KEY, then the `postman login` session, then a guest session)
 .TP
 .B \-\-json
 Output as JSON instead of a table
@@ -1557,7 +1866,7 @@ Permanently delete a monitor. Prompts for confirmation unless \-\-yes is passed.
 Skip the confirmation prompt
 .TP
 .B \-\-api\-key <key>
-Postman API key (defaults to POSTMAN_API_KEY, then the `postman login` session)
+Postman API key (defaults to POSTMAN_API_KEY, then the `postman login` session, then a guest session)
 .TP
 .B \-\-json
 Output the outcome, including any failure, as JSON instead of a plain message
@@ -1668,7 +1977,7 @@ List the monitors visible to you.
 .B Options:
 .TP
 .B \-\-api\-key <key>
-Postman API key (defaults to POSTMAN_API_KEY, then the `postman login` session)
+Postman API key (defaults to POSTMAN_API_KEY, then the `postman login` session, then a guest session)
 .TP
 .B \-w, \-\-workspace <id>
 Filter to monitors in this workspace
@@ -1731,7 +2040,7 @@ Show a monitor's configuration.
 .B Options:
 .TP
 .B \-\-api\-key <key>
-Postman API key (defaults to POSTMAN_API_KEY, then the `postman login` session)
+Postman API key (defaults to POSTMAN_API_KEY, then the `postman login` session, then a guest session)
 .TP
 .B \-\-json
 Output as JSON instead of a table
@@ -1751,7 +2060,7 @@ Show per\-request latency and outcome history for a monitor.
 .B Options:
 .TP
 .B \-\-api\-key <key>
-Postman API key (defaults to POSTMAN_API_KEY, then the `postman login` session)
+Postman API key (defaults to POSTMAN_API_KEY, then the `postman login` session, then a guest session)
 .TP
 .B \-\-since <dateTime>
 Only executions at or after this ISO 8601 date\-time (defaults to 7 days ago)
@@ -1785,7 +2094,7 @@ Pause a monitor, so it stops firing on schedule.
 .B Options:
 .TP
 .B \-\-api\-key <key>
-Postman API key (defaults to POSTMAN_API_KEY, then the `postman login` session)
+Postman API key (defaults to POSTMAN_API_KEY, then the `postman login` session, then a guest session)
 .TP
 .B \-\-json
 Output as JSON instead of a table
@@ -1799,7 +2108,7 @@ Resume a paused monitor, so it fires on schedule again.
 .B Options:
 .TP
 .B \-\-api\-key <key>
-Postman API key (defaults to POSTMAN_API_KEY, then the `postman login` session)
+Postman API key (defaults to POSTMAN_API_KEY, then the `postman login` session, then a guest session)
 .TP
 .B \-\-json
 Output as JSON instead of a table
@@ -1969,7 +2278,7 @@ Create a Postman workspace and bind it to this git repository.
 .B Options:
 .TP
 .B \-\-visibility <status>
-Required. Workspace visibility, e.g. personal or team
+Required. One of: personal, private, team, public, partner.
 .TP
 .B \-\-name <name>
 Workspace name (defaults to owner/repo from the git remote)
@@ -1977,6 +2286,12 @@ Workspace name (defaults to owner/repo from the git remote)
 .B \-\-summary <text>
 Optional workspace summary
 .TP
+.B \-\-team\-id <id>
+The team inside your organisation the workspace belongs to. Required for a team workspace when your organisation has teams inside it. Find it with `postman team list`.
+.TP
+.B \-\-team\-role <level>
+What a team or public workspace grants: view or edit. Applies to the team named by \-\-team\-id, or to your whole organisation when none is named. Defaults to your team's configured default.
+.TP
 .B \-\-path <dir>
 Directory to bind (defaults to the current directory)
 .TP
@@ -1988,12 +2303,15 @@ Create even when a workspace is already recorded for this repo
 
 .TP Examples:
 
-Requires a login (`postman login`) or POSTMAN_API_KEY.
+Requires a login (`postman login`) or POSTMAN_API_KEY. A guest session
+has no account to own a workspace: run `postman signup` first.
 Refuses to run on CI: create once locally and commit the binding.
 
 Examples:
   $ postman workspace create \-\-visibility personal
   $ postman workspace create \-\-visibility team \-\-name "acme/orders"
+  $ postman workspace create \-\-visibility team \-\-team\-id 451
+  $ postman workspace create \-\-visibility team \-\-team\-role view
   $ postman workspace create \-\-visibility personal \-\-no\-connect
 
 
@@ -2090,6 +2408,58 @@ Examples:
 
 
 
+.SS "team"
+Work with the teams inside your organisation.
+
+.B Usage:
+[options] [command]
+
+.TP Examples:
+
+These are the teams inside an organisation, which the Postman app shows
+under "Teams". The organisation itself is what `postman whoami` reports
+as your team. A Postman team that is not an organisation has none.
+
+
+
+.B Subcommands:
+.TP
+.B team list
+List the teams inside your organisation.
+
+.SS "team list"
+List the teams inside your organisation.
+
+.B Usage:
+[options]
+
+.B Options:
+.TP
+.B \-\-can\-create\-workspace
+Only list teams you could create a workspace in.
+.TP
+.B \-\-json
+Print the list as machine\-readable JSON.
+.TP
+.B \-\-timeout <ms>
+Abort the run after this many milliseconds. Defaults to 30000.
+
+.TP Examples:
+
+Requires a login (`postman login`) or POSTMAN_API_KEY.
+These are the teams inside your organisation. The organisation itself is
+what `postman whoami` reports as your team. `postman workspace create
+\-\-team\-id <id>` takes the id from this list.
+
+A Postman team that is not an organisation has no teams inside it, so this
+lists nothing and exits 0.
+
+Examples:
+  $ postman team list
+  $ postman team list \-\-can\-create\-workspace
+  $ postman team list \-\-json
+
+
 .SS "performance"
 Manage performance tests on your collections.
 
@@ -2148,6 +2518,9 @@ How rows map to VUs: round\-robin (default), fixed, random
 .B \-\-postman\-api\-key <apiKey>
 API Key used to load the resources from the Postman API (Only supported in the US region, use 'postman login \-\-region' to authenticate instead)
 .TP
+.B \-\-output <format>
+Output format for live results: auto (default, interactive dashboard) or ndjson (one JSON object per line on stdout, ending with a "summary" event — for CI or other non\-interactive use) (default: auto)
+.TP
 .B \-\-runner <runner>
 Runner to execute the performance test on: local, postman\-cloud, or postman\-cloud\-static\-ip (egress from your account region's static\-IP cluster) (default: )
 .TP
@@ -3330,7 +3703,7 @@ Start a mock using its path if it lives in your repository, or its id if it live
 .B Options:
 .TP
 .B \-e, \-\-environment <path>
-Path to a file of environment variables for the mock. Relative or absolute, e.g. ./postman/environments/dev.json
+Path to a file of environment variables for the mock. Relative or absolute, e.g. ./postman/environments/dev.environment.yaml
 .TP
 .B \-g, \-\-globals <path>
 Path to a file of global variables for the mock. Relative or absolute, e.g. ./globals.json
@@ -3345,7 +3718,7 @@ Postman API key, used with a Postman cloud id (defaults to your `postman login`
 
 Eg. postman mock run 12345678\-90ab\-cdef\-1234\-567890abcdef  # by id, from Postman cloud
     postman mock run ./postman/mocks/orders                # by path, from your repository
-    postman mock run ./postman/mocks/orders \-\-environment ./postman/environments/dev.json
+    postman mock run ./postman/mocks/orders \-\-environment ./postman/environments/dev.environment.yaml
     postman mock run ./postman/mocks/orders \-\-port auto    # pick any free port
     postman mock run ./postman/mocks/orders \-\-port 4600    # use port 4600 (fails if it is in use)
 
@@ -3710,7 +4083,7 @@ Start mocks with fault\-injection scenarios defined in a .sim.yaml file
 .B Usage:
 [options] <filepath>
 
-.SS "context"
+.SS "describe"
 [Beta] Get API context for AI coding agents directly from the command line.
 
 
@@ -3719,7 +4092,7 @@ Start mocks with fault\-injection scenarios defined in a .sim.yaml file
 
 .B Subcommands:
 .TP
-.B context instructions
+.B describe instructions
 Get agent instructions for using Postman Context with AI coding agents.
 
 Topics:
@@ -3729,25 +4102,25 @@ Topics:
   maintenance     — Agent instructions for maintaining and updating client code
 
 .TP
-.B context collection
+.B describe collection
 Collection commands
 .TP
-.B context request
+.B describe request
 Request commands
 .TP
-.B context folder
+.B describe folder
 Folder commands
 .TP
-.B context response
+.B describe response
 Response commands
 .TP
-.B context workspace
+.B describe workspace
 Workspace commands
 .TP
-.B context environment
+.B describe environment
 Environment commands
 
-.SS "context instructions"
+.SS "describe instructions"
 Get agent instructions for using Postman Context with AI coding agents.
 
 Topics:
@@ -3760,7 +4133,7 @@ Topics:
 .B Usage:
 [options] [topic]
 
-.SS "context collection"
+.SS "describe collection"
 Collection commands
 
 .B Usage:
@@ -3768,13 +4141,13 @@ Collection commands
 
 .B Subcommands:
 .TP
-.B context collection get
+.B describe collection get
 Get a collection's metadata and a map of its folders and requests.
 
 Returns collection info (name, description, variables, auth) plus a
 recursive tree of folders and requests.
 
-.SS "context collection get"
+.SS "describe collection get"
 Get a collection's metadata and a map of its folders and requests.
 
 Returns collection info (name, description, variables, auth) plus a
@@ -3788,7 +4161,7 @@ recursive tree of folders and requests.
 .B \-c, \-\-collection\-id <id>
 Collection ID
 
-.SS "context request"
+.SS "describe request"
 Request commands
 
 .B Usage:
@@ -3796,10 +4169,10 @@ Request commands
 
 .B Subcommands:
 .TP
-.B context request get
+.B describe request get
 Get a request from a collection
 .TP
-.B context request context
+.B describe request context
 Fetch all context about a request and return it as a Markdown document.
 
 Returns: collection metadata, request details (method, URL, headers, body,
@@ -3807,9 +4180,9 @@ auth, docs), parent folder documentation, response examples, and
 environment variables.
 
 Examples:
-  postman context request context \-c <collection\-id> \-r <request\-id>
+  postman describe request context \-c <collection\-id> \-r <request\-id>
 
-.SS "context request get"
+.SS "describe request get"
 Get a request from a collection
 
 .B Usage:
@@ -3823,7 +4196,7 @@ Request ID
 .B \-c, \-\-collection\-id <id>
 Collection ID
 
-.SS "context request context"
+.SS "describe request context"
 Fetch all context about a request and return it as a Markdown document.
 
 Returns: collection metadata, request details (method, URL, headers, body,
@@ -3831,7 +4204,7 @@ auth, docs), parent folder documentation, response examples, and
 environment variables.
 
 Examples:
-  postman context request context \-c <collection\-id> \-r <request\-id>
+  postman describe request context \-c <collection\-id> \-r <request\-id>
 
 .B Usage:
 [options]
@@ -3844,7 +4217,7 @@ Collection ID
 .B \-r, \-\-request\-id <id>
 Request ID
 
-.SS "context folder"
+.SS "describe folder"
 Folder commands
 
 .B Usage:
@@ -3852,10 +4225,10 @@ Folder commands
 
 .B Subcommands:
 .TP
-.B context folder get
+.B describe folder get
 Get a folder from a collection
 
-.SS "context folder get"
+.SS "describe folder get"
 Get a folder from a collection
 
 .B Usage:
@@ -3869,7 +4242,7 @@ Folder ID
 .B \-c, \-\-collection\-id <id>
 Collection ID
 
-.SS "context response"
+.SS "describe response"
 Response commands
 
 .B Usage:
@@ -3877,10 +4250,10 @@ Response commands
 
 .B Subcommands:
 .TP
-.B context response get
+.B describe response get
 Get a saved response example from a collection
 
-.SS "context response get"
+.SS "describe response get"
 Get a saved response example from a collection
 
 .B Usage:
@@ -3897,7 +4270,7 @@ Collection ID
 .B \-r, \-\-request\-id <id>
 Request ID
 
-.SS "context workspace"
+.SS "describe workspace"
 Workspace commands
 
 .B Usage:
@@ -3905,10 +4278,10 @@ Workspace commands
 
 .B Subcommands:
 .TP
-.B context workspace get
+.B describe workspace get
 Get a workspace by ID
 
-.SS "context workspace get"
+.SS "describe workspace get"
 Get a workspace by ID
 
 .B Usage:
@@ -3919,7 +4292,7 @@ Get a workspace by ID
 .B \-w, \-\-workspace\-id <id>
 Workspace ID
 
-.SS "context environment"
+.SS "describe environment"
 Environment commands
 
 .B Usage:
@@ -3927,10 +4300,10 @@ Environment commands
 
 .B Subcommands:
 .TP
-.B context environment get
+.B describe environment get
 Get a single environment by ID
 
-.SS "context environment get"
+.SS "describe environment get"
 Get a single environment by ID
 
 .B Usage:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "postman-cli",
-  "version": "1.60.0",
+  "version": "1.63.0",
   "description": "Official Postman CLI - Command-line companion for API development, testing, and automation",
   "keywords": [
     "postman",
@@ -58,10 +58,10 @@
     "man/"
   ],
   "optionalDependencies": {
-    "@postman/pm-bin-macos-arm64": "1.60.0",
-    "@postman/pm-bin-macos-x64": "1.60.0",
-    "@postman/pm-bin-linux-x64": "1.60.0",
-    "@postman/pm-bin-linux-arm64": "1.60.0",
-    "@postman/pm-bin-windows-x64": "1.60.0"
+    "@postman/pm-bin-macos-arm64": "1.63.0",
+    "@postman/pm-bin-macos-x64": "1.63.0",
+    "@postman/pm-bin-linux-x64": "1.63.0",
+    "@postman/pm-bin-linux-arm64": "1.63.0",
+    "@postman/pm-bin-windows-x64": "1.63.0"
   }
 }