Workspaces
Keep a project’s code, members, configuration, and agent work together.
A workspace is the shared home for repositories, members, sessions, tasks, specifications, rules, skills, and integrations. Select it before starting work so Uno uses the intended project context.
Choose the workspace that owns the outcome
Use the workspace switcher to move between projects you can access. Check the repository list and role when similarly named workspaces belong to different teams.
A separate session is usually enough for an independent task in the same project. A separate workspace is useful when source access, membership, configuration, or project ownership should differ.
Create and configure
Use the workspace creation action offered by the app, then complete its setup. Additional owned workspaces can require an active plan or wallet funding. Read the current requirement rather than assuming another workspace is free to create.
Owners and admins manage shared configuration. Attach repositories, prepare manifests, set model connections, and review team access. Onboarding can finish before all snapshots are ready; environment readiness is a separate state.
Share access and context
Add existing Uno users through Members. Use rules and skills for project conventions, secrets for credentials, and external tools when work needs more than repository content.
Your role applies across the web app and authorized integrations. An MCP connection does not grant more access than its user. A Session API key is scoped to its owning workspace.
Understand shared funding
Workspaces participate in organization-level funding. Wallet credits belong to the shared organization, not to the personal user who started a session. Inspect the current balances and access requirements before starting recurring or parallel work.
See plans and credits, activity, and how work fits together.