> For clean Markdown content of this page, append .md to this URL. For the complete documentation index, see https://learning.postman.com/llms.txt.

# Develop with a coding agent using Native Git

Using the [Postman CLI](/docs/postman-cli/postman-cli-overview/), a coding agent can do the same work with Postman that a developer would otherwise do in the Postman app. This includes setting up a project, building against your API, and syncing the results to a Postman Workspace. That workspace is what makes the agent's work visible to a teammate, a reviewer, or another agent, so they can act on it without re-running anything themselves.

This topic walks through the end-to-end workflow: setting up a project for a coding agent, keeping its skills current, connecting your workspace, working with your API, and reviewing it in a shared workspace.

## Before you begin

* Have a Git repository for the API your agent will work on. It can be empty, contain only source code, or already have an OpenAPI, Swagger, or AsyncAPI specification.
* [Install the Postman CLI](/docs/postman-cli/postman-cli-installation/).
* [Install the Postman plugin](/docs/reference/developer-resources/postman-plugin/) for your coding agent.
* (Optional) [Sign in](/docs/postman-cli/postman-cli-auth#postman-login) to Postman with the `postman login` command.

## Set up the project

Run this command yourself, before your agent has any Postman skills to act on your behalf. From the root of your repository, run the [`postman init`](/docs/postman-cli/postman-cli-init/) command.

```bash
postman init
```

This creates the [Native Git](/docs/use/native-git/overview/) project structure, adopts an existing API specification if you have one, and installs agent skills from the [Postman skills repository](https://github.com/postmanlabs/skills). This enables your coding agent to work with the Postman CLI the way an experienced developer would.

## Keep agent skills current

Your agent can check whether its Postman skills are current on its own. You can also ask it directly:

Check whether my Postman CLI skills are up to date.

This runs [`postman skills status`](/docs/postman-cli/postman-cli-skills/#postman-skills-status). If a skill is behind, the agent asks before running [`postman skills update`](/docs/postman-cli/postman-cli-skills/#postman-skills-update) to fetch the latest version. Learn more at [Skills commands](/docs/postman-cli/postman-cli-skills/).

## Connect your workspace

Before your agent's work can be reviewed in Postman, your project needs to be connected to a workspace. How you connect it depends on whether you signed in before running `postman init`.

### If you signed in

Signing in before running `postman init` doesn't guarantee your project is connected to a workspace. The `postman init` command only offers to create one. It skips that offer if you passed `--no-cloud` or declined the prompt. If you're not sure it's connected, ask your agent to check:

Create a Postman workspace and connect this project to it.

This runs [`postman workspace create`](/docs/postman-cli/postman-cli-workspace/#postman-workspace-create). Once your project is connected, ask your agent to sync its changes:

Push my changes to Postman.

This runs [`postman workspace push`](/docs/postman-cli/postman-cli-workspace/#postman-workspace-push), which validates your local files and synchronizes them with the connected workspace. Run it again any time your agent's changes need to reach Postman Cloud.

### If you started as a guest

If you ran `postman init` signed out, your agent has been building against a guest workspace instead. This is a local, Git-tracked project that's a real [Local View](/docs/use/native-git/overview/), just not yet connected to a Postman Cloud workspace. Ask your agent to connect it, so your work stays under your account instead of remaining local:

Sign me up for Postman and connect this project to my account.

This runs [`postman signup`](/docs/postman-cli/postman-cli-auth/#postman-signup), which opens a browser on an interactive terminal and signs the CLI in when sign-up finishes. In environments where the browser can't redirect back to the CLI, it prints a single-use sign-up URL instead. Once you've signed up, sync further changes the same way as the signed-in path, by asking your agent to push them.

## Work with your API

Once your agent's environment is set up, you can ask it to do the same work with the Postman CLI that a developer would otherwise do in the Postman app. For example:

Run my collection against staging and tell me if anything fails.

Depending on the task, this might run a spec check, a collection run against a real API or a [mock](/docs/postman-cli/postman-cli-mock/), a [monitor or performance test](/docs/postman-cli/postman-cli-monitoring/), or [client SDK generation](/docs/postman-cli/postman-cli-sdk-gen/). See the [full list of Postman CLI commands](/docs/postman-cli/postman-cli-options/) for what else your agent can do.

The CLI prints results in the terminal, and supported linked resources can also report them to Postman Cloud, so your agent can inspect the outcome and decide what to do next.