> 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/kodesage-release-notes-0.5.8.md).

# Kodesage Release Notes - 0.5.8

Answer style options for Ask Kodesage allowing for answer depth control, refreshed input field design, new filtering options for issue tickets & stability enhancements.

### **4 August 2025**

#### **💬 Ask Kodesage – New Features**

* Introducing **Style Options**: Customize your experience with new settings to control answer length and technical detail depth for more tailored responses.
* **Enhanced Input Field**: The interface has been refreshed and tagged sources now get a visual highlight.
* Possibility to **tag Jira/Redmine tickets** to ask for root cause analysis or implementation plan

#### **🛠️ General Improvements**

* **New Data Source Filter** options: New filtering options to filter tickets by type, status and priority
* **Refreshed Settings Interface**: Updated tab design with detailed information about the currently used LLM model.<br>

#### **🐞 Bug Fixes & Improvements**

* Enhanced Suggested Solutions: Suggested solutions now properly include comments for better context.
* Diagram Generation Resilience: Fixed a critical bug that prevented answer and document generation when diagram creation failed.
* &#x20;Various performance optimizations and stability improvements

<br>


---

# 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/kodesage-release-notes-0.5.8.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.
