Postman update reportedly installs AI plugins and startup instructions

A November 3 report on Postman’s official GitHub support tracker says updating the desktop app to version 12.35.1 automatically installed Claude Code and Codex plugins on an existing, signed-in Mac. The user provided installation logs and explicitly said they had no evidence of uploaded data.

Postman’s current download page says its desktop app includes the CLI and agent plugins. The plugin connects API development and testing to a coding agent’s workflow. Official documentation says it handles tasks through the CLI where possible, then uses the hosted MCP server for unsupported operations. The integration therefore reaches the coding environment alongside the desktop application.

The new report identifies Codex plugin 1.3.0 and a startup instruction, but says its configuration contained no hook-trust record. The original issue dates to October 25. The full rollout and affected population remain unverified.

An installation path that includes startup instructions

In the installer revision linked by the original report, the Codex integration registers and installs the plugin, then calls a routine to approve its startup hook. A hook runs an action at the beginning of an agent session. The installation path also checks existing registrations and handles migration from an older distribution location, bringing plugin setup and session behavior into the same process. A user-selected distribution reference is preserved or blocks migration.

The approval routine reads the hook’s current fingerprint and trust status and checks that its instruction file exists before writing approval state. It rechecks the fingerprint and stops if the content changed; already trusted hooks are left alone. If the relevant Codex API is unavailable, this step is skipped while installation continues. The routine targets Postman’s own startup hook. These conditions bound what the source code demonstrates about an attempted approval.

The startup text tells agents to load Postman’s API engineering skill before substantial design, implementation, testing, monitoring or documentation work. Pure questions and trivial one-line edits are exceptions. Specific skill requests can take a narrower route. The text also gives explicit user instructions and project guidance precedence, defining both the workflow it seeks to influence and the instructions that override it.

Local work and the conditions for remote reporting

Postman’s workflow guide says local work needs no account, while cloud operations such as workspace synchronization or pushing a mock prompt for sign-in first. Generated API collections and tests can be reviewed and committed beside application code. Its MCP documentation requires an account and supports OAuth for the US remote service; the EU remote and local MCP servers use API-key authentication.

The repository documents a further condition for reporting: after a local folder is connected to a Postman workspace, artifacts such as run results, lint results and request activity are published as they are produced. A per-command reporting option changes that behavior. Hosted MCP calls reach Postman separately from the CLI’s reporting settings. Actual transmission therefore depends on the commands performed, authentication and workspace connection.

The current installer guide explicitly says the combined installer approves the Codex startup hook and asks users to review it inside Codex if approval fails. Installing through Codex’s own method leaves that review and approval to the user. Postman says its skills and MCP server work with or without the hook. The documented installer also supports selecting an agent, inspecting installation status and removing the plugin. Its combined flow includes confirmation and a preview mode that makes no changes.