The team is one file.
Define roles, prompts, models, effort, and permissions in YAML. Validate before launch. Start only the seats your task needs.
Explore the team file ↗ OPEN SOURCE. OWNER DIRECTED.Your little
Your little
software factory.
An engineering team of Claude Code agents.
One configuration file. You set the direction.
Talk to your engineering manager. Let a team with distinct roles plan, build, review, and deliver your next application.
YOUR MACHINE. YOUR REPOSITORY. YOUR CALL.
THE TEAM, IN MOTION Illustrative workflow
YOU Product owner
↕ requirements & decisions
EMEngineering managerPlans · coordinates · delivers↗TLTech leadArchitecture & reviewSEEngineersSeparate worktreesQAQualityBehavior & evidenceSECSecuritySpecialist reviewTWTech WriterGuides & documentationWhen neededUXUX DesignerUser flows & interfacesWhen needed
↔ Cross-session collaborationGitHub issues → PRs
One YAML team file
Persistent tmux sessions
Separate git worktrees
No server to run
LESS TERMINAL JUGGLING.Give every part of
Give every part of
the job its own seat.
Writing code is only part of building software.
Planning, architecture, testing, security, UX design, documentation, and delivery deserve their own perspective. Fabrikito sets up the sessions, worktrees, prompts, and permissions so your team can focus on the project.
See how the pieces fit →Independent. In conversation.
Each seat keeps its own context and working tree. Teammates exchange messages, surface concerns, and review from their own expertise.
How messaging works ↗A process comes with it.
Issues before changes. Written assignments. Reviews at exact commits. Behavioral evidence. Merge coordination under your authority.
Follow the workflow ↗SMALL FOOTPRINT. LONG MEMORY.Close the tab.
Close the tab.
The team stays.
Persistent tmux sessions keep working when you detach. Bring every seat back into one iTerm tab, or attach to a single seat from any terminal.
No orchestration server. No background service. A Bash launcher, system Ruby, and tools you already use.
Under the hood →Issue #42 is ready.
→ tl: review the approach
→ eng: implement the change
Waiting on review evidence…
▌Reviewing PR at its exact head.
Checks passed. PR opened.
Verifying acceptance criteria.
Examining sensitive changes.
Checking guides against the code.
Mapping user flows and interfaces.
WHY FABRIKITO?Factory thinking.
Factory thinking.
Human scale.
Fabrik, German for factory.
–ito, a little smaller.
A configurable software team for small-scale development. Start with the roles you need, adjust their models and effort, and grow the roster as the work calls for it.
More active seats use more tokens. Fabrikito does not cap or report cost; check each session’s usage.
Right-size your team →YOUR NEXT PROJECT HAS A TEAM.Small factory.
Build your team ↗