QuantumByte

npm install (web) + creates Python venvs and pip install (orch, worker). 3 db-up docker compose up -d --wait — starts Postgres, Redis, minio + creates the qb-assets bucket, waits until all healthy. 4 migrate Applies Prisma migrations. 5 generate Generates the Prisma client into apps/web/src/generated/prisma . Fill in secrets make env only creates the web .env . The worker and orchestrator read env from their own .env files (or the process environment) — copy their examples: cp apps/worker/.env.example apps/worker/.env cp apps/orchestrator/.env.example apps/orchestrator/.env Then set, in apps/worker/.env : ANTHROPIC_API_KEY — a real sk-ant-… key. Or leave the sk-ant-... placeholder to fall back to your claude.ai login at ~/.claude/.credentials.json (only a real-looking key is passed to the SDK). GIT_PAT — a GitHub PAT with repo scope. The repo owner is derived from the token; no username needed. Required for the agent workspace. Everything else has a working local default. Full var reference: web · orchestrator · worker . Start it Everything in one terminal (Ctrl-C stops all three): make dev # starts infra, then web + orchestrator + worker together Or one app per terminal — better for reading logs and running a worker fleet: make db-up # infra (Postgres + Redis + minio) make web # http://localhost:3000 make orchestrator make worker # repeat in more terminals for a fleet Handy endpoints: URL What http://localhost:3000 web app http://localhost:9001 minio console ( quantumbyte / quantumbyte ) localhost:5432 Postgres ( quantumbyte / quantumbyte ) End-to-end walkthrough Open http://localhost:3000 and create a project from an intent prompt. The web app writes a PENDING message to Postgres. The orchestrator assigns it to a live worker (pinning that project to the worker via affinity for AFFINITY_TTL_SECONDS ). The worker clones the project's GitHub repo, runs the Agent SDK, and streams replies + activity back into the chat. Generated assets land in minio and are served from S3_PUBLIC_URL . The harness derives requirements from the project overview and verifies them against the workspace; verdicts show in the blueprint UI. If nothing moves after you send a prompt, at least one worker must be running and heart-beating — check the worker terminal. Stopping and resetting make db-down # stop infra containers (data persists in named volumes) make clean # remove node_modules + Python venvs (does not touch the DB) Full wipe including data: docker compose down -v # removes pgdata + miniodata volumes — destroys all local data Troubleshooting Symptom Likely cause / fix Prompt sent, chat never advances No worker running, or none heart-beating. Start make worker . Worker exits on start / auth error ANTHROPIC_API_KEY invalid and no claude.ai creds. Set a real key or log in. Worker can't create/clone repo GIT_PAT missing or lacks repo scope. make migrate fails to connect Infra not up/healthy. Run make db-up and re-run. Generated images 404 minio not up, or S3_PUBLIC_URL not browser-reachable. Check the minio console and the bucket is public-read. Harness never runs / duplicate runs Redis unreachable — the worker degrades open (runs without the dedup lock). Bring Redis up to restore dedup. Port already in use (3000/5432/6379/9000) Another process owns it. Stop it, or remap in docker-compose.yml / the dev script. Also see ARCHITECTURE.md — system design and invariants apps/orchestrator/README.md , apps/worker/README.md — per-app config tables docs/roadmap.md — where this is going Footer © 2026 GitHub, Inc. Footer navigation Terms Privacy Security Status Community Docs Contact Manage cookies Do not share my personal information You can’t perform that action at this time.