Skip to main content
Start with the Runloop Quickstart to use the examples below.

Overview

Agent Mounts allow you to attach pre-configured AI agents to your Devbox at creation time. Agents are reusable templates that define how to set up and run AI coding assistants or other automated tools on your Devbox.

Agent Source Types

Runloop supports several types of agent sources:

Creating an Agent Mount

Use the mounts parameter with type: "agent_mount" to attach an agent to your Devbox:

Agent Mount Parameters

Either agent_id or agent_name must be provided, but not both. Using agent_name will mount the most recent agent with that name.

Public Agents

Runloop provides pre-configured public agents that you can mount without creating your own. Public agents are automatically updated to the latest upstream version at least weekly. If you need a specific version, you can pin it by using agent_id instead of agent_name.
Each agent requires API keys to authenticate with its underlying LLM provider. Use Agent Gateways to securely provide these keys without exposing them inside the devbox.
DeepAgents requires sqlite3 to be installed. This is handled automatically on the default devbox and Debian-based blueprints. If you use a custom blueprint, ensure libsqlite3-0 (or equivalent) is installed in your blueprint.
Mount a public agent by name just like any other agent:
You can also list available public agents using the API:

Examples

Mounting an Agent by Name

When you specify agent_name, Runloop will find the most recent agent with that name:

Mounting an Agent by ID

For precise version control, use the agent’s ID:

Mounting a Private Git Agent

For agents sourced from private Git repositories, provide an authentication token:

Agent Path Requirements

The agent_path parameter behavior depends on the agent source type:

Best Practices

  1. Use agent names for flexibility: Using agent_name allows you to update agents without changing your Devbox configuration.
  2. Use agent IDs for reproducibility: When you need exact version control, use agent_id to pin to a specific agent version.
  3. Secure your tokens: Use environment variables or Account Secrets for authentication tokens.
  4. Combine with setup commands: Use setup_commands to run any additional agent initialization after mounting.