chirai / test-runs

Demo
projects.

Every app on this page was generated by Chirai during development — one prompt, no manual coding, deployed live. This is what the system actually produces, not a curated showcase.

All links are live and clickable
Real stats from actual runs
Updated as we build
🔬 These are test runs, not demos. Some have rough edges — that's the point. We document what the system produced, what broke, what QC caught, and what we improved. You're watching a product being built in public.
run_001 live

Space Shooter

$ chirai build "space shooter game"
live
status
Phaser 3
engine
game
category

One of our earliest test runs — typed "space shooter game" and let Chirai figure out the rest. The system correctly identified this needed a game engine (Phaser 3), not a web app stack, and switched its entire generation pipeline accordingly. Ships with player movement, enemy waves, shooting mechanics, score tracking, and a game over screen.

✓
Correctly routed to Phaser 3 game pipeline — no Next.js, no Supabase, right tool for the job
✓
Player movement, bullet mechanics, enemy spawning — all working on first generation
✓
Score system and game-over state work correctly across restarts
→
This was a pipeline validation run — confirmed the game route detects correctly from a 2-word prompt
Phaser 3.88 TypeScript Vite Canvas 2D Arcade Physics
Play it now — spaceshooter.chirai.dev
✓ QC passed — no critical issues
SCORE: 1240
▶ Play game
generated files
▸ package.json
▸ src/scenes/GameScene.ts
▸ src/scenes/MenuScene.ts
▸ src/scenes/GameOverScene.ts
▸ src/objects/Player.ts
▸ src/objects/Enemy.ts
▸ src/objects/Bullet.ts
▸ src/main.ts
✓ deployed to vercel
run_002 live

Pomodoro Timer

$ chirai build "pomodoro timer"
32
files
7,305
lines
42m
gen time
$3.98
cost

Our first full SaaS app generation — a pomodoro timer with user accounts, session history, task management, and stats tracking. This run exposed several bugs in our generation pipeline that we've since fixed: the parser was reading file listing instructions as actual file output (producing 0 files per screen group), a double-slash path bug in screen routing, and thinking blocks from Claude consuming output tokens and causing truncation.

✓
Full auth flow generated — login, register, session management all working
✓
4 Zustand stores, SQL migration, 4 API route files — complete backend
!
Parser bug: file listing markers confused the model — screens 1 & 2 produced 0 files. Fixed in v0.2.
!
Path bug: screen.path had leading slash → src/app/(app)//profile/page.tsx. Fixed.
→
42 min / $3.98 is too slow and expensive for tier-1. After fixes: ~15 min / ~$0.60 expected.
Next.js 14 TypeScript Supabase Zustand Tailwind CSS Outfit font
Deploy in progress Get notified when live
⚠ QC: 3 critical (auto-repaired 9 files)
25:00
FOCUS SESSION
Screenshot coming soon
generated files (32 total)
▸ tailwind.config.ts
▸ src/types/database.ts
▸ supabase/migrations/001_initial.sql
▸ src/store/session.store.ts
▸ src/store/task.store.ts
▸ src/app/(auth)/login/page.tsx
▸ src/app/(app)/timer/page.tsx
▸ src/app/(app)/history/page.tsx
▸ src/app/(app)/settings/page.tsx
+ 23 more files
🔬

More runs coming

We generate new apps every time we ship a fix. Bookmark manager, habit tracker, and invoice tool are queued. Each will be documented here with full stats.

Get notified when we add more

Want your idea
on this page?

Join the beta and we'll generate your app next.

Apply for beta access