Key points
- Postman desktop logs record automatic plugin installation on 24 October 2026.
- The installer code attempts to approve its own instruction hook for Codex.
- The hook instructs agents to route API tasks through Postman skills.
Hacker News reported that a user investigation found Postman desktop version 12.33.4 automatically installed a plugin and attempted to approve its own instruction hook for coding agents.reported The investigation, dated 25 October 2026, identified changes to Codex and Claude Code agents after opening Postman on a Mac.reportedA user found that opening Postman on their Mac automatically installed a plugin and changed settings in their coding agents.The investigation reveals that Postman v12.33.4 uses an installer that attempts to self-approve hooks for Codex agents via batchWrite operations.
Evidence: reported
Postman silently auto-installs AI plugins and attempts to share all API dataaifleet-hn-ai
Evidence: reported
Postman silently auto-installs AI plugins and attempts to share all API dataaifleet-hn-ai
The evidence
The log entries at lines 11562-11563 correspond to the installation of the Codex Postman plugin version 1.1.0.reported
Evidence: reported
Postman silently auto-installs AI plugins and attempts to share all API dataaifleet-hn-ai
The investigation found that Codex’s global user configuration was changed to include a startup instruction hook. The hook registers a SessionStart command with a matcher for startup, clear, or compact events.
The hook instructs the agent to load the postman:api-engineer skill before responding to any non-trivial API engineering task. This includes designing, implementing, mocking, testing, monitoring, documenting, or deploying an API or Postman Flow.
The installer source code explicitly attempts to approve its own hook after installation. It invokes approvePostmanHook and uses config/batchWrite to upsert the hook state with a trusted hash.
The decision
The user considered the automatic changes to unrelated coding agents a severe consent and trust-boundary problem. They argued that an API client should not make itself the default workflow in other tools simply because the user opened it.
What the evidence means
The installer logic aims to bypass manual hook approval by programmatically setting the trusted hash. This suggests a design choice to ensure the plugin functions without explicit user intervention for hook registration.
The hook’s broad matcher captures general session start events, ensuring the instruction is loaded frequently. This explains the recurring Postman skill announcements observed in the coding agents.
What builders can do with it
Developers can observe how the plugin uses the codex-hooks.json interface to register session start commands. The source shows how a hook can be registered with specific matchers and context files.
Builders can review the installer source to understand how approvePostmanHook interacts with the system configuration. The code demonstrates the use of batchWrite to update hook states with trusted hashes.
The investigation highlights the impact of remote MCP connections and CLI installations on agent behaviour. Developers can use this to audit their own agent configurations for unexpected routing.
Why it matters
- The automatic installation recorded in logs raises questions about plugin consent mechanisms in desktop applications.
- The self-approving hook logic shows how plugins can attempt to enforce their workflow in external coding agents.
- The broad hook matcher demonstrates how agent instructions can be triggered by general session events rather than specific user requests.
Topics: Postman, AI agents, plugin security, consent, MCP
Updated
Then / now / next
Users expected Postman to remain a standalone API client without altering other coding tools.
A user investigation shows Postman auto-installed a plugin and attempted to set itself as a default workflow in coding agents.
It remains unclear if this behaviour is intentional by design or an unintended consequence of the plugin installer.
Story timeline
- Then Users expected Postman to remain a standalone API client without altering other coding tools.
- 03 Nov 2026 Postman silently auto-installs AI plugins and attempts to share all API data
- Now A user investigation shows Postman auto-installed a plugin and attempted to set itself as a default workflow in coding agents.
- Next It remains unclear if this behaviour is intentional by design or an unintended consequence of the plugin installer.
The strongest doubt
Counterpoint from the sources
The source material does not provide an official response from Postman or clarify whether the automatic installation is a known feature or a bug.
For readers
Developers
- Review plugin installer code for automatic configuration changes and self-approving hooks.
- Audit agent configurations for unexpected routing instructions and remote connections.
Policy
- Consider consent requirements for software that modifies external tool configurations.
- Evaluate trust boundaries for plugins that install hooks in unrelated applications.
Consumers
- Check application logs for automatic installations if you notice unexpected behaviour in coding tools.
- Verify that plugins do not alter global configurations without explicit user approval.
Ask the article
Local keyword search of this article; no generated answers.Did this article give you the evidence you needed?
Your choice stays on this device. No public tally.Terms in this story
MCP
Model Context Protocol, a standard for connecting AI models to external tools and data sources.
Hook
A mechanism that allows external code to intercept or modify the behaviour of a software application.
BatchWrite
A configuration update method that writes multiple values to a system state simultaneously.
Questions readers ask
Did Postman confirm the automatic plugin installation?
No, the report is based on a user investigation and log analysis, not an official statement from Postman.
What version of Postman was involved in the investigation?
Postman desktop version 12.33.4 was the version used during the investigation on 25 October 2026.
Does the hook require user approval?
The installer code attempts to approve the hook automatically, but the source does not confirm if this succeeds without user intervention.
Connected stories
Reading receipt
- Postman desktop logs record automatic plugin installation on 24 October 2026.
- The installer code attempts to approve its own instruction hook for Codex.
- The hook instructs agents to route API tasks through Postman skills.
Still open: Did the self-approving hook logic succeed in modifying the user’s configuration without explicit approval?
Still open: Is the automatic installation of the plugin an intentional feature or an unintended bug in Postman v12.33.4?