> 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/february-2026.md).

# February 2026

## Euno Release Notes — February 2026

### New Features

[Domains](/setup-configuration/domains.md) — logically group resources in your data model based on EQL rules

[Google Workspace Integration](/sources/identity-and-organization/google-workspace-integration.md) — integrates with Google Workspace to observe users and groups from your identity and access management system

[Assistant Thinking Mode ](/ai.md)— Visible reasoning steps in the AI Assistant, with UI and detail improvements

***

### Integration Improvements

[Tableau](https://docs.euno.ai/sources/business-intelligence/tableau-integration)

* Tableau LUID now exposed in sidepane for easier cross-referencing
* Hidden resources now identified

[Looker](https://docs.euno.ai/sources/business-intelligence/looker-integration)

* LookML view `extends` field inheritance support

[BigQuery](https://docs.euno.ai/sources/data-warehouses/bigquery-integration)

* Column observation exclude patterns
* Consolidated zero-usage column observations

[Snowflake](https://docs.euno.ai/sources/data-warehouses/snowflake-integration)

* Column names now normalized (capitalized), including external refs in Tableau

[dbt](https://docs.euno.ai/sources/transformation-etl/dbt-core)

* Schema file path fix for monorepo packages in dbt descriptions

### AI Assistant

* Resources can now be attached to assistant chat
* [Impact Analysis](https://docs.euno.ai/using-euno/impact-analysis) supports unlimited hops
* [EQL](https://docs.euno.ai/using-euno/euno-query-language-eql): case-insensitive support via `i`-prefix literals and mixed `IN`; new `r` prefix for string literals

### UI & Platform

* [Active tags](https://docs.euno.ai/using-euno/metadata-activation/metadata-tags): default values for fixed tags; coalesce metadata tag support


---

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