Postman Silently Auto-Installs AI Plugins and Alters Coding Agent Configurations

What happened with the Postman desktop application update?

Recent investigations shared on autopilot gaming framework discussions and GitHub revealed that opening the Postman desktop application on macOS leads to unexpected modifications in external coding agents. The application automatically installs plugins, establishes startup instruction hooks, and configures remote Model Context Protocol connections without explicit user approval.

Evidence gathered from Postman desktop version 12.33.4 showed the automated inclusion of a Codex Postman plugin and a Claude Code plugin. According to internal application logs, the installer executed routines that altered user-wide configurations, creating significant debates regarding consent and trust boundaries across developer environments similar to those seen in tracker firmware source code releases.

How did the silent plugin installation affect coding agents?

The automated installation process leaves clear traces inside local system logs and configuration files. Postman logs explicitly record successful script completions for auto-upgrades targeting external assistants, matching mechanisms sometimes analyzed in tools like agent autoloop background utilities.

Furthermore, the global user configuration for Codex inside ~/.codex/config.toml is altered to point directly to the Postman GitHub plugin repository. Session start hooks are registered to automatically route broad API engineering tasks into Postman skills, while the installer attempts to self-approve its own hook configuration.

How can developers mitigate and remove these unwanted integrations?

Affected users who wish to remove these unwanted integrations must perform a comprehensive cleanup across multiple system paths and configuration files. Developers should check their global configuration files, remove registered hooks, and delete any automatically added marketplace sources.

To completely purge the unauthorized integrations and secure your local environment, follow these mitigation steps:

Check and clean your Codex configuration file located at ~/.codex/config.toml to remove Postman marketplaces and plugin entries.

Inspect ~/.claude/settings.json and remove any references to official Postman Claude plugins or settings scopes.

Frequently asked questions

Which Postman version and applications were affected by the silent installation?

Postman desktop version 12.33.4 automatically installed plugins for coding agents such as Codex and Claude Code without explicit user consent.

How were coding agents modified during the Postman desktop update?

The installer modified configuration files like ~/.codex/config.toml and ~/.claude/settings.json, adding marketplace sources, plugins, and startup instruction hooks.

What steps can developers take to clean up unwanted Postman integrations?

Users should inspect global configuration directories, remove unauthorized plugins and MCP connections, delete added instruction hooks, and remove the Postman CLI.