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

# murmur spawn-profiles

> List the identities you can spawn an agent as — your own developer identity and any service profiles you may borrow — with a usable/blocked verdict for each.

Lists the identities you can spawn an [agent](/concepts/agents) as in the configured tenant: your own developer identity and any [service profiles](/concepts/service-profiles) you are allowed to borrow. Each entry shows whether it is usable now and, if not, why and how to fix it. It is the discovery companion to [`murmur spawn --service-profile`](/cli/spawn).

Profiles you cannot assume are omitted. For the raw catalog listing of every defined profile, use [`murmur get service-profile`](/cli/get) instead — that answers a different question ("what profiles exist") and is not filtered by what you may borrow.

## Synopsis

```bash theme={null}
murmur spawn-profiles
```

This command takes no arguments or flags.

## Output

A table of identities. The `TYPE` column is `self` (your own developer identity) or `service-profile` (a borrowable profile). `USABLE` is `yes` or `no`. `DETAIL` carries each unmet requirement as `reason (remediation)` for a blocked identity, or the profile's description.

```
TYPE             ACCOUNT          USABLE  DETAIL
self             acme-dev         yes
service-profile  ci-builder       yes     Opens PRs as the CI bot
service-profile  release-manager  no      missing service-profile.assume permission (ask an admin to grant you service-profile.assume on release-manager)
```

When `self` is shown as unusable, a footnote reminds you that the verdict is advisory: the server cannot see your local credentials, so a spawn as self may still succeed.

## Examples

### List spawn identities

```bash theme={null}
murmur spawn-profiles
```

### Spawn under a usable profile

After confirming `ci-builder` is usable, pass its account to [`murmur spawn`](/cli/spawn):

```bash theme={null}
murmur spawn --service-profile ci-builder nightly-build Run the nightly build and open a PR
```

## Errors

| Code              | Meaning                                 | What to do                                                        |
| ----------------- | --------------------------------------- | ----------------------------------------------------------------- |
| `connect to API`  | The CLI could not reach the Murmur API. | Check your network and `murmur.yaml` configuration.               |
| `UNAUTHENTICATED` | Identity token is missing or expired.   | Run [`murmur auth`](/cli/auth) or check your `murmur.local.yaml`. |

## Related

* [`spawn_profiles`](/mcp-server/spawn-profiles) — equivalent MCP tool
* [`murmur spawn`](/cli/spawn) — spawn an agent, optionally under a service profile
* [`murmur get`](/cli/get) — read or list catalog resources, including service profiles
* [Service profiles](/concepts/service-profiles) — bot identities agents can run as