# Ask AI in the Filter Search Bar

Nikita Kabardin

Describe the filters you want in plain language and the search bar drafts them as editable query pills. Opt-in on Langfuse Cloud, powered by AWS Bedrock with zero data retention.

The [Filter Search Bar](/content/changelog/2026-06-19-filter-search-bar/index.html) is fast once you know your field names. On a project you have not touched in a while, you often don't. What was the metadata key for the routing queue again? Is it `name` or `traceName`? **Ask AI** is for exactly that moment: click it and describe what you are after in plain language. Type something like:

> enterprise plan customers stuck in the membership-support queue

and it drafts a set of editable `metadata.*` filter pills, dropped into the bar for you to adjust or throw away.

Ask AI is in beta and available on **Langfuse Cloud only**. It is **off by** **default**; an organization owner or admin turns it on in **Organization** **Settings → General → AI Features**. It runs on models hosted on AWS Bedrock with zero data retention. See [data privacy and security](/content/security/ai-features/index.html).

## [How it stays grounded in your data](/content/changelog/2026-06-26-ask-ai-filter-search-bar#how-it-stays-grounded-in-your-data/index.html)

The thing we cared about most is that Ask AI is **project-aware**. Rather than guessing field names in the abstract, the request carries a small, client-side snapshot of your project: the columns and values already loaded in the table, the metadata keys it has seen, and how many rows currently match. That gives it a real shot at your actual schema instead of a plausible-looking guess:

- "routing queue should be membership-support" maps to `metadata.routing.queue:*membership-support*`, when that key exists in your data
- "support chat sessions" maps to `traceName:SupportChatSession`, the name that is actually there

It is still a language model, so treat what comes back as a starting point rather than gospel. Two things keep the blast radius small: it can only emit filters the bar's grammar supports (column filters, metadata, numeric and categorical scores, input and output content search, `has:` null checks, tag any/all/none, negation), and any column it tries to invent is dropped before the query runs. Whatever lands is editable, so a wrong guess is one pill away from fixed.

## [How it works](/content/changelog/2026-06-26-ask-ai-filter-search-bar#how-it-works/index.html)

Ask AI is a button next to the bar, always available. Press it, type your request, hit Enter. With an empty bar it drafts a query from scratch; with filters already in place it **refines** them, adding, changing, or removing as you ask ("also only errors", "drop the latency one"). Everything applies through the same path the sidebar uses, so it is lossless and the browser back button undoes it.

## [Feedback](/content/changelog/2026-06-26-ask-ai-filter-search-bar#feedback/index.html)

This is an early version of an idea we like: natural-language filtering that actually understands your project's data. It is the [magic filter](/content/changelog/2025-09-30-natural-language-filters/index.html) concept, rebuilt to live inside the search bar, and it will not get everything right yet. If it misreads what you meant or reaches for a field that is not there, we want to see it. Tell us what you typed and what you expected in the [feedback thread](https://github.com/orgs/langfuse/discussions/14595). That is the fastest way to make the next version better.