Postman Is Now a Full Local Development Environment
Postman has long been the go-to tool for API testing. Now, it is pushing that boundary much further. With its latest release, Postman becomes a complete local development environment, one that sits right alongside your code, the way an editor or terminal does.
The update centers on five new capabilities: Git integration, Local Mocks, an embedded terminal, multi-protocol support in a single collection, and an AI assistant with repository context. Together, they close what developers have always called the development loop, without jumping between five different tools.
At the core of this shift is the new Unified Workbench. Collections, environments, API specs, mock servers, and flows all live in a single customizable sidebar. That means no more switching between windows to find what you need.
Native Git support is one of the biggest changes. Specs, collections, environments, mocks, and tests now live as files in the local filesystem and Git repository, right next to the application code. Moreover, collection changes can be reviewed in the same pull request as the code changes that introduced them. That alone removes a major pain point for teams managing API changes alongside source code.
Local Mock Servers take the development experience further. Local Mocks run on your machine alongside your development server, giving you a controlled environment for testing without hitting external services. Developers can therefore iterate fast, test changes in an active branch, and validate everything before a single commit goes through.
Multi-protocol support is another notable leap. REST, WebSocket, and gRPC requests can all live in the same collection. When you run the collection, it executes all three in sequence. As a result, teams can test real end-to-end flows in one run, without stitching together separate tools for each protocol.
The new Agent Mode brings AI into the workflow. Agent Mode works across specs, tests, and mocks to automate multi-step changes with broad workflow context, including input from MCP servers from Atlassian, Amazon CloudWatch, GitHub, Linear, Sentry, and Webflow, while keeping every change versioned and reviewable. Developers can use Agent Mode conversationally, delegate full workflows to it, or have it work directly on the codebase to fix errors, generate stubs, or create client code.
Postman also introduces a new Collection 3.0 format. It uses YAML files instead of JSON blobs, splitting collections into individual files that are readable and writable not only for AI agents but also easier for humans to compare and review.
The practical result is that your workspace is a directory, your changes are commits, your mocks run locally, and your tests run in CI without reconfiguration. The development loop, in other words, now closes entirely inside Postman.
For teams looking to get started, Postman provides a sample workspace, the Intergalactic Banking API, as a hands-on guide through Git-backed workspaces, Local Mocks, Agent Mode, and multi-protocol CI runs.
