Skip to main content
Lists the identities you can spawn an agent as in the current tenant: your own developer identity and any service profiles you are allowed to borrow. Each entry reports whether it is usable right now and, if not, why and how to fix it. Use it before spawn to discover what to pass to the service_profile parameter. 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.

Parameters

This tool takes no parameters. Passing any argument is an error.

Response

Returns an object with a profiles key containing the identities you may spawn as, or [] when you have none. When you have folders, the object also includes a folders key with your complete dashboard folder list. The folders key is absent, not empty, when the caller has no folders.

profiles[]

folders[]

Your complete personal folder list, including folders holding no agent. This is the folder listing every folder tool reads: pass a name to folder, folder_assign, or spawn’s folder parameter. The key is absent when you have no folders.
For your own identity (self), the usable verdict is advisory: the server cannot see the credentials on your local machine, so a spawn as self may still succeed even when self is reported as blocked.

Examples

List spawn identities

Response:

Spawn under a discovered profile

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

Errors