> 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/add-ons/teams/release-notes.md).

# Release Notes

{% hint style="success" %}

## Separate release cycle

From version 9.5 onward, Teams follows its own release schedule, independent of IDA.
{% endhint %}

## Teams v9.5

### Agentic diffing for IDA databases

IDA produces a readable, structural diff right in the terminal, as plain unified-diff text. It works in scripts, in CI, and as input for AI agents.

See [Diffing IDA databases with `git diff`](https://docs.hex-rays.com/add-ons/teams/how-tos/git-diff.md) for details.

### LFS chunked store

Large databases can be cloned and checked out in seconds instead of minutes. Run `git lfs install` to enable it.

See [Large File Storage (LFS)](https://docs.hex-rays.com/add-ons/teams/concepts/git.md#large-file-storage-lfs) for details.

### Global install

Run `git ida install` once per machine. Cloning a repository then works immediately, no per-repository setup needed (creating a new one still needs `git ida initialize`).

See [Using `git-ida` from the command line](https://docs.hex-rays.com/add-ons/teams/how-tos/git_ida_cli.md) for details.


---

# 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/add-ons/teams/release-notes.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.
