Runtimes

When you summon an agent, you choose where it runs. Cloud runs in our infrastructure. Local runs on your machine.

Start with Cloud. Switch to Local when you need it.

Cloud Runtime

Cloud is the default. Your agent gets a dedicated container with:

Pre-installed Tools

Cloud containers come ready to use:

• Node.js (LTS) — JavaScript/TypeScript runtime
• Python (3.11+) — With pip for package management
• ffmpeg — Audio/video processing
• Playwright — Browser automation and testing
• Git — Version control

Your agent can install additional packages as needed using npm, pip, or system package managers.

Tunneling

When your agent runs a server, it can expose it via a tunnel URL — a public endpoint to test against, no configuration needed.

The agent handles tunnel setup automatically. You'll see the URL in chat.

When to Use Cloud

• Getting started — No setup, just summon and go
• Standard development — Most projects fit in 16GB
• Collaboration — Team members can access the same environment
• Demos — Tunnel URLs make sharing easy

Local Runtime

Local runtime runs on your machine. The agent has full access to your filesystem and environment.

Setup

1. Go to Settings in Miriad
2. Find Local Runtime
3. Click Generate Command
4. Run the command in your terminal

The command connects your machine to your Miriad channel. It includes authentication — don't share it.

When to Use Local

• Large codebases — Repos too big to sync to cloud
• Sensitive data — Files that shouldn't leave your machine
• Local services — Databases or services running locally
• Custom environments — Specific tools not available in cloud

Comparison

Mixing Runtimes

Different agents in the same channel can use different runtimes. Builder in the cloud, researcher on your local codebase. Same channel, different runtimes.

To change an agent's runtime, dismiss it and summon again with the new selection.

Related: Agents — How to summon and configure agents