> For the complete documentation index, see [llms.txt](https://docs.warp.dev/llms.txt).
> Markdown versions of each page are available by appending .md to any URL.

# Agent profiles

Use agent profiles with the Oz CLI to control what the agent can access, how it behaves, and where it can act.

Agent profiles control what the agent can do, how it behaves, and where it can act when running from the Oz CLI. Create profiles in the Warp app to configure file access, command execution, MCP server usage, model selection, and directory permissions, then reference them by ID in CLI commands.

Agent profiles control three things:

-   **What the agent can do** — file access, command execution, and MCP server usage
-   **How the agent works** — model selection, autonomy level, and response style
-   **Where the agent can act** — directory allowlists and denylists

You can create and configure agent profiles in the Warp app. For detailed instructions, see [Agent Profiles & Permissions](https://docs.warp.dev/agents/capabilities/agent-profiles-permissions/).

Agent profiles are automatically synced to each host where you have Warp installed, so you can use them remotely as well.

For CLI usage, create a dedicated profile that permits the directories, commands, and MCP servers required by the workflow. The default profile loads available MCP servers. Command execution uses **Agent decides**, and its denylist still blocks matching commands. Add run-scoped servers with `--mcp`, or select another profile to use its MCP permissions. See [MCP servers](https://docs.warp.dev/reference/cli/mcp-servers/) for details.

## Using a profile with the CLI

1.  Find the profile ID using `oz agent profile list`:

```sh
$ oz agent profile list
+--------------+------------------------+
| Name         | ID                     |
+=======================================+
| Default      | AnTb02PZfrkVC9l4V15eH1 |
|--------------+------------------------|
| Coding       | CWhozDJPdPCsjJ1pSG0HCN |
|--------------+------------------------|
| Command Line | hV6n5dNm7ThQVlOiPF8DLS |
+--------------+------------------------+
```

2.  Pass that ID using the `--profile` flag:

```sh
$ oz agent run --profile CWhozDJPdPCsjJ1pSG0HCN --prompt "update my CI pipeline to use nextest"
```

Note

The `--profile` flag is available on `oz agent run` only. Cloud runs (`oz agent run-cloud`) do not use agent profiles.