> ## Documentation Index
> Fetch the complete documentation index at: https://docs.blocks.team/llms.txt
> Use this file to discover all available pages before exploring further.

# Profiles

> Pick a model, MCPs, and auth method on a per-invocation basis

## Overview

Profiles let you bundle an agent, model, and configuration under a single slash command. Invoke any profile with `@blocks /<profile> ...` — the same syntax used for skills and plan mode — to run a specific agent with a specific model, auth method, and MCP set.

For example, `/quick` could map to the `claude` agent on the `haiku` model with Bedrock auth and no MCP servers.

Each agent ships with an implicit default profile keyed by the agent's own keyword (e.g. `/claude`, `/codex`) that uses the agent-level settings.

## Why use profiles

* **Pin a model** for a specific kind of work (e.g. `/sonnet-latest`, `/opus`).
* **Restrict an invocation** to a subset of MCP servers (e.g. a read-only DB profile).
* **Switch auth method** (API Key vs OAuth vs AWS Bedrock) without changing the agent default.

## Creating a profile

1. Go to **Dashboard → Agents → \[Your Agent]**.
2. In the **Profiles** section click **Add Profile**.
3. Set a **Keyword** — this becomes the slash trigger. Keywords are alphanumeric, underscore, or hyphen only, and must be unique within the workspace.
4. Configure the fields described below.
5. Click **Create**.

## What you can configure

* **Keyword** — the slash trigger (`/<profile>`).
* **Authentication method** — choose between the agent's supported modes (e.g. API Key, OAuth, AWS Bedrock for Claude Code).
* **Model** — pin a specific model from the agent's available models.
* **MCP servers** — opt into a subset of MCP servers, or leave the override off to inherit the agent default.

## Using a profile

Invoke a profile the same way you invoke any other slash command:

```
@blocks /sonnet help me fix the conflict at src/app.ts
@blocks /sonnet /review-security
```

Profile keywords compose with skills and plan mode.

## Default profile

Each agent has an implicit default profile that matches the agent's own keyword (`/claude`, `/codex`, etc.) and uses the agent-level settings. The Profiles list in the dashboard labels this row as **Default**.

## Managing profiles

Edit or delete profiles from the same **Profiles** section. Changes take effect on the next invocation.