RELAY — agent handoff console

Brief

What should the relay build?

The Architect turns this into a system plan. Everything downstream is derived from it.

Gate after Architect Gate after Tech Lead Tools in loop AI Document

Review loops

Routing

Each agent runs on its own model. Mix a frontier planner with a local coder, or push the whole relay on-device with WebGPU. Prompts below are the ones actually sent.

Route

How calls leave the browser

Hosted providers go through your Cloudflare function so keys can live in server env vars. Local endpoints are called direct — the browser must reach them.

Checking whether this deployment has functions…

Proxy path Tool hops per stage Tool-call style

Route hosted providers through the function

WebGPU

Checking WebGPU…

Models run entirely in this tab. Nothing leaves the device.

MCP

Connect an external tool server

Streamable HTTP servers are reached through your Cloudflare function, which handles CORS and holds the auth header. On a static deployment there is no function, so the browser calls the server directly and it must send CORS headers. Tools discovered here are offered to whichever agents you allow.

Name Server URL Authorization header

Built in

Tools that need no server

Always available to the relay. These run in the page or through your own function.

AI Document

Context the relay can draw on

Text is chunked and scored with BM25 in the browser. The top passages are pasted into the Tech Lead and Developer prompts — no embeddings, no upload.

0 documents

Binary formats such as PDF and DOCX are not parsed here. Paste their text instead.

Build output

No files yet

History

Runs are stored in this browser only. Token counts come from provider responses; where a provider omits them the cell reads “not reported” rather than a guess.