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

# Kodesage Release Notes - 0.7.2

New metrics and usage reports, improved PDF viewing and ingestion, refined navigation, and enhanced Ask Kodesage context and reference management.

### **21 January 2026** <a href="#release-notes-kodesage-0.7.2-date" id="release-notes-kodesage-0.7.2-date"></a>

#### 📊 **Metrics Enhancements** <a href="#metrics-enhancements" id="metrics-enhancements"></a>

* Introduced a new **Download all projects statistics** button, providing detailed usage statistics via a downloadable report.
* Added **new metrics**, including **time-to-first-token (TTFT)** for Ask Kodesage and **API usage stats**

***

#### ✨ **General Improvements** <a href="#general-improvements" id="general-improvements"></a>

* Added a built-in **PDF viewer** for Data Sources and manually tagged references.
* Improved **PDF upload and processing status**, making ingestion progress clearer and more reliable.
* Refined and enhanced the **left-side navigation menu** for better usability.

***

#### 💬 **Ask Kodesage Enhancements** <a href="#ask-kodesage-enhancements" id="ask-kodesage-enhancements"></a>

* Enabled adding of **PDFs and Confluence pages using @** to context
* Improved the **Reference panel** and refreshed the **manual tagging** experience


---

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