Stop rebuilding product understanding project by project.
Give each product or client project a shared model that people, AI and connected tools can use as the work continues.
The account is organised as workspaces, then projects, then repositories. Each repository gets its own model, and everyone you invite to the team reads that same model — there is no personal copy that quietly falls behind. One key per person covers every project that person is allowed to read, so a new client project is another project in the same workspace rather than another setup.
Create a workspace and a project inside it
Connect the repositories that belong to that project and build them
Invite colleagues and give each one owner, member or viewer
Hand out the MCP key so agents can list the projects they may read
Add the next product or client as another project in the same workspace
Understanding is not pooled across repositories: each one is read on its own, questions are asked of one at a time, and nothing notices that two projects describe the same thing. Meanings you confirm on a document are kept with the repository you confirmed them in, not shared across the workspace. How many workspaces, repositories and seats you get is set by the plan, and every build and rebuild draws on one shared credit pool.
See it on a real product.
Three models are published in full and open without an account. Ask one of them the question this page is about.