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

# Kodesage Release Notes - 0.9.7

This release adds paragraph-level citations in Ask Kodesage and Docs Studio, video upload and transcription as a data source, better Jira and Confluence sync and CLI improvements.

### **21 September 2026**

#### **New Features**

* **Citations**: Every response in Ask Kodesage and Docs Studio is grounded in cited data sources, displayed paragraph by paragraph for transparency..
* **Video support as Data source:** You can now upload videos as data sources. Videos from your connected sources are also transcribed, so you can search their content.

#### **General Improvements**

* **Better Jira and Confluence sync:** Large Jira projects now sync completely, and all Confluence spaces now load. You can also filter spaces by name.
* **Web UI updates:** We improved the conversation history in Ask Kodesage and made other small UI improvements.

#### **CLI Improvements**

* You can now paste text with Ctrl+V.
* The "insecure TLS" option is now saved in your profile.

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