Skip to content
Open sourceAGPL-3.0-or-laterRuns offline in mock mode

A 3D office where a hierarchy of LLM agents actually does the work.

One application, thirteen employees, and a cost ceiling on every run.

You describe a task to a CEO agent. It builds an objective, puts specialists on it, has them argue the approach, gets a file-level plan, writes real code, and tries to break it — every step a separate model call, priced for the work it actually is.

13
roles
across 8 departments
4
stage modes
single · parallel · debate · review-loop
15
tools
8 take paths and are confined
15
skills
markdown, loaded from disk
doneactingthinkingidleblocked
The console

This is the application, not a diagram of one

Every image below is a capture of a live instance — the same build the quick start produces, running with thirteen employees and a real brief in flight. Pick a surface to see what it does.

All features
127.0.0.1:8787
The dev3d console: a 3D floor of an office with employees at their desks, an information panel on the left, the inspector on the right and a brief composer docked at the bottom.

The office is the application. Employees sit at named desks and change colour as their status changes, the panel on the left is the live state of the organisation, and the dock is where work is commissioned.

Twelve surfaces of the console, captured at 1600×1000 from 127.0.0.1:8787.

How a run flows

Five stages, from a sentence to a reviewed change

Complexity, prompt, turn, stage, run. Each stage is a group of LLM calls with its own mode, its own roles and its own model budget — which is what makes a thirteen-person company affordable to run.

  1. 01

    Intake

    CEO

    A nano model reads the brief, sizes it, and decides how much company the task deserves. This is the cheapest call in the run and it shapes every one after it.

  2. 02

    Research

    Specialists, in parallel

    Two to four specialists read, argue and record what they found. A debate stage has them take positions and a chair summarise what survived.

  3. 03

    Plan

    CTO

    A frontier model turns the surviving position into a file-level plan: which files change, in what order, and what would falsify the approach.

  4. 04

    Build

    Developers

    Developer agents write real files into the run’s workspace, through tools whose path arguments cannot leave its root.

  5. 05

    Break it

    QA, then the CEO

    QA tries to falsify the result. The CEO reports back with what was done, what was skipped and what is still unproven.

Prefer to drive it without the UI? The HTTP API is the same one the office uses — see the wire protocol.
The transcript

The record is the run, not a summary of it

Every turn is kept: which model answered, what it cost, what it was asked and what it wrote. When a run goes wrong you read the turn that went wrong instead of guessing at it.

  • Every turn is a separate model call, priced and attributed — so the cost of a run is explicable rather than one opaque number.
  • Approvals stop the office until a human answers, and one that times out counts as refused rather than as permission.
  • Cancellation is safe, and the transcript keeps what happened up to the moment you stopped it.
127.0.0.1:8787
The Work page: approvals waiting on a human, the list of runs with their cost and stage, and the transcript of the run in progress showing its objective and constraints.
Approvals, every run, the transcript of each one and the artifacts it left behind. The transcript is the run as it happened, not a summary written afterwards.
Model routing

The cheapest model that can actually do the job

A one-line intake summary and an architecture review are not the same purchase. dev3d routes them to different models, inside a band the role declares.

  • Roles declare a minimum and maximum tier — a policy the router cannot exceed.
  • Three postures: cheap, balanced, quality. Switchable per installation at runtime.
  • Providers with no key are catalogued but excluded from the routing pool, so a missing key cannot silently fail every turn.
  • Plugins can contribute routing rules scoped to a task class — a preference, never an override.
Routing decisions, per stagelive
Intake classification
cheapest capable
nano$0.0001
Research & summarise
cheap, local preferred
small$0.004
File-level plan
frontier, named difficulty
strong$0.180
Implementation turns
strong coder, tool-capable
standard$0.090
QA & falsification
independent reviewer
standard$0.060
Illustrative per-turn costs. The router reads real prices from the model catalog, including the ones a plugin contributes.
Documentation

Written down, including the parts that are awkward

Installation, concepts, guides and reference. The reference documents limits as readily as features — the plugin that cannot be unloaded from memory, the confinement boundary that is a boundary and not a jail.

Quick startNode 24+
pnpm install                 # Node >= 24
cp .env.example .env         # optional: add provider keys

pnpm dev:server              # orchestrator on http://127.0.0.1:8787
pnpm dev:web                 # office UI on http://127.0.0.1:5273
No API keys required — with none configured the office runs in mock mode, fully demonstrable and entirely unbilled.

Run it yourself in about two minutes

dev3d is open source under the AGPL. Install it, run the mock pipeline, and decide whether to point it at a real provider once you have seen the shape of the work.