metabase / metabase/metabase

AI data analysis / narrative insights inside Documents

Open
#76,156 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

.Auto triaged .Team/UXWest Organization/Documents Type:New Feature
Dominant language
Clojure
Stars
49.3k
Forks
6.8k
Avg merge
1d 13h
Merged PRs (30d)
653

Description

**What problem will this feature request solve?**
Insights that explain the charts and queries embedded in a Document have to be written entirely by hand. There's no way to have AI read the embedded data and produce a written analysis.

**Describe the solution you'd like.**
Have AI / Metabot read the charts, queries, and data included in a Document and generate insights, trends, highlights, and narrative explanations as written text — automatically, and ideally refreshable as the data changes.

**How does this feature request impact you?**
It would be additional value the customer wants to deliver to their clients on top of manually edited documents.

**Additional information**
- Related: [#76089](https://github.com/metabase/metabase/issues/76089) — *AI generated dashboard summaries* (open). Same idea applied to dashboards; AI-written summary of key insights, refreshable, includable in subscriptions.
- Related: [#16012](https://github.com/metabase/metabase/issues/16012) — *Using natural-language generation to add data stories to Metabase Dashboards* (open). NLG paragraphs tied to query values that describe the data.
- Related: [#74304](https://github.com/metabase/metabase/issues/74304) — *Create automated (non-dashboard) reports using Metabot/AI* (open).

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing how Documents currently contain charts, queries, and embedded data, then compare the related issues #76089, #16012, and #74304. Define the supported AI inputs, narrative output, and refresh behavior before identifying implementation entry points. Done means a scoped design and implementation that generates and refreshes written insights in Documents.

Written by the indexing model from the issue text.

Assessment

Tech stack
clojure
Domain
ai, data-visualization
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.