01
Brief
You write one paragraph. The intake desk reads it, classifies the deliverable, and logs any reference files.
A desktop studio of agents
One brief in.
A product you can run.
Thirty-two people across six floors take your paragraph, argue about it, cut the filler out of it, and build the actual thing. A lead writes the contract, three agents own the files, and a verifier boots the result. Not a slide deck. Not a summary. A working folder on your disk.
Linux and Windows. Runs on your machine. Your briefs stay local.
Watching the studio
- INTAKE
- BRIEF
- PLAN + AUDIT
- TEAM CONTRACT
- PARALLEL BUILD
- VERIFY + FIX
- SHIP
How it works
Seven stages. Planning runs in parallel. The build is a real agent loop with file ownership, and nothing ships until the verifier boots it.
02
Plan and audit
One person rewrites the brief. The product plan and the audience research run at the same time, design starts from both, and the audit cuts the filler before anyone builds.
03
Team contract
A lead turns the plan into entities, endpoints, copy and file ownership. Three packages are queued with separate paths, so the agents cannot overwrite each other.
04
Parallel build
Front end, server and tests are written at the same time. Each agent reads the shared project and writes only its own files. A verified baseline is kept in case an agent breaks the build.
05
Verify and fix
The verifier parses every file, runs the test suite, starts the real server on a free port and walks the API. Failures go back to a fixer agent before anything is signed.
06
Ship it
The director checks the evidence and closes the project. A full-stack app also gets a RUN APP button that starts it and opens the browser.
What it makes
Full-stack app
A Node server, a file-backed store, a browser interface and a test suite. Add, edit, remove, search, sort, filter, export CSV. The data lives on disk, not in the browser.
node server/index.js
Pixel art
Rendered on a strict grid with a limited palette, at 4x with nearest-neighbour scaling so the edges stay hard.
image.png
Music
A score written as note data and synthesised into a real stereo track. It comes out playable, not as a description of a song.
track.mp3
Vertical reel
1080 by 1920 at 30 fps. Bold capitals that build in, one accent word, cards, counters, a progress line. The layout is measured, so text never spills.
video.mp4
Motion design
A 12 to 26 second film: device screens, kinetic type, layered UI, reflections, bloom and one accent. Rendered to MP4 and exported with an offline player.
motion.mp4 + motion.html
Document
Markdown with sections, rules and concrete points. Written to be read at a desk, not skimmed on a landing page.
document.md
server/
public/
project.json
The folder
Alongside the file: the brief, the plan, the design, the audit, the task list, and the build summary.
~/PixelCorp/
0
people on staff
0
floors
0
production stages
0
deliverable types
Download
Portable. No installer, no admin rights, no Node.js on the machine. Unpack nothing, run it.
Windows
146 MB, single .exe
Windows shows a SmartScreen warning because the build is unsigned. Choose More info, then Run anyway. The first launch unpacks a video encoder next to your app data.
Linux
177 MB, AppImage
Make it executable, then run it:
chmod +x PixelCorp-1.0.0-Linux.AppImage
After it starts
- Open SETTINGS and paste your CommandCode API key.
- Press TEST CONNECTION. You want
OK … reply: ready. - Press SAVE. The token counter in the header fills in.
- NEW PROJECT, write one paragraph, START BUILD.
The app ships without a key on purpose. Keys do not belong in a repository.
What it will not do
It will not invent numbers
No fake testimonials, no invented user counts, no made-up statistics. If the brief does not contain a number, neither does the output.
It will not pad
No three identical feature cards. No big centred headline over a gradient. The audit stage exists to remove exactly that.
It will not phone home
The only network calls are the ones to the model API. Everything it makes is written to a folder you choose.