Hackeroom dev-house

Give Claude Code a dev team. You create the members — a name, a role you write, skills you attach, a model, a permission mode — and they fill seats in a workflow you can sit and watch.

Hackeroom — Officelocalhost:3000 · run #48
FOCUS
BUILD
CREATE
CAFÉ
Runs automatically · roughly 22 seconds
Squadlive tool calls, as they are gated
Teamwho is in, and what they cost
spent this run $0.00
1

There is no built-in squad

The team is whoever you hire. Nothing is hardcoded — not the names, not the count, not the models. An empty slot is a skipped phase.

2

Skills belong to one member

Each member's skills are packaged as a plugin loaded for their session only, so a long document costs about fifteen tokens of context until it is actually needed — and nobody else can see it.

3

Limits are enforced, not requested

A PreToolUse hook gates every call against a capability manifest written at run start. Members cannot write to .claude/, so they cannot edit their own permissions.

4

You can see the bill

Tokens and spend are attributed per member and per model, so an expensive member is obvious — and moving them to a cheaper one is one edit.