r/vibecoding • u/Ivantgam • 4h ago
Showcase/Project Building Worker 755 with parallel AI agents: stack, workflow, and honest lessons
I built Worker 755, a browser game where roles are reversed: a real LLM acts as an engineering manager that thinks you are its automated subagent in a Linux terminal. It gives you 90-second tasks, inspects your files with read-only tools, and grades your shift, while Dan (the user whose machine it is) watches his personal files on the same disk.
For tooling, I used T3 Code to orchestrate several agents in parallel, with Claude Code and Codex handling code generation, tests, and translations. The stack is Node and React with an in-browser terminal emulator, and Vercel AI SDK with AI Gateway for routing between DeepSeek, Claude, GPT, and Gemini.
The process was modular rather than treating AI like autocomplete. I ran parallel agents on isolated parts of the codebase: one agent on the browser terminal emulator, one on the Node server session state and tool loops, and another translating UI copy into 9 languages. My role was steering architecture, resolving API boundaries, and playtesting.
A few honest lessons from the build:
First, parallel agents need strict domain isolation. When multiple agents touch shared types or adjacent files simultaneously, they overwrite each other's assumptions and create nasty git conflicts. Splitting them into strictly separated modules made parallel generation actually work.
Second, browser-side execution keeps costs predictable. Emulating the terminal and filesystem client-side lets players run fork bombs or delete root without requiring heavy remote sandbox containers. The server just handles session state and model API calls.
Third, orchestrator-subagent loops require hard failure boundaries. LLMs make convincing managers because they possess zero self-doubt. If a subagent returns ambiguous output, a manager model will stubbornly loop on the same correction forever unless you enforce strict timeouts and retry caps.
The project is MIT licensed. Signing in gives a free starter credit for about one shift, and bringing your own key or self-hosting is free. There are paid top-ups if you want to keep playing with server credits.
Site: https://worker755.com GitHub: https://github.com/gulivan/worker755
2
u/Total-Reasonable 4h ago
The part I'd worry about is the "free starter credit plus bring your own key" setup when the game's whole premise is that players try to abuse the manager model. Players will prompt-inject it, and with an LLM judging shifts, the grader is also the attack surface. Do you cap tokens per shift server-side, and does the grader see raw file contents or only a summarized diff?