01
Work scattered across chats
Running several ventures with AI agent teams inside chat windows does not scale: instructions, states and results blur together.
Home / Playground / Master App
Internal tool: command centre
Every office. One desk.
One app where a founder sees and directs every virtual AI office he runs: each venture has its own 3D office, its own agent team, and its own message thread.
Internal toolPersonal operations
How command flows through the Master App
One home screenEvery venture, one office each
Enter the officeReal 3D scene, agent team at work
Give the orderCommand bridge tracks it: sent, claimed, done
Stay in your wallsEach office touches only its own data
Three offices run in the current setup: a nonprofit, a HealthTech company with its lab inside it, and a playground for other apps and sites. Each office has its own design, roster and data.
The app is shown publicly only in demo mode, on demo data. An office with no live connection shows a not-connected screen: the app invents nothing.
Three offices. One desk.
Broadcast one instruction to every office, or direct one office in its own thread, and watch the claim and completion states move.
The problem
Agent teams need a workplace.
02
No separation, real risk
Without hard walls, one project's agent can touch another project's data. For a nonprofit and a company under one founder, that line has to be structural, not promised.
03
Dashboards that invent
Most dashboards show something whether or not anything is connected. A command tool that guesses is worse than no tool at all.
What it does
What it does.
3D offices you can enterReal three.js office scenes with the agent team visible at work, and clickable agent profiles showing who is doing what.
A command bridgeEvery instruction is tracked through honest states: sent, claimed, done.
Broadcast and direct threadsOne message to all offices at once, or a private thread per office.
Strict data separationRow level security means each office's account can only ever touch its own office's data.
Honest statesA disconnected office says so on screen. The app invents no data, ever.
How it works
Order in. Work out.
STEP 01
Open the home screen
Every office is visible at a glance, with its live state.
STEP 02
Direct the work
Send an instruction to one office, or broadcast to all of them.
STEP 03
Watch it move
Agents claim the work; the command board shows states changing in real time.
STEP 04
Review the record
Completed work and its thread stay attached to the office that did it.
My layer
What I built.
I designed and built the Master App end to end: the per-office 3D scenes, the live agent rosters and profiles, the command tracking system, the broadcast system, and the row level security model that keeps every venture's data inside its own walls.
The scene approach was adapted from an earlier office app I built for a different product, then rebuilt as a multi-office command centre.
Original build by Simanto Mitro.
Internal tool, in active use.
The Master App runs my daily operations across three offices, with interface redesign work (smaller rooms, a wider corridor, a modern decorated look) in progress.
Building something in health?
If this kind of system would help your clinic, organisation or team, the conversation starts with one cup of coffee.