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

# Kodesage Release Notes - 0.8.0

A reworked Concepts tab, native Atlassian agent tools, and multilingual agents.

### **10 April 2026**

#### **💬 Ask**

* The Concepts tab now defaults to the graph view, with a view switcher and polish.
* Fixed the concept graph failing to render when navigating to the tab.
* Chat state is cleaned up correctly on page refresh.

***

#### **📄 Docs Studio**

* Faster Docs Studio loading.
* Simplified delete dialogs for documents, documentation and templates.

***

#### **🎫 Ticket Analyse**

* Native Atlassian agent tools for Jira and Confluence.
* Fixed an empty list on the Issue Analysis page.
* Fixed timezone handling for Jira dates.
* Corrected ticket ID alignment in the tickets table.

***

#### **⚙️ Settings**

* An improved data source connection panel for ticketing systems.

***

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

* Multilingual built-in agents, with multilingual benchmarks.
* Security fixes from dependency and static analysis scanning.
* A dependency health banner surfacing degraded services.
* Fixed a false 'outdated references' warning during document generation.


---

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