# profiles

Every install starts from a built-in station profile, a named bundle that marks which stations are selected by default and which are left optional. `brigade profiles` inspects those bundles so you can see what a fresh install wires before you add sidecars. It is read-only: it lists and shows the shipped profiles and never edits config or installs anything.

## Commands

- `brigade profiles list` lists the built-in profiles with selected and optional station counts and a one-line summary.
- `brigade profiles show <profile>` shows one profile by name or alias, printing its aliases, summary, selected stations, and optional stations.

Both accept `--json` for machine-readable output.

```bash
brigade profiles list
brigade profiles show repo
brigade profiles show default        # alias of repo
brigade profiles list --json
```

## The built-in profiles

- `repo` (alias `default`) is the default repo workspace profile, with priority stations and Scout skills selected. It selects the core sidecar set for memory, guard, security, tokens, evidence, search, and skills while leaving heavier or host-global stations optional.
- `workspace` is the operator workspace profile, carrying the repo priority stack plus Scout skills and selecting `mcp` as well.
- `fleet-operator` is a read-only fleet visibility profile; fleet-kit style automation remains optional.

```
brigade profiles:
  repo            selected=8 optional=3  - Default repo workspace profile with priority stations and Scout skills selected.
  workspace       selected=9 optional=2  - Operator workspace profile with the repo priority stack and Scout skills selected.
  fleet-operator  selected=8 optional=3  - Read-only fleet visibility profile; fleet-kit style automation remains optional.
```

An unknown profile name exits non-zero and prints `unknown profile: <name>`.

Profiles are inspection only. Use `brigade stations list` to see the station catalog for a profile, and `brigade add` to wire the sidecars a profile selects.