Skip to main content
An alias gives an agent port a stable URL. The ephemeral port-proxy subdomain changes every time an agent is spawned. An alias lets you reach the same service at a predictable address such as github_app-acme-dashboard.alias.port.murmur.dev. Each alias maps a name to a specific agent and port. When a request arrives at the alias subdomain, the port proxy resolves the alias to the target agent and forwards traffic to the specified port on that agent’s VM.

Fields

The agent_id.account must match the caller’s username. You can only create aliases that point to your own agents.

URL format

The alias subdomain follows the pattern:
For example, an alias named dashboard in the acme GitHub App tenant resolves to:
The alias name can contain hyphens. Each hyphen inside a part (provider, org, or name) is doubled in the subdomain, and a single hyphen separates the parts: my-cool-app produces github_app-acme-my--cool--app.alias.port.murmur.dev.

Examples

Creating an alias

Updating an alias to point to a different agent

The update succeeds because the agent_id.account matches the existing alias’s owner. Attempting to reassign an alias owned by a different account fails with ALREADY_EXISTS.

Listing aliases

The list prints one name per line, with no header.

Reading a single alias

Errors

  • Catalog: concept overview of catalog resources
  • Agents: the resource an alias routes traffic to
  • murmur set: CLI command for creating and updating catalog resources
  • murmur get: CLI command for reading catalog resources