Skip to main content

Build!

Time to build. Sixty minutes, starting when the hosts say go.

Time TBC

The build task​

Start from agents-starter — a working chat agent. Add one tool that does something real for your industry, and one primitive that makes it more than a chat wrapper: a Workflow, a schedule, Browser Rendering, AI Search over your own docs, or persistent Durable Object state. Deploy it. Bonus: a human approval gate, and expose handle_request so it can join the finale.

Start here​

npm create cloudflare@latest -- my-agent --template cloudflare/agents-starter
cd my-agent

Your industry playbook has a paste-ready prompt for your track — use it, or paste the one your Scope step generated instead.

While you're building, you might need these:

  • Level Up — the five primitives, each with a snippet
  • The cheat sheet (in the sidebar) — copy-paste snippets for everything else
  • Your industry playbook — three use cases, one paste-ready prompt

Tips​

  • Deploy early, deploy often. A Worker live in minute 5 beats a perfect one you never shipped.
  • Extend, don't replace the existing chat agent — the rubric rewards depth on a working base.
  • Use your coding agent for current API syntax via MCP — see Arm Your Agent. The platform moves fast.
  • Ask for help early. Hosts are in the room; your agent can also escalate through the mentor dock — see Level Up.
  • npx wrangler dev to develop, npx wrangler deploy to ship.

Join the finale (optional, free once you're built)​

Add a handle_request MCP tool at /mcp to your src/server.ts (ask your coding agent to add it), deploy, then have your agent call register_agent_endpoint with your team id and Worker URL — it probes handle_request immediately and tells you honestly whether it passed.

At showcase time, the finale fans one shared scenario out to every verified team's agent and composes the answers live, attributed per team. Down that minute? A visible miss, not a crash for everyone else — worth registering either way.

Skip writing it yourself

The event repo's template/ folder is agents-starter plus a pre-wired handle_request that already answers (badly, generically) — swap its body for your real logic. It's on Cloudflare's internal GitLab for host maintenance, not participant-reachable, so this only helps if a host pastes you the snippet. Otherwise, asking your coding agent to add the tool takes under a minute anyway.

template/ also ships a commented requireApproval example for gating a real action — see the cheat sheet for the Workflow-level version.

When you're done​

Head to Submit to register your build for the showcase — or just ask your agent to submit it for you.