Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.runloop.ai/llms.txt

Use this file to discover all available pages before exploring further.

The Runloop Dashboard is a powerful web-based interface designed to help developers manage, monitor, and optimize their AI-powered coding environments. It serves as a central command center for your Devboxes, offering intuitive tools for deployment, monitoring, and troubleshooting.

​
Getting Started

  1. Log in to your Runloop account at https://platform.runloop.ai
  2. Navigate through the sidebar to access different tools and features

​
Key Features

  1. Comprehensive Search: Quickly find specific Devboxes using metadata and status filters.
  2. Log Viewer: Deep dive into Devbox logs with real-time streaming and querying.
  3. Resource Monitoring: Track and optimize CPU, memory, and storage usage across your Devboxes.
  4. Runloop Shell: Look inside any running devbox using shell access, right from the UI.

​
Essential Dashboard Tools

​
Runloop Shell

The Runloop Shell allows you to manage active Devboxes, execute commands, and troubleshoot issues without leaving your browser. Use the filter functionality to find the right Devboxes Devboxes:
  • By status: status:running
  • By metadata: metadata.project:ai-refactor
  • By time range: created_after:2023-01-01

​
Log Analysis

Access and analyze logs for any Devbox:
  1. Select a Devbox from the dashboard
  2. Navigate to the “Logs” tab
  3. Use built-in filters to isolate specific log entries
  4. Enable real-time streaming for active monitoring

​
Resource Optimization (Coming Soon)

Monitor resource utilization:
  1. View historical usage graphs
  2. Receive optimization recommendations

​
Security and API Keys

Manage your Runloop API keys from the Settings page in the dashboard. API keys authenticate your SDK and CLI requests.

​
Key Types

Runloop supports two types of API keys:
  • Secret keys (ak_) provide full access to all resources in your account. Use these for local development or trusted environments where you need unrestricted access.
  • Restricted keys (rk_) are scoped to specific resource types and access levels. Use these for CI/CD pipelines, monitoring dashboards, third-party integrations, or any context where you want to limit what the key can do.

​
Creating Restricted Keys

Restricted keys let you define exactly which resources the key can access and at what level:
Access LevelDescription
NoneNo access to the resource type
ReadCan list and view resources
WriteCan create, modify, and delete resources (includes read access)
You can set scopes for the following resource types: Devboxes, Blueprints, Snapshots, Benchmarks, Scenarios, Repo Connections, Agents, Objects, and Account. Any resource type you don’t explicitly configure defaults to no access.

​
Key Lifecycle

  • Keys are created and managed exclusively in the dashboard
  • The raw secret is displayed only once at creation: copy it immediately
  • Scopes are immutable after creation. To change permissions, delete the key and create a new one
  • Keys support optional expiration dates
  • The dashboard displays when each key was last used

​
Example Use Cases

ScenarioRecommended Scopes
CI/CD pipeline provisioning devboxes from existing blueprintsDevboxes: write, Blueprints: read, Snapshots: read
Read-only monitoring dashboardDevboxes: read, Blueprints: read
Automated benchmark runnerBenchmarks: write, Scenarios: read, Devboxes: write
Third-party integration with limited accessOnly the specific resources the integration requires
For production automation, prefer restricted keys over secret keys. Granting only the permissions a workflow needs reduces the impact if a key is ever exposed.