Shared codebase context for teams: one graph per org
By Steven Van ·
Teams get a seat per developer, join requests for orgs already on Graphify, and shared memory across one workspace per GitHub organization.
Graphify now supports one shared workspace per GitHub organization, so every developer and agent on a team queries the same code graph. Graphify indexes each repository once and keeps the graph current from its default branch. Members and connected agents read it through the console or the hosted MCP server, so nobody has to rebuild context locally.
The change is described in Shared codebase context for teams: one graph per org.
Teams plan and upgrading
The Teams plan gives the workspace a seat for each developer, and the number of seats is chosen at signup. On upgrade, an existing workspace can be converted into a team workspace, keeping its repositories, graphs, memory and address. Starting a new workspace is the other option.
Joining an org that already has Graphify installed
If a teammate has already installed Graphify on the organization, the next person now sees which workspace owns the GitHub installation and can request to join. Graphify checks that the requester is a member of the organization on GitHub, and the workspace owner approves the request. This replaces an error that previously stopped the second person on a team from connecting. Teammates do not need their own GitHub App install.
Access and workspaces
- Members see the repositories in the workspace they belong to.
- Owners and admins invite people from Members and can see how many seats are in use.
- Anyone who can read a repository can open its Contributors page.
- Each person owns one workspace and can join others by invite. A switcher at the top of the sidebar separates "Your workspace" from "Shared with you", and team workspaces carry a Teams badge.
- Each agent installation keeps its own workspace selection, so a laptop pointed at the team workspace and a desktop pointed at a personal one do not overwrite each other.
- Agents sign in to the hosted MCP server through the browser, so they do not need their own API keys.
Shared memory
Developer Memory and the Learn page are available to every user, and what one person teaches Graphify about review findings applies to the whole workspace. Marking a finding as wrong with @graphify wrong helps quiet it across the workspace without changing any formal verification verdict.
Developers who want a local graph for experiments can also run uv tool install graphifyy alongside the workspace.
