Who
I got tired of treating Editor, disk, git, and remote hosting as four different systems for the same daily loop.
Kitchen is for operators who want live sync and a real editor (nvim, VS Code, Zed) without renaming the product a cloud IDE. It is for people who will say "no git" and mean no add/commit/push/pull/rebase, while history and human merge stay.
If you have ever saved a file and still had a ceremony left before another machine could see it, this is for you.
What
I built Kitchen (michaelmonetized/kitchen, web 0.1.0). Codename. Next 16.2.9 + Convex + Clerk + Mirror. HEAD 97bec56. 34 commits.
Where
Live https://kitchen-gilt-nine.vercel.app. Home/pricing/docs/sign-in return 200; discover returns 404; vision/mission return 404 (untracked working tree). Web is tree/diff/blame in the browser; local editors stay native.
When
June 18 2026: public log opens at fork-merge; same day org-admin, collab-relay, landing, Vercel ship, recovery loops, then Mirror client, launch-gate, diff/blame, agent kit, offline queue. June 21 lakebed parity. June 22 nightly HEAD 97bec56. Pack day 2026-09-08 draft-only; working tree dirty, not pushed.
Why
Honest codename. Launch gate blocks PH/HN until Mirror demo is true. Dual honesty: marketing routes return 200 while discover returns 404 and docs drift in the working tree. "No git" means no ceremony verbs; Versions and Pierre merge stay.
Engagement Q: If your editor already saves to disk, what would have to be true before you deleted git add: live Versions on another machine, or a merge UI you trust more than conflict markers?