@postman/postman-plugin 0.2.1 → 0.2.2

package/README.md

@@ -169,40 +169,41 @@ external systems need access, the same mock can become a durable hosted URL
 without rebuilding it in another tool.
 
 
-## Telemetry
+## How Postman builds context
 
-Some Postman CLI commands report usage analytics by default. Where supported,
-you can disable reporting for an individual command with
-`--no-report-events`. `postman application test` uses
-`--report-events=false` instead.
+Work done in a Postman folder produces artifacts: collection runs, lint
+results, request history, mock deployments. When that folder is connected to a
+Postman workspace, after `postman init`, those artifacts are
+published to it as they are produced. The workspace is
+where a teammate, a reviewer, or another agent can see what the agent actually
+did.
 
-What is sent by default:
+What each command contributes to the connected workspace:
 
-| Command | Data sent |
+| Command | What it publishes |
 | --- | --- |
-| `postman collection run` | Run analytics and run history |
-| `postman application test` | Run results and analytics |
-| `postman spec lint` | Lint analytics, including violation counts and pass/fail |
-| `postman workspace push` | Push analytics |
-| `postman runner start` | Runner analytics |
-| `postman flows run` | Flow-run analytics |
-| `postman request` | Request analytics |
-
-Important limits:
-
-- `postman collection run --no-report-events` disables analytics but does not
-  disable run-history uploads.
-- `postman init` makes richer reporting opt-in with `--report-events`; it does
-  not accept `--report-events=false`.
-- The CLI also sends a minimal, unauthenticated event indicating that certain
-  commands ran. Reporting flags do not disable these client events. They are
-  emitted by `collection run`, `spec lint`, `workspace push`, `init`, the
-  `mock` commands, and `performance run` in the US region; other regions,
-  including the EU, do not emit them.
-- The plugin registers Postman's hosted MCP server as a fallback when the CLI
-  cannot run. MCP tool calls reach Postman and are not controlled by CLI
-  reporting flags; avoiding that traffic requires not installing the MCP
-  server.
+| `postman collection run` | Run results and run history |
+| `postman application test` | Test run results |
+| `postman spec lint` | Lint results, including violation counts and pass/fail |
+| `postman workspace push` | The local workspace contents |
+| `postman runner start` | Runner processing and health activity |
+| `postman flows run` | Flow run results |
+| `postman request` | Agent's API interaction activity |
+
+
+Publishing happens by default. To change this workflow, you can set 
+`--report-events=false` per invocation.
+
+### Anonymous usage counts
+
+The CLI records command usage surface — a minimal,
+unauthenticated count with no workspace, user, or payload attached.
+
+### The MCP fallback
+
+The plugin registers Postman's hosted MCP server as a fallback for when the CLI
+cannot run. MCP tool calls reach Postman by design and are not governed by the
+CLI flags above; skip installing the MCP server if you do not want that path.
 
 ## License
 

package/mcp.pi.json

@@ -6,8 +6,8 @@
       "description": "Postman workspaces, collections, specs, environments, mocks and monitors",
       "headers": {
         "X-Source": "postman-pi-plugin",
-        "X-Plugin-Version": "0.2.1",
-        "User-Agent": "postman-pi-plugin/0.2.1"
+        "X-Plugin-Version": "0.2.2",
+        "User-Agent": "postman-pi-plugin/0.2.2"
       }
     }
   }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@postman/postman-plugin",
-  "version": "0.2.1",
+  "version": "0.2.2",
   "description": "Postman's API engineering skills for coding agents: a Pi package, and an npx installer that sets up Claude Code, Codex, Cursor, Kimi Code, Factory Droid, OpenCode and Pi.",
   "type": "module",
   "license": "Apache-2.0",

package/skills/api-monitoring/SKILL.md

@@ -99,8 +99,9 @@ Postman's cloud. Extra
 flags cover the runner's own networking: `--region eu` for EU residency,
 `--proxy`/`--egress-proxy`/`--egress-proxy-authz-url` for outbound routing,
 `--ssl-extra-ca-certs` for a private CA, and `--metrics`/`--metrics-port`
-for a health-check endpoint. Analytics are sent by default; `--no-report-events`
-opts out. `runner list` shows the team's registered self-hosted runners —
+for a health-check endpoint. Runner activity is published to the connected
+workspace by default; `--no-report-events` keeps it local. `runner list` 
+shows the team's registered self-hosted runners —
 feed an id from here into `monitor create/update --runner` or `monitor list
 --runner`. `runner regions` lists the Postman-region and private-runner
 values valid for `--runner` on `monitor create`/`update`, including a

package/skills/api-testing/SKILL.md

@@ -73,9 +73,10 @@ answering "did my app's actual calls conform to the contract," not "does
 this endpoint respond correctly." `--capture-only` skips the matching step
 entirely and just exports what was captured as a new v3 collection,
 organized by host — a way to bootstrap a collection from real traffic
-rather than authoring one from scratch. Results upload to Postman
-automatically after each run; `--report-events=false` skips that for a run
-that shouldn't be recorded.
+rather than authoring one from scratch. Results are published to the connected
+workspace after each run, so the evidence of the run outlives the terminal
+session; `--report-events=false` keeps a run local when it shouldn't be
+recorded.
 
 ## Critical Rules
 

package/skills/flows/reference/flow_cli_flags.md

@@ -80,7 +80,7 @@ execution and reporting. Takes the path positionally; a bad path fails with
 | `-x, --suppress-exit-code` | Overrides the run's exit code. Defeats CI gating. |
 | `--verbose` | Per-request detail: method, URL, assertions. |
 | `--no-truncate` | Full output, no truncated long values. |
-| `--no-report-events` | Don't send analytics. `--report-events` exists for compatibility; analytics are on by default. |
+| `--no-report-events` | Keep the run local instead of publishing results to the connected workspace. |
 
 ### BETA: dataset iteration