agent-lab.
we run a team of ai agents and needed to keep track of what was approved.

the problem.
- who
- our own studio.
- before
- working with a team of ai agents means many roles, sessions and proposals at once. it's easy to lose track of who did what, and of what was actually approved.
- what was needed
- one place to see which agent is working, and to approve every change first.
how we thought about it.
agents only propose; nothing changes until we approve it.
because with many roles at once, it's easy to lose track of what was actually approved.
from sketch to screen.
- sketchmany roles, sessions and proposals at once, drawn as one map.
- measuresized for a laptop first, and on a phone.
- wireframeteam map, live sessions, project memory, blueprint, in grey.
- screena local dashboard. agents only propose; we approve.
what we built.
agent-lab, a local dashboard for our claude code agents: a map of every role on the team, the live sessions, the project memory, and a blueprint where agents only propose and nothing changes until we approve it.

how we use it.
day to day at the studio: we see which agent is working, start new projects from our team templates with a preview before any file is written, and review what agents propose before it becomes direction.

status.
our own tool, built and used every day. not for sale.
have something like this? tell us.
sending a message doesn't commit you to anything.