By Hamza Faisal
Opening Postman on a Mac did more than open Postman. According to a detailed report in the company's own app-support tracker, a desktop update quietly installed Postman plugins into two other developer tools — Anthropic's Claude Code and OpenAI's Codex — without the user explicitly asking for them, and wrote a trust approval for its own startup hook. The discovery shot to the top of Hacker News on November 3 and sparked a fierce debate about consent in developer tools, even as the evidence stops well short of the viral claim that Postman tried to share users' API data.
What the logs showed
The report, filed as GitHub issue 14370, came from a user posting as indicava. On a signed-in Mac running Postman desktop version 12.33.4, the app's own main.log recorded an "auto-existing-upgrade" step on October 24 that installed two plugins: claude-code and codex. The user had not clicked install on either.
The changes went further than a plugin listing. On that machine, the Codex configuration gained a Postman plugin plus a trust record for Postman's SessionStart hook, which runs when an agent session starts. Claude Code received the plugin at user scope, and the plugin configured a remote connection to Postman's MCP server.
A second user, ronthedrummer, reproduced the pattern on November 3 after updating from 12.31.3 to 12.35.1, with Cursor recorded as already installed. Other users reported Postman entries in four tools — Claude Code, Codex, Cursor and Copilot — while its public plugin repository shows the installer can reach nine coding agents.
What has not been proven
The most-shared version of the story overstates what happened. The Hacker News headline claimed Postman "attempts to share all API data," but the original report explicitly does not claim data exfiltration, and the second reporter likewise wrote that there was no evidence data was uploaded.
On the first machine, the remote MCP connection never authenticated — the Codex log recorded "Auth required" — so the connection failed before data could flow through it. What the logs document is an unwanted integration and an injected session instruction, not a documented breach.
Still, the consent failure is well documented, and that drove the reaction. The Hacker News thread drew more than 1,000 points and hundreds of comments, with some users recommending open-source alternatives such as Bruno, Insomnia, Yaak and Hurl. Posts about the incident on X jumped from around 70 on November 3 to more than 400 by the morning of November 4.
Postman's response — and why developers are still angry
Postman responded in the GitHub issue on the evening of November 3. A company representative said the desktop app bundles the CLI and agent plugins because many users had trouble setting them up separately, that the bundling is mentioned on the download page and in the update flow, and that the components can be uninstalled inside the app. The company said it will make the opt-in clearer, especially for existing users, and is reviewing its hook-approval and session-start behaviour. The same commitment was attributed to Postman's head of product, Sarabmeet Kallar.
For many developers, that does not resolve the core complaint: installing a plugin, connecting to a remote server and trusting a startup hook are three separate decisions, and an upgrade should never silently make all three at once. The fix they want is simple — no automatic installation until users explicitly opt in, no installer-side self-approval of hooks, and a startup instruction that applies only when a user actually asks for Postman.



