> 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/how-tos/working-with-vault/resolving-conflicts.md).

# Resolving conflicts

When you need to commit changes to a file that other users have also modified in the meantime, you must first merge the two sets of modifications together.

When the two sets of modifications do not overlap, merging is trivial — at least conceptually. But when they do overlap, they produce conflicts.

Teams comes with multiple strategies to help resolve conflicts in IDA database files:

* [Auto-resolve (if no conflicts)](#auto-resolve-if-no-conflicts)
* [Auto-resolve, prefer local](#auto-resolve-prefer-local)
* [Auto-resolve, prefer remote](#auto-resolve-prefer-remote)
* [Interactive merge mode](#interactive-merge-mode)
* [Use local, discard remote](#use-local-discard-remote)
* [Use remote, discard local](#use-remote-discard-local)

## Auto-resolve (if no conflicts)

1. Launch IDA in a non-interactive batch mode, attempting to perform all merging automatically.
2. If any conflict is discovered, bail out of the merge process, and don’t modify the local database.

## Auto-resolve, prefer local

1. Launch IDA in a non-interactive batch mode, attempting to perform all merging automatically.
2. If a conflict is discovered, assume that the "local" change (i.e., the current user’s change) is the correct one, and apply that.
3. Once all merging is done and conflicts are resolved, write those to the local database and exit IDA.

## Auto-resolve, prefer remote

1. Launch IDA in a non-interactive batch mode, attempting to perform all merging automatically.
2. If a conflict is discovered, assume that the "remote" change (i.e., the change made by another user) is the correct one, and apply that.
3. Once all merging is done and conflicts are resolved, write those to the local database and exit IDA.

## Interactive merge mode

This is a manual merge mode.

1. Launch IDA in an interactive, 3-pane mode, allowing the user to decide how to resolve each conflict.
2. Once all merging is done and conflicts are resolved, exit IDA and write the changes to the local database.

## Use local, discard remote

1. Select the local database, ignoring all changes in the remote database.

No IDA process is run.

## Use remote, discard local

1. Select the remote database, ignoring all changes in the local database.

No IDA process is run.


---

# 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/how-tos/working-with-vault/resolving-conflicts.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.