A developer opened Postman. Then two AI coding agents changed without their permission.

8 relevance

Postman AI plugin controversy is highly actionable and directly relevant to developer experience and AI tooling.

AI/ML thenewstack.io

Answer the board on AI readiness

Arrive with evidence, not opinion. See how your foundation benchmarks against your peers, get a clear read, and leave with a ranked place to start.

Why It Matters

For a platform engineer focused on AI agent orchestration and developer experience, this highlights a critical trust and security boundary: desktop tools can silently inject instructions into AI coding agents, potentially overriding developer intent and introducing opaque dependencies in the SDLC.

Key Takeaways

Audit your AI coding agent configurations (e.g., ~/.codex/config.toml) for unauthorized plugins and session-start hooks, and restrict desktop app permissions to modify agent settings.

A developer opened Postman. Then two AI coding agents changed without their permission.

Summary

A developer reported that Postman's desktop app (v12.33.4 on macOS) silently installed plugins into Claude Code and OpenAI Codex, modifying configuration files to enable a Postman skill and auto-approve a session-start hook that instructs Codex to use Postman's tools for API tasks without explicit user consent. The installer bypasses the manual review process by writing the hook's trusted hash directly to Codex's config, raising security concerns about third-party apps altering AI coding agent behavior without opt-in.

Author

Amanda Caswell