AgentClash
K

Getting Started

Self-Host Starter

Bring up the local AgentClash stack with the repo’s existing scripts and understand which dependencies are mandatory versus optional.

This is the shortest honest path to a local AgentClash environment today. It is based on the repo’s existing development scripts, not an imagined one-click installer.

Warning

The repo does not currently ship a Helm chart or a polished production installer. What it does ship is a local stack script plus documented Railway deployment building blocks for the backend.

Prerequisites

  • Go 1.25+
  • Docker
  • Temporal CLI
  • Node.js 20+
  • pnpm
  • psql

1. Start the local stack

From the repo root:

bash
./scripts/dev/start-local-stack.sh

This script starts PostgreSQL and Redis, applies migrations, launches the Temporal dev server if needed, then starts the API server and worker. Logs are written under /tmp/agentclash-local-stack/.

2. Start the web app

bash
1cd web
2pnpm install
3pnpm dev

The web app runs at http://localhost:3000.

Warning

web/ ships both lockfiles (pnpm-lock.yaml and package-lock.json). Local dev uses pnpm, but CI installs with npm ci against package-lock.json. If you change a frontend dependency, update package-lock.json too or the frontend CI job will fail.

3. Seed a runnable fixture

Back in the repo root:

bash
1./scripts/dev/seed-local-run-fixture.sh
2./scripts/dev/curl-create-run.sh

Warning

seed-local-run-fixture.sh is destructive to your local dev database. It TRUNCATEs the fixture tables (challenge packs, organizations, users, model catalog entries) before inserting deterministic IDs. Only run it against a throwaway local Postgres, never a database with data you care about.

Without a real sandbox provider such as E2B, native runs can still be created, but the model-backed execution path will not complete successfully.

Required vs optional services

  • Required: PostgreSQL, Temporal, API server, worker
  • Optional: Redis for event fanout and rate limiting
  • Optional: E2B for sandboxed native execution
  • Optional: S3-compatible storage for production artifact storage

Production notes

The repo’s documented production building blocks today are:

  • Railway for the API server and worker
  • Temporal Cloud for orchestration
  • Vercel for web/
  • S3-compatible storage for artifacts

Verification

You should be able to hit:

bash
curl http://localhost:8080/healthz

Then open http://localhost:3000.

See also

PreviousQuickstartNextFirst Eval