Currently buildingprivate
Agent Office
A private, local control plane for a small team of AI coding agents. It coordinates Claude Code and Codex sessions, gives every agent its own isolated workspace and a fixed budget, sends approvals to a phone-friendly page and shows the team as an isometric pixel-art office.
Private project. The code is not public and the project is under active development. Test versions are available: send a request.
How it works
- AssignEvery project gets its own floor with agents, roles, rules and a work queue. One active session per agent; unfinished requests are handed on to a colleague.
- IsolateEach agent works in its own Git worktree. Commits are brokered, and the developer’s own checkout is never touched.
- ApproveRisky operations wait for a decision on the phone. A changed, expired or replayed operation needs a fresh one.
- WatchThe office shows who is working on what, with tickets, chat and a budget view of the real usage windows of the subscriptions.
Agent World
A layer on top of the office: every employee becomes a resident of a small city, with needs, money, a home and hobbies. A good or a bad day may shape how they work — never whether they work safely and honestly.
- Needs, a wallet and a wardrobe: clothes wear out, and every figure is drawn in what it actually wears.
- A city with districts, a supermarket, café, bakery, bookstore, gym and a clothing store, stocked with real goods from a warehouse.
- A fixed workday with guaranteed breaks and free time; off duty, residents decide on their own where to go.
- Work is offered, not imposed: it starts when the resident accepts it or the owner overrides that on the record.
- Optional small talk between idle colleagues, from which personalities and relationships grow; every change can be traced and undone.
Off by default. The life simulation makes no model calls of its own; the small talk runs within a weekly token limit.
Principles
When sandboxing, sign-in, a policy check or a provider check is not available, nothing runs.
Nothing is pushed automatically. Pushes, syncs and risky tool calls wait for an explicit decision.
The app binds to the local machine and is reached on the LAN through HTTPS. Credentials never reach the agents.
Where it stands
- Server and browser appWorking
- Isolated workspaces and brokered commitsWorking
- Approvals, budgets and usage windowsWorking
- Safety and provider verificationNot passed yet
- Agent World: needs, money, cityBuilt, acceptance open
- Agent World: workday, free time, own decisionsBuilt, acceptance open
- Agent World: thinking, emotions, relationshipsPlanned
A passing test suite does not mean it may run on its own: autonomous use stays off until the safety and provider checks have passed on the real machine.