Mechanical newbie Β· learning to operate
Own the machine before the ideas. Type without looking, move without the mouse, live in the terminal and git.
Play LeetCode against your phone's AI. Or team up against other people's phones.
The model runs on the phone's NPU. Radios off. No cloud, no API call. It still wins.
Everyone else's "AI coding" is a network call to someone else's datacenter. CodeClash runs the whole match on the hardware in your hand β and proves every answer instead of trusting it.
Gemma executes on the phone's Hexagon NPU via LiteRT-LM. Put the device in airplane mode and it keeps coding. Nothing leaves the phone.
Every solution runs against a real test suite inside a sandbox β isolated namespace, cleared env, no filesystem. No vibes. Green or red.
Greedy decode β no temperature roulette. The clash that worked in rehearsal works in front of the room. Demos don't get stage fright.
A match is two roles talking over a local socket. The phone is the house β it runs the AI and judges the code. Your laptop is the challenger.
Arena β Weapon over a local WebSocket. No relay server. The match exists only on the LAN in the room.
The phone proves the edge. The platform behind it lives in the cloud β AWS-hosted HawkTalk AI models, served on Inferentia and trained on Trainium. One family of models, two silicon targets, racing each other.
CodeClash wears three hats at once: a HawkTalk AI product, built by an AWS customer that trains and serves its own models on Trainium + Inferentia, and a live showcase of what edge and cloud NPUs do when you point them at the same problem.
Same on-device engine underneath every mode β the phone generates, a sandbox verifies. What changes is who's fighting whom.
Fewest tokens to a solution that passes every test. Elegance beats brute force.
Don't just solve it β write the tests that break the other side's answer. Adversarial by design.
Two solutions land. One human, one phone. The room votes on which is which.
You and your phone's model tackle the bank together β you steer, it drafts. Beat the clock, not each other.
Team up against other people's phones. Every table is a human-plus-NPU pair; fastest pair to green takes the round.
Slide the AI handicap 0β100% so a first-week coder and a frontier operator can share a table. Try it in the hero above.
One-shot, locked environment. Spot the bug the diff introduced before the timer's up.
Write a spec precise enough that the model β or the next human β ships it with zero back-and-forth.
Points for the clearest account of why your solution works, not just that it passed.
Vibe coding isn't a solo activity anymore. The Vibe League turns your setup β your agent stack, your phone, your prompts β into a competitive team sport. Every race scored, every rank hardware-aware, every season a fresh climb.
The unnerfed opponents at the top of the ladder don't live on your phone β they're HawkTalk models running full-speed on AWS Inferentia. Climbing the Neural Index means out-coding the cloud, not just the room.
Non-zero-sum ELO: win +1.0, lose β0.95. That 0.05 "grind gap" means if you show up and hold 50%, you still climb β rank rewards experience in the arena, not just raw speed. Divisions are hardware-aware: you don't bring a 2022 Pixel to an S25 Ultra duel.
Your custom agent stack vs. another player's. Pure setup optimization β best rig wins.
Three humans + three agents against a God-Tier phone-NPU simulation. Coordinate or lose.
You and your personal AI team up to out-run the raw local NPU's speed. Human + machine vs. machine.
Full architectural race to deploy an entire cloud-ready project β not one function, the whole build.
Every race renders a Twitch / YouTube-ready overlay β the numbers a caster needs, live. Download a top player's Shadow and race their prompt-stream; spectators can back an agent setup before the buzzer.
90-minute live-streamed sprints feed seasonal qualifiers, funneling the best human-plus-NPU pairs toward the Vibe Coding World Championship.
CodeCoach isn't a fourth mode β it's the thing that turns the modes and drills into a pipeline instead of a menu. It watches how you worked, not just whether the code passed, and decides what you do next.
Own the machine before the ideas. Type without looking, move without the mouse, live in the terminal and git.
Run code in your head. Trace what it actually does before you trust it β the skill every debugger is built on.
Turn a spec into code that passes β and fix what's broken when it doesn't.
Think past the happy path: design tests, navigate a codebase you didn't write, weigh production concerns.
Direct the model instead of being impressed by it. Precise specs, critical reading of its output, and knowing exactly when to step in.
Run a fleet, not a chat. Decompose the work, design the verification, delegate with judgment β and own the audit when it lands.
The model can already write the code. CodeCoach trains the part it can't do for you β knowing what to point it at, and whether to believe it.
CodeClash makes its debut at the Games & AI Meetup. Come watch a phone in airplane mode out-code the room β then take a turn on the Weapon and try to beat it.