CloudClaw Documentation

Introduction

CloudClaw is an enterprise-grade open source AI Agent platform built with Spring Boot 3.4 + Spring AI 1.1 + Vue 3.

Core design principles:

Current version: v1.0.4 | License: Apache 2.0

Installation

Requirements

ComponentRequirement
Java17+
Maven3.9+ (build only)
PostgreSQL16+ (cluster mode only)
Redis7+ (cluster mode only)

Standalone Mode (Recommended for Getting Started)

Zero external dependencies. Uses SQLite + in-memory message queue. Ideal for development, evaluation, and personal use.

# 1. Clone the project
git clone https://github.com/cloudclaw-dev/cloudclaw.git
cd cloudclaw

# 2. Build
mvn clean package -DskipTests

# 3. Set secrets (required)
export JWT_SECRET="your-secret-key-at-least-32-bytes-long"
export CRYPTO_SECRET="your-crypto-key-at-least-32-bytes"

# 4. Start
java -jar cloudclaw-app/target/cloudclaw-app-1.0.3.jar

⚠️ Security Note: JWT_SECRET and CRYPTO_SECRET are required. Standalone mode includes default values for demo only — always use strong random strings in production.

After starting, visit http://localhost:8080/. Default admin account: admin / admin123

Cluster Mode (Recommended for Production)

Uses PostgreSQL + Redis. Supports horizontal scaling.

# 1. Prepare database
createdb cloudclaw

# 2. Build and start
mvn clean package -DskipTests
export JWT_SECRET="your-secret"
export CRYPTO_SECRET="your-crypto"
java -jar cloudclaw-app/target/cloudclaw-app-1.0.3.jar \
  --spring.profiles.active=cluster

Configure database and Redis in application-cluster.yml:

spring:
  datasource:
    url: jdbc:postgresql://localhost:5432/cloudclaw
    username: postgres
    password: your-password
  data:
    redis:
      host: localhost
      port: 6379

Quick Start

First-time usage flow after starting:

  1. Login — Sign in with admin / admin123
  2. Configure LLM — Go to "LLM Management" and add your API Key (supports DeepSeek, Qwen, GLM, Ollama, and any OpenAI-compatible API)
  3. Create Agent — Go to "Agent Management", create a new Agent with system prompt and model
  4. Start Chatting — Switch to the "Chat" page, select an Agent and start

Agent Management

Agent is the core entity in CloudClaw. Each Agent has independent configuration:

FieldDescription
NameDisplay name of the Agent
System PromptDefines the Agent's role and behavior
ModelLLM model to use (e.g. deepseek-chat, qwen-plus)
TemperatureControls output randomness. 0 = deterministic, 1 = maximum randomness
Max TokensMaximum length of a single response
MCP ServersBound MCP tool servers
SkillsBound Skill skills
WorkflowMulti-Agent orchestration mode (optional)

The Agent form is organized into 4 tabs: Basic / Model / Workflow / Tools

Chat

Chat Interface

Session Management

Multi-Agent Orchestration

CloudClaw provides 5 built-in orchestration modes for multi-agent collaboration:

ModeDescriptionUse Case
PipelineSequential execution, output feeds into nextPipeline processing, multi-step tasks
ParallelMultiple agents run simultaneously, results mergedParallel analysis, multi-angle evaluation
RouterLLM intent classification routes to best sub-agentCustomer service routing, task dispatch
SupervisorPlanner/reviewer agent delegates tasks iterativelyComplex project management, quality control
HandoffConversation transfers between agents with contextCustomer service transfer, multi-expert consultation

Each node supports independent configuration: model, system prompt, MCP servers, skills.

MCP Gateway

Built-in MCP (Model Context Protocol) gateway enables agents to call external tools through a standard protocol.

Features

Configure MCP Servers

Add servers in the admin "MCP Servers" page. Required fields:

Memory Service

Provides persistent memory for agents, supporting cross-session context retention.

Supported Engines

EngineDescriptionUse Case
jdbcDatabase-backed memory with vector searchRecommended default, works out of the box
mem0Integrates third-party Mem0 memory serviceAdvanced memory capabilities

Configuration: cloudclaw.memory.engine=jdbc

Skill System

Adopts the Claude Agent Skill standard with progressive loading:

Auto-discovery via @Tool annotation.

Code Sandbox

Secure isolated code execution environment with multiple backends:

BackendDescription
LOCALLocal process execution (default)
DOCKERDocker container isolation (Testcontainers)
E2BE2B cloud sandbox

Supported Languages

Python, JavaScript, Shell, Java

Execution Modes

Security Limits

LLM Management

Multi-provider model management with a unified configuration entry.

Features

Supported Models

DeepSeek, Qwen, GLM, Ollama local models, and any OpenAI-compatible API. Configure API Key, then select the model in Agent settings.

Configuration Reference

All settings are in application.yml or application-cluster.yml. Environment variables override file values.

PropertyDefaultDescription
server.port8080Server port
spring.profiles.activestandaloneMode: standalone or cluster
cloudclaw.jwt.secretBuilt-in defaultJWT signing key (env: JWT_SECRET)
cloudclaw.jwt.access-token-ttl2hAccess token TTL
cloudclaw.jwt.refresh-token-ttl7dRefresh token TTL
cloudclaw.crypto.secretBuilt-in defaultEncryption key (env: CRYPTO_SECRET)
cloudclaw.memory.enginejdbcMemory engine: jdbc or mem0
cloudclaw.mq.providerinmemoryMessage queue: inmemory or redis
cloudclaw.mcp.pool.max-connections-per-server5Max MCP connections per server
cloudclaw.cache.session-ttl30mSession cache TTL
cloudclaw.sandbox.default-backendLOCALSandbox backend
cloudclaw.sandbox.default-modeSTATELESSSandbox mode
cloudclaw.sandbox.default-timeout30sDefault execution timeout
cloudclaw.sandbox.max-timeout5mMaximum execution timeout

Docker Deployment

Standalone Docker

docker compose -f docker-compose.standalone.yml up -d

Requires JWT_SECRET environment variable.

Cluster Docker (PostgreSQL + Redis)

# 1. Create .env file
cp .env.example .env
# Edit .env and fill in secrets

# 2. Start all services
docker compose up -d

Includes PostgreSQL (with pgvector), Redis, and CloudClaw containers.

Build Custom Image

# Full build (frontend + backend)
docker build -t cloudclaw .

# Or use pre-built JAR
docker build -f Dockerfile.simple -t cloudclaw .

Cluster Mode

Architecture Comparison

StandaloneCluster
DatabaseSQLitePostgreSQL 16+
CacheCaffeine (local)Redis 7+
Message QueueIn-memoryRedis Streams
ScalingNot supportedSupported
Use CaseDev, evaluation, personalProduction, teams, enterprise

Database Migration

CloudClaw uses Flyway for automatic database migration:

All tables are created automatically on first start. Subsequent upgrades migrate automatically.

Users & Permissions

Roles

RolePermission
ADMINFull admin access: user management, agent management, system monitoring, logs
USERChat interface, session management, personal memory

Authentication

Admin Features

Need more help? Visit GitHub Issues or Discussions.