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

# Kodesage Release Notes - 0.7.6

Chat input fixes, a concept collection status banner, and password change in settings.

### **5 March 2026**

#### **💬 Ask**

* Fixed pasted text alignment and cursor position in the chat input.
* Fixed losing text selection when dragging into the input field.
* A concept collection status banner.
* Fixed the agentic toggle flickering.
* Fixed agentic summarisation becoming stuck in progress.

***

#### **⚙️ Settings**

* Password change in user settings.
* Personal access token authentication for on-premise Confluence.
* Faster permission checks and smaller responses.

***

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

* A standalone frontend architecture.
* Support for an additional large model.
* Fixed diagram escaping and rendering.
* Resolved inconsistencies when deleting resources and projects.


---

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