Skip to content
Warp

Agents > Oz CLI

Agent profiles

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

Open in ChatGPT ↗
Ask ChatGPT about this page
Open in Claude ↗
Ask Claude about this page
Copied!

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.

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

Using a profile with the CLI

Section titled “Using a profile with the CLI”
  1. Find the profile ID using oz agent profile list:
Terminal window
$ oz agent profile list
+--------------+------------------------+
| Name         | ID                     |
+=======================================+
| Default      | AnTb02PZfrkVC9l4V15eH1 |
|--------------+------------------------|
| Coding       | CWhozDJPdPCsjJ1pSG0HCN |
|--------------+------------------------|
| Command Line | hV6n5dNm7ThQVlOiPF8DLS |
+--------------+------------------------+
  1. Pass that ID using the --profile flag:
Terminal window
$ oz agent run --profile CWhozDJPdPCsjJ1pSG0HCN --prompt "update my CI pipeline to use nextest"