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

# Kodesage Release Notes - 0.7.7

DOCX export, chain-of-thought polish, and substantially hardened ingestion.

### **17 March 2026**

#### **💬 Ask**

* Failed reasoning steps now show a clear warning rather than an error background.
* A completion summary status in the agentic reasoning view.
* The submitted prompt fills the viewport automatically.
* Fixed the concept collection status ribbon.

***

#### **📄 Docs Studio**

* DOCX export.

***

#### **🎫 Ticket Analyse**

* Ticket auto-commenting has been removed.

***

#### **⚙️ Settings**

* Synchronisation now triggers automatically after a data source configuration change.
* Clearer data source error indicators.
* Data source deletion now cleans up uploaded files properly.

***

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

* In-place extraction of compressed files during repository sync.
* Retries and better error handling across sync and ingestion.
* Symlink safety, status display and branch name normalisation.
* PDF generation extracted into a dedicated service.
* A simpler queueing architecture with one fewer moving part.
* Secrets are no longer written to temporary files.


---

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