DocsVibeCodeWorker
Docs · the QA lab
Break it. Prove it. Ship it.
Evidence-driven QA: point VibeCodeWorker at a game, watch it observe → reason → act, and get runs, findings, bugs, and portable handoffs with proof. Start at /vibecodeworker.
- 3
- steps per loop
- 4
- severities
- 3
- verdicts
- 1
- portable handoff
The floor plan
Surfaces at /vibecodeworker/*
Overview, hub, run, full, phone, docs, and demo — each pairs a guide with the live surface plus a public service-status pill. If the pill reports trouble, wait before opening runs: the loop depends on the service underneath.
The assembly line
The 7-step agent loop
Signed in, every route returns success envelopes and rate-limits per user. Read the full run (trail + findings) before every next step.
Check status
Confirm service health, catalog game count, recent runs/bugs. Unhealthy? Stop here.Pick a target
List catalog games — slug, title, genre, play URL. Every legal run target comes from this list; first-party play URLs only.Open a run
Catalog slug + a 1–500 character goal (“verify level-2 boss spawns adds”). You get a run ID.Observe → reason → act
Append one iteration at a time — observation, action, or finding (text + optional ≤10 KB data object). Open runs only.File bugs
Title + description + severity (low/medium/high/critical, default medium), optionally pinned to a run (defaults the slug).Complete the run
Close with summary + verdict: pass / fail / inconclusive. Closed runs are read-only history.Hand off
Export a portable markdown brief for any coding tool (defaults to your latest run). The dashboard gives recent runs + bugs in one view.
Exhibit A
What good evidence looks like
run #4821 — boss-spawn verification
verdict: passOBSERVE screenshot: 3 adds spawn at 0:42, HP bars visible
REASON spawn matches spec §2.1 → engage, record score events
ACT cleared wave, no console errors, 60fps held
FINDING goal met — no bug filed, evidence attached
Field notes
Writing runs + bugs that get fixed
🎯 Goals
One verifiable claim per run: “menu → new game → first checkpoint, no console errors.”
🔬 Steps
Small, timestamped, evidence-first: “screenshot shows…”, “score event fired…”.
🐞 Bugs
Expected vs. actual + repro path + severity + run link. Critical = data loss, payment error, safety.
🏁 Verdicts
Pass (evidence), fail (repro defect filed), inconclusive (blocked — say what blocked you).
Keys + gateway
Call the loop with your own tools
The run loop above uses your login session. The gateway (under /api/vcw/gateway/*) gives the same loop a key you can paste into your own agent tools — hosted on our GPUs, or routed to your own provider keys (BYOK).
Probe the gateway
No key needed: GET /api/vcw/gateway/status reports the hosted markups (15% standard, 9% enterprise) and the BYOK kinds. Start here before wiring anything.Issue a key
Signed in: POST /api/vcw/gateway/keys with a label, scopes (vcw:read, vcw:write), and optional lifetime/daily budgets + expiry. The vcw_live_ secret is shown once and never again (max 10 active keys). List them anytime with GET — secrets never come back.Register your providers (BYOK, optional)
POST /api/vcw/gateway/providers with kind (runpod, openai, fal, meshy, or custom + your https endpoint), a label, and your key. We store only kind + label + last-4 — your full secret is never stored, returned, or logged. DELETE removes one.Dispatch a run
POST /api/vcw/gateway/dispatch with game_slug, compute (cpu/gpu/gpu-boosted), mode (hosted/byok), and goal — authenticated with your login, a bot key, or the gateway key (x-bot-key or Authorization: Bearer), with vcw:write scope. The MVP answers honestly: always started:false with the coin quote, the meter receipt, and the manual next step (POST /api/vcw/runs or autoplay). No worker URL is ever faked; low balance fails closed with 402.Watch the spend
GET /api/vcw/gateway/usage shows your latest 50 metered rows. Every figure is gross with the 25% cut already inside — same as every metered surface on the site.
💰 Gateway prices (gross, cut inside)
run-open 10 · action-step 1 · bug-file 2 · handoff 5 · worker-min 6 · byok-route 2 coins. Hosted adds 15% over provider cost (9% enterprise); BYOK bills the base price. 100 coins = $1.00, always.
🔑 Key hygiene
Copy the secret once, store it like a password, set a budget + expiry, revoke keys you stop using. Gateway-key reads and writes are metered to your coins like session calls.