Discord server
Primary communication channel for the hackathon. A custom role gets assigned to your Discord handle so you can see the hackathon channels.
Schedule
All times America/New_York (EST).
Tue · Apr 21
Kickoff- 12:00 PM ESTVirtual Kickoff — rules, prizes, judging, technical talks
- 12:30 PM ESTHacking officially begins · team formation on Discord
- 5:00–6:00 PM ESTAnthropic office hours (#office-hours)
Wed · Apr 22
- 12:00–1:00 PM ESTLive Session 1 — AMA with Thariq Shihipar, MTS at Anthropic (Claude Code) · @trq212 ↗
- 5:00–6:00 PM ESTAnthropic office hours (#office-hours)
Thu · Apr 23
- All dayHacking continues
- 11:00 AM–12:00 PM ESTLive Session 2 — Claude Managed Agents with Michael Cohen, MTS at Claude Labs · LinkedIn ↗
- 5:00–6:00 PM ESTAnthropic office hours (#office-hours)
Fri · Apr 24
- 12:00–1:00 PM ESTLive Session 3 — Mike Brown, 1st-place winner of Built with Opus 4.6: insights, learnings, where is he now?
- 5:00–6:00 PM ESTAnthropic office hours (#office-hours)
Sat · Apr 25
- All dayHacking continues
- 5:00–6:00 PM ESTAnthropic office hours (#office-hours)
Sun · Apr 26
Submissions due- 12:00–1:00 PM ESTLive Session 4 — Michal Nedoszytko, 3rd-place winner of Built with Opus 4.6
- 5:00–6:00 PM ESTAnthropic office hours (#office-hours)
- 8:00 PM ESTSubmissions due via the CV platform
Mon · Apr 27
- All dayFirst-round judging (asynchronous)
Tue · Apr 28
Winners- 12:00 PM ESTTop 6 teams announced (#announcements) · Final-round judging
- 12:45 PM ESTClosing ceremony — Top 3 revealed
Rules
Four rules. Break any and the team is out.
Open source
Everything shown in the demo must be fully open source: backend, frontend, models, and any other part, published under an approved OSS license.
New work only
Projects must be started from scratch during the hackathon. No previous work.
Team size
Up to 2 members per team.
Banned projects
Projects that violate legal, ethical, or platform policies — or use code, data, or assets you don't have rights to — are disqualified.
Problem statements
Two framings the organizers suggested. Neither is required — just starting points if you’re stuck.
Build from what you know
Start from a real problem in a real place: your work, your community, a field you’re close to. The process that takes weeks and should take hours. The thing someone you know still does by hand. Domain expertise beats credentials — show us the thing only you’d know to build.
Looks like:the process that takes weeks and should take hours. The decision made on gut because the data’s too scattered to use.
Build for what’s next
Start from something that doesn’t exist yet: a new way to work, learn, or make that only makes sense now that the tools have changed. An interface without a name. A workflow from a few years out. The best projects here are easier to demo than explain.
Looks like:an interface that doesn’t have a name yet. A first draft of how this will work in a few years when Claude is even more capable.
Judging
Two stages. Async scoring first, then a live final round.
Stage 1 · Asynchronous
Apr 26 – 27Judges independently review submitted projects via the judging platform. Each team uploads three things: a short demo video (3-min max), the open-source repo, and a 100–200-word written summary. Scores aggregate to pick the top six for live judging.
What's the real-world potential? Who benefits, and by how much? Could this actually become something people use?
Is it a working, impressive demo? Does it hold up live? Is it genuinely cool to watch?
How creatively did this team use Opus 4.7? Did they go beyond a basic integration and surface capabilities that surprised even the judges?
Did the team push past their first idea? Is the engineering sound and thoughtfully refined? Does this feel like real craft, not a quick hack?
Stage 2 · Final round live
Apr 28 · 12 PM EST- Pre-recorded demos play live (3 min per team).
- Judges deliberate after all demos to pick 1st, 2nd, and 3rd plus the extra prizes.
- Winners announced at the closing ceremony at 12:45 PM EST.
Submission
Submit via the CV platform. Required:
- 3-minute demo video — YouTube, Loom, or similar.
- GitHub repository — or code link, fully OSS.
- Written description / summary.
Project must be built entirely during the hackathon. No pre-existing work.
Open submission page ↗Prizes
All paid out in Claude API credits.
Most Creative Opus 4.7 Exploration
$5,000For the project that treated Opus 4.7 as a creative medium, not just a tool — something with a voice, a point of view. Something expressive, playful, strange, or alive. The one that made us feel something.
The “Keep Thinking” Prize
$5,000For the project that didn't stop at the first idea and landed somewhere nobody saw coming. A real-world problem nobody thought to point Claude at — one that changes how we think about where this technology belongs.
Best use of Claude Managed Agents
$5,000For the team that leveraged the Claude platform best. The project that uses Managed Agents to hand off meaningful, long-running tasks — not just a demo, but something you'd actually ship.
Questions
#questions on Discord or reach out to moderators there. For build references — docs, courses, cookbooks — head to Resources. To find collaborators, check the participant directory.