Teams
Invite the people you work with. A mission can belong to one of them, a question can go to a named teammate, and your AI warns you before it edits a file someone else is changing.
Builder and Fleet
What it is
One person with an AI crew is simple. Two people on one project is where things go wrong: both change the same file, questions go to the wrong person, and nobody knows who is working on what. Georgi and Mira are developers on one project, and Georgi's plan touches the refund code that Mira wrote.
Teams are how ShipItFam handles that. People get seats, missions get owners, questions reach the right person, and the crew knows who is on the project.
Seats and invites
A seat is a person. Free has 1 seat, Builder has 5 and Fleet has 10. Seats are counted across all of the owner's projects. If you need more than ten, ask us.
You invite someone by email, as a lead or as a developer. They accept the invite when they sign in.
Assigning a mission
A mission is one job for the crew. It can be assigned to a person. Its plan and its "ship it?" question then go to that person's Helm, which is the feed of things that need them. The mission runs on that person's own computer, in their copy of the code, through their worker, which they start with one command.
npx shipitfam workIf their computer is off, the mission waits for them.
Asking a teammate
A question can be addressed to a named teammate. It lands on their Helm, and any member can still answer it. The crew also knows who is on the project and what each person knows best, so in the middle of a mission it can ask a named person a question. Questions on missions that nobody is assigned to show to everyone.
Two people, one codebase
ShipItFam tracks which files each mission is changing, and which files each person's own Claude session is changing. Before your Claude edits a file that a teammate is changing, it tells you. It is a heads-up, and it never blocks the edit.
Georgi's Claude is about to edit the refund file. It tells him Mira's mission is working in it. He picks another file or waits. This needs the hooks that come with the Kraken, installed in your Claude Code.
What only a lead decides
Three decisions are for leads only: accepting a security risk, importing a skill, and pushing to production.
For developers
Two programs run on your machine, and they do different jobs. The worker builds: it runs mission steps in your copy of the code. The Kraken answers: it replies to teammates' AI assistants from your code and never changes a file. The Kraken comes with Fleet.
On each plan
| Plan | Teams |
|---|---|
| Free | 1 seat, so no teammates |
| Builder | 5 seats, invites, assigned missions, questions to named people |
| Fleet | 10 seats, everything in Builder, plus the Kraken for each person |
Related
Got a team to bring along?
Join the waitlist. We'll let you in as soon as there's a spot.
Join waitlistNext feature: The Kraken →