> For the complete documentation index, see [llms.txt](https://docs.hex-rays.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hex-rays.com/ida-9.5/add-ons/teams/getting-started/getting-started-git.md).

# Git

Since IDA 9.4, Teams includes Git integration, bringing familiar version control workflows to collaborative reverse engineering. **Git-based repositories are recommended for new Teams projects.**

{% hint style="success" %}
Using Vault already? See the [Vault to Git Migration](/ida-9.5/add-ons/teams/how-tos/migrating-from-vault-to-git.md) tutorial to get started.
{% endhint %}

The Git backend removes the need for a dedicated Teams server (previously known as the *Hex-Rays Vault* server). If your team already has a Git provider account, such as GitHub, GitLab, or any self-hosted instance, that's all you need: no dedicated Teams server installation, no admin provisioning, and no additional credential management. Every user authenticates with their own Git account, points IDA at a repository, and starts collaborating immediately.

![Teams menu with Git backend](https://492083732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFP6ibt8r6WPBHTqekG9u%2Fuploads%2Fgit-blob-f897437e436a6a183bb92a637b604163ab02d5e2%2FIDA_Teams_Git_menu.png?alt=media)

{% hint style="info" %}
You can switch to the legacy Vault backend under **Options → General →** [**Teams**](/ida-9.5/ida-actions/options.md#teams-options).
{% endhint %}

## Prerequisites

* IDA Pro 9.4 installed and an active IDA license with Teams add-on

## Setup

Before using the Git backend commands under the **Teams** menu, complete the following steps:

1. **Install Git.** You only need a system-wide Git installation; IDA ships `git-ida` itself. If Git is missing, IDA will tell you when you trigger a Git action.

{% hint style="info" %}

## Working with large databases?

Install [Git LFS](/ida-9.5/add-ons/teams/concepts/git.md#large-file-storage-lfs) once per machine first (`git lfs install`). Then `git ida install` checks for it and handles large databases with the chunked store automatically.
{% endhint %}

2. **Run `git ida install` once per machine.** This registers `git-ida`'s filter, merge, and diff drivers in your global Git config, so any repository you clone, even outside IDA, checks out real databases right away instead of placeholder stubs. IDA runs this for you automatically the first time its Git integration runs; run it yourself only when setting up a script or CI machine. `git ida uninstall` reverses it.
3. **Set up a repository** for the IDB you want to work with:
   * **Teams → Create Repository** — turns the directory containing the current IDB into a new Git repository. Optionally, link it to an empty remote URL at this step.
   * **Teams → Clone Repository** — downloads an existing shared repository to a folder of your choice.
4. **Set your Git identity** (user name + email). On your first commit, IDA opens the *Repository Settings* dialog so you can set them. If you already have a global `user.name` / `user.email` configured, IDA picks them up automatically.

{% hint style="info" %}
For HTTPS remotes, IDA will prompt you for credentials the first time they are needed and store them securely in the OS keychain.
{% endhint %}

## What's Next?

You're ready to collaborate on your IDB. See [Working with Git](/ida-9.5/add-ons/teams/how-tos/working-with-git.md) for day-to-day operations: committing, pushing, pulling, viewing history, and resolving conflicts.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hex-rays.com/ida-9.5/add-ons/teams/getting-started/getting-started-git.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.