GitDB Desktop

GitDB Desktop is a desktop app for working with AI coding agents. You run Claude Code and Codex CLI — the two agent command-line tools it supports — in conversations called threads, and you browse, edit, review and commit the code they work on in the same window.

Every thread works in a workspace: either a folder on your computer or a GitDB repository.

GitDB Desktop drives the Claude Code and Codex CLI you install yourself — it does not ship its own copy of either. See Install GitDB Desktop for the one-time setup.

The four viewsCopy Anchor Link

The navigation in the top bar switches between four views:

Two of the views show a count next to their name when there is something to count:

• Code shows how many agent sessions are running right now.
• Git shows how many uncommitted changes are waiting in a GitDB repository. Local folders never show this badge.

CodeCopy Anchor Link

The Code view is where you start threads, send messages, answer the agents' permission requests and watch their work. See Threads and sessions, Agents and The composer and status bar.

GitCopy Anchor Link

The Git view works on both kinds of workspace, with two exceptions that exist only in GitDB:

• Pull Requests — in a local folder the section says: "Pull requests are GitDB only — this workspace is a local folder."
• Outline — in a local folder the section says: "The outline is GitDB only — the AST index lives in GitDB and this workspace is a local folder."

FileCopy Anchor Link

The File view opens files from the workspace in an editor. What saving does depends on the workspace, and the editor says so next to the file's path:

• In a local folder: "⌘S writes to disk" (Ctrl+S on Windows and Linux).
• In a GitDB repository: "⌘S → GitDB WIP (unstaged) — not a disk write". Your edit is saved in GitDB as an uncommitted, unstaged change — the app calls these changes WIP (work in progress). Nothing is written to your disk. Stage and commit your changes from Git → Changes.

MemoryCopy Anchor Link

The Memory view works only with a GitDB repository. In a local folder it shows "Memory lives in GitDB" and "Connect to a GitDB repo to recall and store agent memory. Local folders have no memory store."

GitDB memory has no "list everything" view, so the Memory view starts empty. Run a Recall to see results. You can also Store new memory, and from a selected result, Re-anchor to current (attach it to the file open in the editor) or Forget it.

Local folders and GitDB repositoriesCopy Anchor Link

Opening a workspaceCopy Anchor Link

Use the workspace chip — the first item on the second row of the top bar (it reads "Open a workspace" when nothing is open):

• Open local folder… (⌘O on macOS, Ctrl+O on Windows and Linux) opens a folder on your computer.
• Connect to GitDB repo… opens the Connect to GitDB dialog. Pick a repository from Recent repositories, or open one of your Organizations and pick one of its repositories. Choose a Branch, then click Sign in with browser — or Connect, for a repository you've connected to before. The dialog notes that the credential is encrypted by your operating system's keychain.

The chip also lists your recent workspaces under Other workspaces, so you can switch back to one in a click.

For service accounts, the dialog also has Use an API key instead (advanced). An API key you type there is never stored — "you will be asked again next launch".

What changes between the twoCopy Anchor Link

Next stepsCopy Anchor Link

1. Install GitDB Desktop and at least one of the two agent CLIs.
2. Sign in, or choose offline mode.
3. Open a workspace and start your first thread.