Skip to main content
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. For the raw catalog listing of every defined profile, use murmur get service-profile instead — that answers a different question (“what profiles exist”) and is not filtered by what you may borrow.

​
Synopsis

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

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

CodeMeaningWhat to do
connect to APIThe CLI could not reach the Murmur API.Check your network and murmur.yaml configuration.
UNAUTHENTICATEDIdentity token is missing or expired.Run murmur auth or check your murmur.local.yaml.