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

# Kodesage Release Notes - 0.9.1

A deterministic concept graph, CLI theming and sandboxing, and on-premise database tuning.

### **6 July 2026**

#### **💬 Ask**

* The concept graph is now deterministic, built from parsed code and database schema.
* An additional language-quality pass improves localized answers.

***

#### **📄 Docs Studio**

* Agentic generation parity in the new interface.

***

#### **🎫 Ticket Analyse**

* The whole Issue Tracker row is now clickable.

***

#### **⚙️ Settings**

* Restored the Invite Member button under Settings → Members.
* The concepts tooltip now shows when concepts were last created.
* Removed the obsolete editor configuration download.

***

#### **⌨️ CLI**

* Linux arm64 builds.
* Automatic theme detection with a theme picker, persistence and live switching.
* The install page is now fully copy-paste.
* Fullscreen markdown wraps to the viewport width.
* New sandbox subsystem providing native operating-system isolation.

***

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

* Database tuning for 32 GB on-premise hosts, and bounded connection lifetimes.
* Project lists are scoped to per-project view permissions.
* A unified connection model for Atlassian products, with credential separation.
* Built-in product self-knowledge, so Kodesage can answer questions about itself.
* Restored the install-as-app button.
* Clearer data source sync states for uploaded and knowledge-base-processed documents.


---

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