Click power, sit through boot (BIOS → breach → ROAST_COUNCIL.exe → four entities), pick a language (EN / HI / ML / ZH / KO), ask one question. Four panels answer with typewriter text and a pop-in animation.
Most of the project is frontend (frontend/index.html, ~2.7k lines): CRT layers, boot script, fake window chrome, fourthWall dialogs. Backend: four parallel Groq calls, JSON back.
| Step | What happens |
|---|---|
| Power | Landing screen → boot window |
| BIOS | Green typed lines, security scan |
| Breach | Red panic, shake, MOM.exe / HATER.dll / … |
| Voice | “we saw you click that power button” |
| Language | Keys 1–5 (menu on main screen too) |
| Council | Input + four persona terminals |
Red / yellow / green window buttons open snarky alerts, not a real window manager. Close runs a shutdown animation.
Try on the live app after boot finishes.
| Try | Result |
|---|---|
| Idle ~45s | System alert |
Paste code / npm / git |
Blocked + dialog |
Type ls + Enter |
Same |
| Fast mouse movement | Motion sickness dialog |
| Right-click | Blocked |
| Ctrl+C, F12 | Keyboard / devtools dialogs |
| Name | Angle |
|---|---|
| Worried Mom | Over-the-top concern |
| The Hater | Short, brutal |
| Conspiracist | Everything is connected |
| Hype Man | Hype regardless of facts |
| Frontend | HTML, CSS, JS, Tailwind — Vercel |
| Backend | Flask, Groq Llama 3.3 70B — Render |
| Also | POST /council/debate · serious UI in frontend/cf/ |
Run locally
cd backend && pip install -r requirements.txt
cp .env.example .env # GROQ_API_KEY
python app.pypython -m http.server 8080 # repo rootfrontend/index.html points at production Render by default; use http://localhost:5000/api/getResponses for local API.
Started as a multi-agent council; rate limits and UX pushed it to a one-shot roast terminal. The UI is the point.