Skip to main content
This guide walks you through setting up the Agent Control Plane locally for development purposes.

Prerequisites

  • Docker and Docker Compose installed

Quick Start

1. Configure Environment Variables

Copy the example environment file:
The .env file comes pre-configured with defaults for local development. Most values work out of the box, but you must fill in these required variables:
All other values (database, Redis, Temporal) have sensible defaults for local development.

2. Start the Services

This command builds and starts all services. Database migrations run automatically on startup.

Service URLs

Once running, the following services are available:

Makefile Commands

The project includes a comprehensive Makefile for common operations:

Core Commands

Database Migrations

Example - Creating a new migration:

Architecture Overview

The local development stack includes:

Services

  • Control Plane API - FastAPI application serving the REST API
  • Temporal Worker - Processes workflow executions
  • Temporal - Workflow orchestration engine
  • Temporal UI - Web interface for monitoring workflows
  • PostgreSQL - Primary database
  • Redis - Caching and session storage

Environment Variables Reference

Database Configuration

Redis Configuration

Temporal Configuration

API Configuration

External Services (Required)

Temporal Worker Configuration

Optional Services

Development Workflow

Viewing Logs

Follow logs from all services:
Or view logs for a specific service:

Accessing the Database

Connect to PostgreSQL:

Running Commands in the API Container

Restarting After Code Changes

The API container mounts the source code as a volume, so most changes are reflected immediately. For changes requiring a restart:

Troubleshooting

Services Won’t Start

  1. Check if ports are already in use:
  2. Clean up and restart:

Database Connection Issues

  1. Verify PostgreSQL is healthy:
  2. Check logs:

Temporal Workflow Issues

  1. Access the Temporal UI at http://localhost:8080
  2. Check worker logs:

Next Steps