Teams
Shared workspaces with roles, task assignment, pooled AI credits, and a team activity feed.
A team is a shared workspace. Projects created under a team are visible to its members; AI credits are pooled across the team.
Creating a team
Create a team from the sidebar. The creator becomes the team owner. A team has a name and a billing status (active, trialing, past_due, or cancelled) tied to its subscription — see Plans & Credits.
Roles
| Role | Capabilities |
|---|---|
| Owner | Full control of the team, members, and billing. |
| Member | Works on team projects and is assignable to tasks. |
Invitations
Owners invite people by email. Pending invitations are tracked until accepted; once accepted, the person becomes a team member and can see the team's projects.
Shared projects
Projects created in the team workspace belong to the team (team_id set) rather than to an individual. Members switch into the team workspace from the sidebar to see and work on them. Personal projects remain private to their owner and are never exposed to the team.
Task assignment
Team tasks carry an assigned_to list, so work can be assigned to one or more members. Assignment changes surface in the team Activity feed.
Pooled credits
A team has a shared credit pool rather than per-member balances, so AI generation draws from the team's allocation. Team members who connect their own provider key via Bring Your Own Key run generation on that key and don't draw from the pool.
Team activity
When you're in a team workspace, the Activity feed is team-scoped — it shows actions across the team's projects, attributed to the member (or MCP key) that performed them. In a personal workspace it shows only your own activity. See Activity feed.
Related
- Plans & Credits — Team plan tiers and seat-based pricing.
- Activity feed — team vs. personal scope and attribution.