The Postman plugin is a set of skills that teach Claude Code how to do API engineering with the Postman CLI. Loading it from a local clone means every skill is available for the rest of this module.

1. Make sure the Postman CLI is installed. If postman --version fails, install it:

   $npm install -g postman-clinpm install -g postman-clicopy

   0/1 run

2. Clone the plugin repo:

   $git clone https://github.com/postmanlabs/postman-plugin.gitgit clone https://github.com/postmanlabs/postman-plugin.gitcopy

   0/1 run

3. Create a fresh project directory for this module. Postman links a workspace to a project through its Git origin remote, so give the repo one. It can be a real repo you own or a placeholder URL — nothing is pushed to it in this module:

   copy all

   $mkdir movies-api-project && cd movies-api-projectmkdir movies-api-project && cd movies-api-projectcopy

   $git initgit initcopy

   $git remote add origin https://github.com/<your-username>/movies-api-project.gitgit remote add origin https://github.com/<your-username>/movies-api-project.gitcopy

   0/3 run

4. Start Claude Code with the plugin loaded:

   $claude --plugin-dir /path/to/postman-pluginclaude --plugin-dir /path/to/postman-plugincopy

   0/1 run

5. Confirm the plugin loaded: type /postman: in Claude Code and check that skills such as postman:api-engineer and postman:api-mocking appear.

postman init is the first move in any API engineering task: it scaffolds the local postman/ directories and installs Postman skills into the project, so your API artifacts live beside your code. It's idempotent, and it works without signing in.

1. Ask Claude Code:

   ✦copy

   ›

   Run `postman init` in this project, then show me what it created.

   Paste this into your agent

2. Confirm Claude runs postman init and that your project now contains a postman/ directory (collections, environments, mocks, and so on), a .postman/resources.yaml file, and an AGENTS.md that points agents at the installed Postman skills.

3. If Claude offers to create a new workspace, decline. The workspace binding in .postman/resources.yaml will be empty for now — you connect your existing workspace in the next step.

If Claude reports a guest session, that's expected — init creates an agent-scoped session so you can start working before connecting your account.

A workspace binding connects your local project to shared context in Postman. This step needs the [Your Name] - AI Basics workspace and its Movies API collection, which you created in the Getting Started with Agent Mode module. Everything from here on builds on that collection, and everything Claude produces is published back to that workspace, so finish that module first if you haven't.

1. Ask Claude Code, replacing [Your Name] with the name you used in that module:

   ✦copy

   ›

   Log me in to Postman and connect this project to my [Your Name] - AI Basics workspace. Pull the workspace so its collections come down as local files.

   Paste this into your agent

2. Authenticate when prompted. Claude will run postman login (browser sign-in), or postman login --with-api-key "$POSTMAN_API_KEY" if you've exported an API key. Get a key at go.postman.co/settings/me/api-keys.

3. Confirm Claude finds the workspace with postman workspace list and runs postman workspace pull <workspace-id>. The pull links the workspace to your repo's origin remote.

4. Check that .postman/resources.yaml now contains your workspace ID, and that postman/collections/ holds your Movies API collection as YAML files.

If Claude reports This git repository has no 'origin' remote, add one with git remote add origin <url> (see Step 1) and ask again.

If Claude can't find your AI Basics workspace, or postman/collections/ is empty after the pull, you don't have the Movies API collection yet. Don't let Claude create a new workspace to get past this. Complete Getting Started with Agent Mode, then come back and ask again.