Skip to main content

Step 7 of 7: Demo and submit

By the end you will be able to:

  • Walk through a three-minute demo of your agent
  • Submit your project and confirm your entry
  • Reopen your demo URL from a fresh browser tab

Use the Cloudflare account on your team card (also on the Workspace page). No account yet? Ask a host: you can read on, but you can't deploy until it is ready.

The curl and PowerShell examples use $DEMO_URL (macOS / Linux) or $env:DEMO_URL (PowerShell): your demo URL from your team card, set once per terminal in Step 1. Open a new terminal later? Set it again.

Why it matters​

  • The build only counts once other people can see it.
  • A short, honest demo of something that works beats a long tour of something half-built.
  • Submitting takes two minutes. Do it as soon as you have anything that runs, then resubmit as it improves.

The concepts​

After the build block ends (17:30), every team demos to the room (17:30 to 18:15). Judges watch the demos; how scoring works is on the Submit page. Submitting is how the judges find your team, your demo URL and your code.

A three-minute demo has four beats:

  1. The problem in one sentence: who hits it, and what it costs them.
  2. The agent doing it on your demo URL, live: the tool from step 2, the memory from step 3, the primitive from step 4.
  3. The human in the loop: trigger the approval from step 5 and click Approve.
  4. One thing you secured (optional): a before and an after from step 6.

Use synthetic data for this workshop. Your demo URL and chat may be publicly reachable; do not upload real customer, employee or proprietary data.

Do it​

1. Check your agent is live​

macOS / Linux
curl -s -X POST "$DEMO_URL/api/chat" \
  -H 'content-type: application/json' \
  -d '{"message":"hello"}'
Or type it in your agent's chat page
hello

Open your demo URL in a browser and paste this into the message box instead of running the command above. It is the same agent either way.

It should answer on your demo hostname. That URL is the demo URL you will submit.

2. Submit​

Open the Submit form. Your team comes from your sign-in, so there is nothing to choose. Give a project name, your demo URL (the hostname on your team card, with https:// in front) and a link to your code. Submitting again updates your entry, so submit early and resubmit freely. An AI judge looks at your demo URL each time you submit.

No repository? Your code and lockfile are yours: keep the starter folder to redeploy in your own account.

3. Rehearse once​

Run your three minutes end to end, once, with a teammate. Have a screenshot of the working agent ready in case the wifi is not.

Check it worked​

  • The Submit form confirms your entry.
  • Your demo URL answers from a fresh browser tab.
  • You know who says which beat of the demo.
Stuck?
  • The Submit form says you are not assigned. You can only submit for the team a host assigned you to. Not assigned yet, or in the wrong team? Ask a host.
  • The demo URL does not answer. Check the Worker deployed as agent into your team account, and see Step 1 "Stuck?". Do not try a workers.dev URL: it is off on purpose.
  • The approval demo is flaky. Approvals only exist in the chat page, not over curl. Demo from the page.
  • Live wifi is bad. Show a screen recording or screenshots, and say so. That is fine.
  • Anything else. Raise a hand for a host, or ask the Mentor dock (it escalates to a host when unsure). Remote: remote help channel to be confirmed by the event owner.
Go further
  • After the event: your temporary team account and its resources are torn down on 2026-10-14. Keep your code; redeploy it in an account of your own any time (Bring It Home lists what to change).
  • Write down what you would do next with two more days. It is the best closing line for a demo.
  • Bring It Home turns your submission into a short recap you download and keep.

Finished step 7?

Checking your team…

Back: Step 6: Secure it. That's the whole path. Good luck in the demo.

Need help? Raise a hand for a host, or ask the Mentor dock (it escalates to a host when unsure). Remote: remote help channel to be confirmed by the event owner.