> For the complete documentation index, see [llms.txt](https://docs.euno.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.euno.ai/support-resources/release-note/september-2026.md).

# September 2026

### New Features <a href="#toc_1" id="toc_1"></a>

**Context Calibration** — run evaluations of your AI context to continuously maintain trust in AI *(early access)*

**Catalog Write Tools** — create and update Glossary terms, AI Metadata Tags, and Workflows directly from the Euno Assistant and MCP

**Customer Skills in the Euno Assistant** — skills you author with the Skills Generator are now available to the Assistant

### Integration Improvements <a href="#toc_2" id="toc_2"></a>

#### SQL Server <a href="#toc_6" id="toc_6"></a>

* Usage metrics over 14, 30, and 60-day windows, including partial counts while a window is still filling

#### BigQuery <a href="#toc_8" id="toc_8"></a>

* Table labels ingested as metadata

#### Looker <a href="#toc_10" id="toc_10"></a>

* dbt `config.meta` honored for Euno LookML sync tags, making the sync dbt Fusion–ready
* dbt tag lineage now gated on an authoritative dbt source, with relationships cleared when a tag or its target goes away

### UI & Platform <a href="#toc_13" id="toc_13"></a>

* A new search and filtering user interface
* Various bug fixes and performance improvements across integrations


---

# 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.euno.ai/support-resources/release-note/september-2026.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.