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

# What's new in 0.8.x

Agentic mode graduates out of beta and reaches Issue Analysis and Docs Studio, plus file uploads, Slack, and much broader database support.

### **April – June 2026**

#### **💬 Ask**

* Agentic mode left beta and became the default.
* Image and file uploads in chat, by paste, drag-and-drop or picker.
* Researcher and explorer agents, with persisted subagents.
* Ask Kodesage in Slack, with pluggable channel adapters.
* Ask Kodesage agentic mode exposed over MCP.

***

#### **📄 Docs Studio**

* Agentic mode for Docs Studio.
* Camunda BPMN workflow analysis, including tagging a diagram already in the knowledge base.
* DOCX export fixes and better list, heading and table rendering.

***

#### **🎫 Ticket Analyse**

* Agentic mode in Issue Analysis.
* Ticket attachments end-to-end, including images in the issue analyser.
* Issue Analysis results are now visible to all users.

***

#### **⚙️ Settings**

* Access Tokens redesigned to match the Data Sources experience.
* Clearer project create and delete permissions.
* PL/SQL navigation with package drill-down, member search and call graphs.

***

#### **⌨️ CLI**

* First native Kodesage CLI binaries published.
* Token-authenticated access, image attachments and a theme-aware interface.

***

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

* PostgreSQL, Db2 and Informix added to database schema import.
* Unified schema import and live connections under Data Sources.
* Faster, more reliable ingestion and document export.


---

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