Organizations
Your GitHub org is your tenant. When an org admin installs the Macroscope GitHub App, it creates the tenant boundary. All agents, workspaces, secrets, and catalog entries are namespaced to your org.- Personal tenants exist automatically for every authenticated GitHub user
- Organization tenants exist when the Macroscope GitHub App is installed on a GitHub org
Users
Users log in to Murmur with their GitHub account. They automatically have access to any organization that has installed the Macroscope App.Glossary
Placements
Where agents run, which cloud account, region, and network. Platform placements are preconfigured; customer placements let you run agents in your own cloud.Environments
The VM compute shape: machine type, disk size. Each workspace references one environment.Recipes
A base image plus a provisioning script that installs your toolchain. Baking a recipe produces an image.Images
The result of baking a recipe. Agents boot from images, so everything your provisioning script installs is available immediately.Workspaces
The top-level organizational unit within a tenant. Groups repositories, references an environment and placement, and defines defaults for agents spawned within it.Agents
An autonomous Claude Code (or Codex) session running on a cloud VM. Agents clone repos, execute tasks, open pull requests, and can spawn child agents recursively.Agent Personas
Reusable templates that define an agent’s prompt, model, tools, and constraints. Use them to configure roles such as an architect.Pools
Pre-booted VMs that let agents start in seconds. The platform maintains warm VMs ready for instant assignment.Flights
Markdown documents that define multi-agent workflows: task dependencies, personas, and event triggers. A pilot agent reads the flight and orchestrates the sub-agents.Events
Real-time GitHub events delivered to running agents: PR comments, reviews, CI results, and file changes. Agents react autonomously without polling.Secrets
Credentials and sensitive values: tenant-wide, per-developer, or per-spawn. Encrypted at rest, delivered as environment variables on agent VMs.Service Profiles
Non-human identities for automated agents: flights, scheduled tasks, and bots that operate on behalf of the org.More
Security
Authentication, authorization, and encryption: how Murmur protects credentials and enforces access control.Catalog resources
The resource registry that stores all Murmur configuration, including workspaces, environments, placements, secrets, and more. Each kind is documented field by field.CLI
Install and configure themurmur command-line interface. Every command documented with flags, examples, and errors.