You don't have to pick a lane, anything that hits the brief is fair game. But if you're staring at a blank screen at 10:05 AM, this is the menu.

Build a web app where Kiro ships the feature and Kane proves it works, without you opening the browser to check. The category every dev quietly wants but nobody's nailed.

• A todo app where every new feature comes with auto-generated Kane flows. 

• A drag-and-drop dashboard builder that re-verifies every component after edits.

•  A self-healing checkout flow where Kane catches a regression, the agent fixes it, and Kane re-verifies. 

• A "prompt-to-feature" playground where users type "add a dark mode toggle" and watch the whole loop close in real time. 

• A npx create-verified-app template that bakes Kane and an agent in from day one. 

• A drive-by GitHub bot that drops into any AI-generated repo and adds Kane verification. 

• A "QA-as-a-service" agent for non-technical founders — point it at a deployed app URL, get a bug report.

The demo writes itself: open the app, trigger a change, watch the loop, show the green run.

Build the tool you wish existed in your day-to-day dev loop. Something that runs Kane automatically, on save, on push, on a schedule, on a Slack message, and uses an agent to decide what's worth your attention.

This lane covers everything from the inner loop (your editor) to the outer loop (production monitoring). What unites it: you set it up once, and it works while you're doing something else.

• A kane-watch file watcher that re-verifies behavior on every save.

•  A gh kane GitHub CLI extension that runs Kane on the current PR's preview deploy and posts results in the comments. 

• A Cursor or Claude Code MCP server that gives the agent a verify_with_kane tool. 

• A pre-commit hook that derives Kane flows from your git diff and blocks bad commits. Auto-bisect that walks back through commits to find the one that broke Kane. 

• A visual canary that tells real regressions apart from harmless pixel drift. 

• A conversion funnel watcher that runs your checkout every thirty minutes and pages on anomalies with the failed video attached. 

• A doc-vs-product drift detector that runs the steps in your README and files an issue when they no longer work. 

• A weekly competitor digest where Kane runs across N sites and an agent writes the "what changed" memo.

The demo: install it on a real repo on stage, or show the historical alerts the agent decided were worth paging on. Make the workflow getting tighter visible.

Use Kane CLI as an agent's hands-on the web. Not testing, the actual work the agent does for someone. This is where Kane stops being a QA tool and becomes browser infrastructure for any agent that needs to act on the web.

• The most useful versions in this lane solve a real, weird, specific problem. The most fun versions are pure spectacle. Both win.

• A job application autopilot that takes your resume and a job posting and submits the application, pausing on essay questions so you can answer them.

• A subscription killer that reads your bank statements and navigates each company's cancellation flow.

• The "renew everything" agent for domains, licenses, certifications, and memberships. 

• A travel agent that books on real airline sites with no APIs in sight. Lead enrichment that visits each prospect's site and LinkedIn and returns a one-pager. 

• Live "prompt my app" where the audience tweets a feature, the agent ships it, Kane verifies it, all on a screen behind you. 

• A Wikipedia speedrun bot racing other teams in real time. An agent playing a browser game with no API access, pure vision and clicks. 

• A recursive ship-by-dinner where an agent writes a blog post about itself and uses Kane to publish it to dev.to during your demo.

The demo: show the human task, show the agent doing it, show what would have taken two hours done in four minutes, or just put it on a screen and let the room react.

Three things, ideally done the night before:

1. Install AWS Kiro and sign in. Download from kiro.dev. Sign in with your AWS account (or social login if you're trying it for the first time). Run one chat in vibe mode to make sure it's working.

2. Install Kane CLI and run one flow. Run npm install -g @testmuai/kane-cli, then try one of the examples from the docs. If fifty people are doing fresh npm installs at 10:05 AM, the hackathon loses an hour. We'll send a cheat sheet with your confirmation email.

3. Read the Kiro × Kane integration guide. We'll send a short doc showing how to wire a Kiro hook to a Kane run. It's the fastest path to a closed loop on the day.

You'll have free Kane CLI Pro access for the day, so don't worry about hitting limits during the event.

Three things. That's it.

A GitHub repo — public, or invited access for the judges. Include a README with setup steps.

One paragraph — what you built, who it's for, and what Kane is doing in the flow. Goes in the submission form.

A live URL or runnable command — judges should be able to see the app working in under 30 seconds.

A dev.to writeup is optional but strongly encouraged. Every team gets a credit in the TestMu + dev.to event recap, and standout posts get amplified across both audiences.

$3,000 USD in cash, split across three winners. Every winner also gets the full perks stack.

• 1st Place: $2,500
• 2nd Place: $1,500
• 3rd Place: $1,000

In addition to the cash, every winning team receives:

• A 1:1 with the TestMu AI founders

• Design partner status with input on the Kane CLI roadmap

• 3 months of Kane CLI Pro

• A featured post on the TestMu blog

• A showcase feature on testmuai.com/kane-cli/showcase

• Amplification across TestMu and dev.to channels

Builder Badge — every team that ships a working project by 5 PM gets the Builder Badge on their TestMu community profile, regardless of placement. Show up, ship, get the badge.

• Anyone 18 or older

• Solo or teams of up to four (one team captain receives the prize)

• Open to builders from anywhere, you just need to be in SF on the day

The application is curated. We're optimizing for builders who have shipped things before — we'd rather have fifty people who'll ship something real than two hundred who'll watch.

• The app and the Kane integration must be substantially built during the day. Bringing a scaffold or starter repo is fine — just be honest at demo time about what existed before 10 AM.

• Use any AI coding agent, any framework, any stack. Kane CLI is the only required dependency.

• If your project depends on a login or a paid service, hand the judges working credentials. We can't score what we can't run.

• Code stays yours. By submitting, you grant TestMu AI permission to feature your project in marketing materials with attribution.

• The judges' decision is final.

• A working app shipped in a single day

• Free Kane CLI Pro access for the event

• Breakfast, lunch, snacks throughout, dinner, drinks at the wrap

• A room full of fifty curated SF builders

• Early access to a tool that's about to be a much bigger deal