Crew is the shared workspace: one board, several people, agents in parallel with provenance for every change. None of it ships in the alpha, and this chapter says what does.
Arrives with the public beta. Crew: shared projects, boards and sessions with private projects inside; seats per person with free viewer seats; the Owner, Maintainer, Contributor and Viewer roles; a per-seat approval limit; a 90-day audit log with export; a team evaluation started from the Licence sheet; and the Jira, Slack and Teams integrations. Nothing in that list is built, and the Licence sheet's Crew rows say so.
| TODAY | RULE |
|---|---|
| Free has no device limit | The alpha plan and Free have no device limit. Only Solo is capped, at three devices. You can sign devices out from the Licence sheet's Devices tab. |
| GitLab | Merge requests open from Deliver in gitlab-mr mode, and the Deliver panel links the pipeline page for the branch. GitHub gets the same with pull requests and Actions. See review. |
| Action history | Kept 7 days, locally, with a CSV export of the rows on screen. Today that CSV is how you hand a reviewer what an agent did. See history. |
| One person, one machine | Everything a card touches lives on the machine that ran it. A card cannot be assigned to someone else, and a DETACHED agent is another machine that owned a card and went away. |
Share a repository the ordinary way. Each person runs their own Grid Console over their own checkout; cards live in each person's workspace and reach the others as branches, pull requests and merge requests. Worktrees keep several agents apart on one machine, and git keeps several people apart.
Plugins are per workspace, installed from the registry, with an Allow unverified plugins switch you turn on deliberately. There is no shared, pinned plugin set across a team yet; each person installs their own.
Seats will be per person, not per machine; Crew has no device limit. Roles will decide who approves and who watches. Every decision will record who took it. Integrations will be plugins, shared and version-pinned across a workspace, so a team is never running four versions of the same hook. Those are the commitments; the dates are in the roadmap, and the prices in pricing.