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

# Kodesage Release Notes - 0.9.5

This release adds personal Agent instructions and Microsoft Teams integration, improves Jira and Confluence connectors, and fixes large-file ingestion.

### **4 September 2026**

#### **New Features**

* Ability to give personal Agent instructions under the User Profile tab.
* Integrated Ask Kodesage sessions with Microsoft Teams.

#### **General Improvements**

* Restored the legacy Jira/Confluence connectors, so there is no longer any need to remove previous connections to add a new one.
* Changed the default Jira and Confluence sync cadence to 60 minutes, to avoid data overload when many connections are active.
* Retired the one-shot Ask Kodesage flow and Templates in Settings.
* Fixed large-file ingestion: the quadratic XML chunker that returned HTTP 500 errors on large files is now resolved.
* The agent now preserves user intent across compaction in long conversations.

####


---

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