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

This event's own template/ (public agents-starter plus a pre-wired /mcp finale endpoint) lives in Cloudflare's internal GitLab, not a public host reachable from your laptop — see Join the finale below for the couple of lines to add yourself to get the same effect. Start from the command above; it always works.

Your industry playbook has a paste-ready prompt already scoped to a seed use case for your track — start there if you don't already have your own idea, or if the Scope agent already generated one for your team, paste that 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 deployed in minute 5 that does nothing yet beats a perfect one you never got to wrangler deploy.
  • Keep the existing chat agent working. Extend agents-starter, don't replace it — the rubric rewards agentic depth on top of a working base, not a rewrite from scratch.
  • Use your coding agent. It has Cloudflare's docs and API through MCP — see Arm Your Agent. Ask it to check current API syntax rather than guessing; the platform moves fast.
  • Ask for help early. Hosts are working the room. If your own agent gets stuck, it can escalate through the mentor dock — see Level Up.
  • npx wrangler dev to develop locally, npx wrangler deploy to ship.

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

The event repo's template/ folder is exactly what npm create cloudflare@latest -- my-agent --template cloudflare/agents-starter gives you, plus one addition: a pre-wired handle_request MCP tool at /mcp, already answering (badly, generically) so you get "verified" for free the moment you deploy — swap its body for your real agent logic once you've built something. (The event repo itself is on Cloudflare's internal GitLab for host maintenance — not participant-reachable; ask your coding agent to add a handle_request tool to your own agents-starter's src/server.ts if you want this without the shortcut.)

To opt in:

  1. Deploy your Worker (it already has /mcp if you started from template/).
  2. Ask your coding agent to call register_agent_endpoint with your team id and Worker URL — it probes handle_request immediately and tells you honestly whether it passed.
  3. That's it. At showcase time, the finale orchestrator fans one shared scenario out to every verified team's agent and composes the answers live, attributed per team. A team whose endpoint is down that minute shows up as a visible miss, not a crash for everyone else — worth registering even if you're not sure it'll still be up.

template/ also ships a commented requireApproval example (src/server.ts) — a copy-paste starting point for gating a real business action, not just the toy calculator the stock template ships with. See the cheat sheet for the Workflow-level version of the same idea.

When you're done​

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