What is GitDB
GitDB is a code-native database for AI agents and the engineers who ship with them. Start here for an overview and the key terms used throughout these docs.
GitDB is a code-native database for AI agents and the engineers who ship with them. Your code lives in GitDB as Git repositories, and people and AI agents work on the same repositories through the same service.
- Engineers browse code, review pull requests, and manage access on gitdb.co, and push and pull with ordinary Git over SSH or HTTPS.
- In VS Code, the GitDB extension opens your repositories as workspaces — browse, edit, and commit with no clone on disk.
- On your desktop, GitDB Desktop runs Codex and Claude Code in one thread, working directly on your GitDB repositories or local folders.
- AI agents connect over MCP (Model Context Protocol). Point Claude Code, Cursor, Windsurf, or another agent IDE at a single MCP endpoint and it gets the whole surface: structural (AST) search, semantic search, reading, writing, committing, merging, and memory.
Three ideas, one product
Unified MCP. One endpoint for every agent IDE. AST-aware reads let an agent pull the code structure it needs instead of reading whole files.
Code-aware memory. Fixes, gotchas, and architectural decisions are anchored to the exact AST node they describe, and flagged stale the moment that code changes, so your agents stop solving the same bug twice.
A2A swarm. Multi-agent workflows (Architect → Coder → Reviewer → Tester) with per-role persistent memory. Handoffs between agents are pointers (file paths and line ranges), not raw code.
Some capabilities depend on your plan. See Billing and plans.
Where you work with GitDB
| Product | What it is |
|---|---|
| gitdb.co | The web platform: your account, repositories, pull requests, organizations, access control, and billing. |
| GitDB Desktop | A desktop app that runs Codex and Claude Code in one thread on your GitDB repositories. |
| GitDB VS Code extension | Opens GitDB repositories as workspaces in VS Code. |
Key terms
| Term | What it means on GitDB |
|---|---|
| User | Your personal account. Your username is also your personal namespace: repositories you create live at gitdb.co/<username>/<repo>. |
| Organization | An account that owns repositories and groups people. Organization logins share one namespace with usernames. Every member has a role: owner, admin, member, or readonly. |
| Repository | A Git repository hosted on gitdb.co. Repositories are private; public repositories are coming soon. |
| Branch, tag, commit | Standard Git concepts. Each repository has a default branch, which is what git clone checks out and what the repository home page shows. |
| Pull request | A proposal to merge one branch (compare) into another (base), with reviews, line comments, and a merge button for organization owners and admins. |
| Team | A named group of organization members. Teams are used as targets for read access rules. |
| Read access | Rules that control which members may read files matching a path pattern, either by denying a principal or by making a path need-to-know. An enterprise capability. |
| Personal access token | A token you generate in Settings so scripts and tools can act as you, limited by the scopes you pick and an optional expiry. It is also your password for Git over HTTPS. |
| SSH key | A public key you add in Settings. It authenticates Git over SSH. |
| Enterprise | The layer above organizations. One enterprise owns several organizations, holds one consolidated subscription, and can enforce policies, single sign-on, and SCIM provisioning across all of them. |
Next steps
- Getting started: create your account, push your first repository, and generate an access token.
- gitdb.co platform: everything you can do in the web app.
- GitDB Desktop: the desktop app for agent threads on GitDB repositories.
- GitDB VS Code extension: work on GitDB repositories inside VS Code.