> 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.6.1.md).

# Kodesage Release Notes - 0.9.6.1

This release adds the Qwen 3.8-27B LLM for better quality, selectable reasoning effort in Ask Kodesage, small Settings, UI improvements, and CLI updates.

### **14 September 2026**

#### **New Features**

* New LLM: Qwen 3.8-27B, for significantly improved quality and stability.
* You can now select Medium or High reasoning effort in Ask Kodesage sessions.

#### **General Improvements**

* The active LLM is now shown on the Settings / General tab.
* Password change has moved into a modal.
* Various small UI enhancements.

#### **CLI Improvements**

* The knowledge base is now on by default inside a project.
* The CLI's own edits are auto-committed under a separate Git identity, so its work stays clearly separated from yours.

####


---

# 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.6.1.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.
