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

# Kodesage Release Notes - 0.7.9

Better agentic diagrams, nested archive ingestion, and the groundwork for the CLI.

### **27 March 2026**

#### **💬 Ask**

* Improved quality of agentic diagram generation.
* Ingestion of nested application archives.

***

#### **📄 Docs Studio**

* A 'created by' column in the Docs Studio table.

***

#### **🎫 Ticket Analyse**

* SSL verification options for Confluence, Jira and Git connections.

***

#### **⚙️ Settings**

* Fixed a crash when downloading reports.
* Concept search no longer runs when codebases are excluded by data source filters.

***

#### **⌨️ CLI**

* A re-architected agentic conversation system with persistent storage, new agent types and unified toolkits — the foundation for the Kodesage CLI.

***

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

* Fixed context overflow during long conversations.
* Oracle schema configuration and query limits.
* A redesigned empty projects screen.
* New SQL schema parsing, and faster text, XML and chunk processing.
* Database engine tuning for concurrent access.


---

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