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

# Kodesage Release Notes - 0.9.8

This release introduces Docs Studio 2.0 with a better AI writing agent, linked citations, flexible sections and templates, version history, and images, along with general improvements.

### **2 October 2026**

#### **🎉 Welcome Docs Studio 2.0 🎉**

* Improved AI agent workflow that writes higher quality, more consistent documents
* Citations inside the text that link to their sources
* Add, move, and reorder sections, or start without a template
* Create and edit your own templates, or save a document outline as a template
* Restore earlier versions of a document
* Insert images in the text
* And more.
* Your existing documents and templates move to the new Docs Studio in the background. No action is needed.

#### **General Improvements**

* Show a notice when the step limit is reached or when the context is compacted
* Update vLLM to version 0.30.0
* Filter Redmine items with a saved query
* Retry failed jobs on the Data Sources page
* Improvements for Magic: xpa XML exports are ingested and concepts are available in Hungarian

#### **Manual User To-dos**

* none.


---

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