Workspace membership and roles
Invite team members, separate personal and work spaces, and prepare for enterprise SSO/SCIM when procurement needs it.
Loading…
Loading…
AGI for teams
Bring chats, files, projects, artifacts, and code into one shared workspace. Explicit policy covers what runs locally, what goes through your own provider keys on Desktop and CLI, and what runs in AGI managed cloud.
Team admin
Invite team members, separate personal and work spaces, and prepare for enterprise SSO/SCIM when procurement needs it.
Local, BYOK, and Cloud stay separate, labeled routes for every member. Org-wide provider policy and BYOK enforcement are scoped on enterprise contracts.
Members connect services with individual authentication and per-tool approval boundaries that stay visible. Workspace-level connector policy is scoped on enterprise contracts.
Store files, instructions, memory, chats, and artifacts under the workstream so the team stops rebuilding context.
Local work costs nothing and BYOK bills go straight to your providers. Managed spend applies when a workspace uses AGI managed cloud.
Provider labels and tool approvals stay visible in the product. Audit export for review is scoped on enterprise contracts.
Rollout plan
| Phase 1 | Start with Local and BYOK for high-signal users. No managed compute commitment needed. |
| Phase 2 | Enable shared projects, apps and connectors, and provider policy for repeat workflows. |
| Phase 3 | Bring users onto AGI managed cloud, open in public alpha, for hosted sync and managed compute. |
| Phase 4 | Move to enterprise controls when SSO, audit export, retention, and contract terms are required. |
Public launch: July 12, 2026
Start the team on free Local and BYOK modes today, then move selected users onto AGI managed cloud, which is open in public alpha.
Public launch · July 12, 2026