Preparing your workspace…
Preparing your workspace…
Workspaces
Each client, product or codebase gets its own workspace with its own memory, connected apps and people. Nothing mixes, and one view can still read across the ones you belong to when you ask.
Free 14-day trial — no card
The three rules
A parent can read its nested spaces when you switch that on. Anything new is saved to the workspace you are in.
A combined view includes only the spaces you are a member of. Membership is checked on our servers on every request.
Invite a client to one project. They see that project only, never your other workspaces, and email and calendar details stay with admins.
Four kinds
Your single everything space — you have exactly one. While it is just you, it reads across all your other workspaces. Invite someone and it reads only its own.
A focused space that keeps to itself. Best for a client or initiative: it reads only its own data, so it is the safe one to share.
A hub that holds the spaces nested inside it. Say, one product built from several repos — it reads them only when you switch that on.
One code repository's own space. Made for you the first time a coding agent connects from that checkout — no setup.
No guessing
One pill at the top names the workspaces behind your numbers, and “Where these numbers come from” shows what each one adds — including the ones left out.
How they fit together
Put repos and projects inside a Container to mirror how the work is really organised. Nesting keeps things tidy; it does not quietly merge data.
Inside every workspace
What your meetings, documents, code and AI conversations taught it — cited, and kept current.
A board for the work, with goals that forecast when they will land at your real pace.
Slack, GitHub, Google, Microsoft 365, your CRM and more — connected to this workspace, not to everything.
Scheduling, notes and follow-ups that stay with the client or project they belong to.
Specialist agents that work from this workspace’s memory and report back on its board.
See what each workspace costs to run, and set its own monthly limit — per client, per product.
Your team, on your terms
Bring in teammates, clients or contractors by email. Each gets a clear role, and sensitive categories stay private until both of you agree.
These rules hold everywhere — in the app and inside every AI tool a member connects.
Your AI agents, in the right place
The same workspace follows you into Claude, ChatGPT, Gemini, Cursor and the rest — so an answer about one client never borrows from another.
Coding tools connect from a checkout and land in that repo’s own workspace automatically — created on first connect.
When you link a chat assistant, you pick the workspace it may use. Other workspaces stay out of reach.
Ask your AI to move this chat to another workspace you belong to — or to look something up in one without switching.
Your membership is verified on our servers each time, and access is refused if it can’t be confirmed.
Each read is limited to the workspaces you are allowed to see — nothing is exposed directly to browsers or apps.
Connected-app credentials are encrypted at rest. Enterprise workspaces can use their own key.
Disconnect an AI or remove a person, and their access to that workspace ends.
Start in a minute