Skip to content

trading-desk

Directory actions

More options

Directory actions

More options

Latest commit

 

History

History
 
 

trading-desk

README.md

Trading Desk Example

A reference pod showing seven OpenClaw agents running as a governed fleet — each with a Discord presence, scheduled tasks, and shared infrastructure context.

What's in the box

File Purpose
Clawfile Shared agent image — all trader agents build from this
claw-pod.yml Pod definition — per-agent handles, surfaces, invoke schedules
Dockerfile.openclaw-base Builds the local openclaw:latest base image
Dockerfile.trading-api Mock trading API with skill label emission
entrypoint.sh Baked into the base image — starts gateway, sends greeting
agents/ Per-agent AGENTS.md contracts
policy/ Shared skills (risk limits, approval workflow)

Prerequisites

  • Docker with Compose V2 (docker compose version)
  • claw binary on PATH (go build -o bin/claw ./cmd/claw)
  • Discord bot tokens — one per agent — plus server/channel IDs

.env file

Copy .env.example and fill in real values:

TIVERTON_BOT_TOKEN=Bot ...
WESTIN_BOT_TOKEN=Bot ...
DUNDAS_BOT_TOKEN=Bot ...
BOULTON_BOT_TOKEN=Bot ...
GERRARD_BOT_TOKEN=Bot ...
LOGAN_BOT_TOKEN=Bot ...
ALLEN_BOT_TOKEN=Bot ...

DISCORD_GUILD_ID=...
DISCORD_TRADING_FLOOR_CHANNEL=...
DISCORD_INFRA_CHANNEL=...

POSTGRES_PASSWORD=...

Running

# Build base image once (skip if openclaw:latest exists)
docker build -t openclaw:latest -f Dockerfile.openclaw-base .

# Deploy the full fleet
claw compose up claw-pod.yml

# Check health
docker exec trading-desk-tiverton-1 openclaw health --json

# Tail logs
docker compose -f compose.generated.yml logs -f tiverton

Spike integration test

cmd/claw/spike_test.go is a full end-to-end test that:

  1. Builds all images (Clawfile → trading-desk:latest, mock trading API)
  2. Runs claw compose up on a pre-expanded pod YAML
  3. Asserts generated artifacts — openclaw.json structure, jobs.json channel IDs, compose mounts
  4. Waits for containers to be healthy
  5. Polls the Discord channel REST API to confirm startup greetings arrived

Requirements:

  • Docker running
  • Real bot tokens in examples/trading-desk/.env (TIVERTON_BOT_TOKEN and WESTIN_BOT_TOKEN at minimum)
  • Internet access from Docker containers (no internal-only Docker Desktop network mode)

Run:

go test -tags spike -v -run TestSpikeComposeUp -timeout 300s ./cmd/claw/

The test skips automatically if TIVERTON_BOT_TOKEN is not set in .env.

What it verifies:

Assertion What it checks
openclaw.json structure channels.discord.token, guilds keyed by guild ID
jobs.json structure agentTurn payload, delivery.to = resolved channel ID
Compose mounts /app/config directory, /app/state/cron directory
Container readability /app/config/openclaw.json, /app/state/cron/jobs.json, /claw/AGENTS.md
Skills populated /claw/skills/ contains extracted skill files
Health check Docker healthcheck reports healthy
Discord greetings Messages appear in the channel via REST API polling