Can I vibecode Skribbl?
price $8.25/moyou'd save $99/yrbuild time a weekend for the canvas, multi-day for the parts that make it trustworthycategory dev-toolsreplaced by 0 people
KINDA
MOATexecution polishintegrations
Infinite canvas where coding agents run as live terminal nodes you wire together by drawing
The Build Prompt
copy it and go buildready to paste · 1,661 chars
Build me a canvas for running several coding agents at once, like Skribbl. Requirements: - Electron plus React, with React Flow for the pan/zoom canvas and xterm.js plus node-pty for the terminals. No web version, this is a desktop app. - Each node is a real shell in its own process, spawned with node-pty in a working directory I pick per node. Double click empty canvas to add one, and let me type in it exactly like a normal terminal. - Node position, size, title and cwd persist to a JSON file in the Electron userData folder, restored on launch. The shells themselves do not survive, say so in the UI rather than pretending they do. - Spawn each shell inside `tmux new-session -A -s <nodeId>` so a crashed window can reattach to the running agent instead of killing it. Budget real time for this, the reattach and scrollback restore is the fiddly part of the whole build. - Drag from one node to another to draw a link, and store the links with a direction. Right click a link to delete it. Links are just recorded relationships for now, no message passing between agents. - A top bar counting tokens per node, parsed from each agent CLI's own usage output. Keep input, output, cache write and cache read as four separate counters, never sum them into one number, a cache read costs about a tenth of an input token. - Out of scope: multiplayer, cloud sync, code signing, and any status indicator you would have to infer by scraping terminal output. Guessing wrong there is worse than showing nothing. - README with the node-pty rebuild step for your Electron version, which is the one thing that will break on a fresh machine.
What you lose
- ✕hook-driven agent status, so a blocked agent looks the same as an idle one
- ✕session survival across restarts and crashes
- ✕an accurate token meter, cache reads price nothing like input tokens
- ✕a signed and notarized Mac build, so Gatekeeper blocks what you ship to anyone else
Prior art / alternatives
Why it still works
process supervision, session durability, per-agent metering