Your pixel-agents fork is remarkable — I'm building the same thing

[benkauffman]

Hey @continued-now — I'm Ben. I've been building ctrl, a pixel-art office for AI coding agents. I've been scanning forks of pixel-agents periodically to see what people are doing with it, and yours stopped me cold.

In 3 days you built a standalone web dashboard with meeting rooms, a minimap, character customization, theme transitions with ambient animations, a "Jump In" mode, QR sharing, drag-to-reorder panels, and PWA support. That's not a fork — that's a product.

What really got my attention is the architecture. You independently arrived at the same stack I've been building for months: standalone web app + WebSocket daemon + Canvas 2D rendering + JSONL session parsing. That kind of convergence isn't a coincidence — it means the problem demands this shape.

Your for-ralph.md is worth calling out specifically. Writing success criteria before implementation, structured task lists with clear scope — that's how I work too, and it's rare to see it in a weekend project.

What ctrl is: A standalone React + Canvas 2D web app with a bun WebSocket daemon that watches JSONL sessions. Multi-agent, multi-daemon (one per project per machine), relay sharing for remote access, adapter architecture for Claude Code / Codex / Gemini / any CLI agent. It's currently private but moving to open-core — the repo will be public soon.

What you've built that I haven't shipped yet: Meeting rooms, minimap, character customization, theme transitions, Jump In mode, QR sharing, ambient animations. Several of these are on my roadmap. It's crazy that you built all of this in a weekend.

I'm not pitching a job. I'm saying: if you're interested in working on this problem seriously, I'd like to collaborate. Whether that's contributing to ctrl when it goes public, comparing notes on architecture decisions, or just talking about where this category of tool is heading.

You have a ghost profile so I have no way to reach you other than this. If any of this resonates, open an issue on your fork and tag me (@benkauffman), or start a discussion on bulletproof-sh/.github. I'll see it.

— Ben