murmur spawn-profiles

Lists the identities you can spawn an agent as in the configured tenant: your own developer identity and any 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. Profiles you cannot assume are omitted. murmur get service-profile instead lists service profiles you can read with service-profile.read, regardless of whether you can assume them. Neither listing confers the permission used by the other.

Synopsis

murmur spawn-profiles

This command takes no arguments.

Flags

Name	Type	Required	Description
`--json`	bool	no	Print the `ListSpawnProfilesResponse` as JSON instead of the table. Default: `false`.

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. For self, DETAIL lists each unmet requirement as reason (remediation), joined by ; . For a service profile, DETAIL is 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      Tags and publishes releases

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. When you have folders, the table is followed by them, so a spawn can land in a folder you already have. A caller with no folders sees only the identity table:

Your folders (murmur spawn --folder <name>):
  Infra
  Review queue

Use murmur folder to list folders with their agent counts or to create, rename, delete, and file agents into folders.

Examples

List spawn identities

murmur spawn-profiles

Spawn under a usable profile

After confirming ci-builder is usable, pass its account to murmur spawn:

murmur spawn --service-profile ci-builder nightly-build Run the nightly build and open a PR

Errors

Code	Meaning	What to do
`list spawn profiles: ...`	The request to the Murmur API failed. The rest of the message carries the cause.	Check your network and `murmur.yaml` configuration.
`UNAUTHENTICATED`	Identity token is missing or expired.	Run `murmur login` or check your `murmur.local.yaml`.

spawn_profiles: equivalent MCP tool
murmur spawn: spawn an agent, optionally under a service profile
murmur folder ls: your dashboard folders with agent counts
murmur get: read or list catalog resources, including service profiles
Service profiles: bot identities agents can run as

Getting Started

Core Concepts

Guides

murmur spawn-profiles

Synopsis

Flags

Output

Examples

List spawn identities

Spawn under a usable profile

Errors

​Synopsis

​Flags

​Output

​Examples

​List spawn identities

​Spawn under a usable profile

​Errors

​Related

Synopsis

Flags

Output

Examples

List spawn identities

Spawn under a usable profile

Errors

Related