> For the complete documentation index, see [llms.txt](https://docs.kodesage.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kodesage.ai/release-notes/whats-new-in-0.5.x/git.md).

# Kodesage Release Notes - 0.5.7

Thinking mode option and data source filter indicator for Ask Kodesage,, search & performance enhancements, and new regression test catalogue.

### **16 July 2025** <a href="#release-notes-kodesage-0.5.7-16-july-2025" id="release-notes-kodesage-0.5.7-16-july-2025"></a>

#### 💬 **Ask Kodesage – New Features** <a href="#ask-kodesage-new-features" id="ask-kodesage-new-features"></a>

* **Thinking Mode Option**: A new mode enabling deeper reasoning for improved answer accuracy. Note: this may slightly increase response times.
* **Filter Indicator**: Easily see if any filters are active when querying.

***

#### 📚 **Docs Studio – New Features** <a href="#docs-studio-new-features" id="docs-studio-new-features"></a>

* **New Template**: Added “Regression Test Catalogue” to streamline documentation of test cases.
* **Manual References only**: You can now manually add references without performing search.
* **Thinking Mode** is active by default for better accuracy

***

#### 🔍 **Issue Analysis – Updates** <a href="#issue-analysis-updates" id="issue-analysis-updates"></a>

* **Improved Ticket Listing**: Ticket display in Issue Analysis is clearer and more structured.
* **Thinking Mode** is active by default for better accuracy

***

#### 🛠️ **General Improvements** <a href="#general-improvements" id="general-improvements"></a>

* **Search Enhancements**: Smarter document search logic for more relevant results.
* **Performance & Fixes**: Numerous backend fixes and performance improvements, especially around Docs Studio and Mermaid diagram rendering.


---

# 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.kodesage.ai/release-notes/whats-new-in-0.5.x/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.
