A live 3D city that shows a business owner what their AI agents are doing and holds every consequential step for a person to approve.
What it is
Owners who hand work to AI agents lose sight of it. Agent City turns agent work into a city you can read at a glance: each district is a stage of work, agents walk between buildings, and the integrations they touch light up as they are used. Consequential actions wait in the Human Approval Hall until a person decides.
What we built
One normalized event model for agents, work items, capability calls, approvals, integration activity, and outcomes, reduced into a single world state. Source adapters for several agent runtimes, Agent Forge execution events, DASP envelopes, and a business event schema, each with sanitize and translate steps. A privacy layer that strips names, contact details, prompts, and secrets before anything renders and fails closed. A Three.js renderer with Business and Developer views, a capability inspector, and five WebMCP tools built with Agent Forge.
How it is used
The public demo plays eight synthetic scenarios. In the flagship one, a rehearsal inquiry for The Rectangle is classified, routed, and synced to the CRM, and “Send deposit invoice” waits for approval before the invoice goes out, payment arrives, and the booking is confirmed. Approvals in the demo are scripted, and the demo bundle contains no API calls, live data, or secrets.
Evidence
What it shows
What changed
A business owner can read agent work as a city, and every consequential step waits in the approval hall until a person decides.
One event model
Agents, work items, capability calls, approvals, integration activity, and outcomes are normalized into one event model and reduced into a single world state. The privacy projection fails closed.
Seven source adapters
Adapters for several agent runtimes, Agent Forge execution events, DASP envelopes, the Rectangle site’s business events, and the Atlas feed.
Renderer and scenarios
A Three.js renderer with Business and Developer views and eight scenarios, seven of them business scenarios.
Five WebMCP tools
Defined with Agent Forge and registered in the browser.
Static demo bundle
The public demo makes no API calls and contains no secrets.
Context
Approvals in the demo are scripted and all scenario data is synthetic.
Farwhen
Behind the experience
The systems this project uses, grouped by the part of Farwhen they belong to.
Spatial Orchestration
The room becomes part of the experience.
Agents & Operations
Tools for people and agents.
Our technology
What it runs on
- Agent City
This is Agent City itself.
- Agent Forge
Defines the demo’s five WebMCP tools and emits the execution events the city renders.
- DASP
DASP envelopes are one of the event sources the city adapts.
Built with
Credit
Built by Dream Awake Labs. Private repository. All scenario data is synthetic.
Get in touch
Tell us what you have in mind.
Describe it in a few sentences. You get a draft brief to review before anything is sent.