How It Works

Product Workflow & Demo Guide

ForkLab keeps generated code away from the host machine. The Next.js app handles orchestration and provider calls, while BrowserPod runs the files in an isolated browser runtime to capture execution proof.

Open LiveOpen ArenaCheck Smoke
⎇

Connect Repo

Built-in demo repo today
✎

Prompt Task

Issue-driven or freeform
⚙

LLM Variants

Gemini / Groq / Fallback
⊘

BrowserPod

Isolated execution
✉

Proof & Preview

Nonce, logs, portal URL
⑂

Compare

Review strategy outputs
Architecture Steps
1

Select a sandbox repo

Arena Live uses a built-in Node.js and Express frontend repo with issue context. GitHub MCP and ZIP import remain planned connectors.

2

Generate bounded code

Gemini, Groq, Auto, or fallback mode returns only validated HTML and CSS for variants, or one file patch in Agent Lab.

3

Run inside BrowserPod

ForkLab writes files into an isolated browser sandbox, runs the allowed command, and streams terminal output back into the UI.

4

Capture proof

The page records files written, nonce proof, commands, terminal output, and BrowserPod Portal URLs when the runtime exposes them.

System Boundaries

Outer Shell: Next.js

The app owns navigation, UI state, server-only LLM provider calls, validation, and the list of allowed files and commands.

Inner Runtime: BrowserPod

BrowserPod provides the disposable filesystem, Node runtime, terminal, and Portal callbacks. COOP, COEP, and Permissions-Policy headers keep SharedArrayBuffer available.