A service profile is a bot identity that agents run under when they operate on behalf of the org rather than a specific developer. Instead of using your GitHub token and Claude key, the agent authenticates with the profile’s credentials and commits as a bot author.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.
When to use a service profile
Developer-spawned agents run as you — your GitHub token, your Claude subscription, your git identity. That works for interactive work. But automated agents — flights triggered by events, scheduled tasks, merge-queue processors — need an identity that doesn’t belong to any individual. A service profile provides:- Bot git identity — commits show the GitHub App’s bot avatar, not a developer’s
- Org-scoped credentials — an Anthropic API key owned by the team, not an individual
- Access grants — control who can spawn agents with this profile
What a service profile contains
Using a service profile
From the dashboard — the spawn dialog shows an identity picker. Select the profile instead of your personal identity. From flights — setservice_profile in the flight frontmatter. Every agent the flight launches inherits the profile’s identity.
From the CLI — pass --service-profile on murmur spawn.
See the service profiles guide for step-by-step setup from the dashboard.
| Type | Page |
|---|---|
| Guide | Create a service profile |
| Reference | service-profile |
| Concept | Agents |
| Concept | Flights |
| Concept | Secrets |
| Concept | Authorization |