> 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.6.x.md).

# What's new in 0.6.x

Knowledge base early access, the Ask Kodesage REST API, a much stronger Docs Studio, and Jira and Redmine tickets as data sources.

### **September – November 2025**

#### **💬 Ask**

* A public REST API for Ask Kodesage.
* Smarter reference reranking for more accurate answers.
* Answer style options, a refreshed input field and copyable generated code.
* New data source filters and faster search.

***

#### **📄 Docs Studio**

* PDF export for generated documentation.
* Repeated Docs Studio interface upgrades across the line.
* A new RPG parser and faster tagging of code files.

***

#### **🎫 Ticket Analyse**

* A unified Ticket Analysis interface.
* Jira and Redmine tickets usable as data sources.
* Jira API updates and ticket summaries.

***

#### **⚙️ Settings**

* Confluence references and simplified ingestion.
* Knowledge base early access.

***

#### **🔧 Platform & Performance**

* Image and PDF support.
* Major performance and stability work, including faster model responses.
* Framework upgrade for the web interface.


---

# 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.6.x.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.
