2.16.7
Dbt Foreign Key Recognition
Improvements
- Orion now recognizes foreign key relationships declared in your dbt project through relationships tests, using them to determine the correct join paths between tables.
Company
TeamNew updates and improvements to Orion.
2.16.7
2.16.3
Comprehensive behavioral analytics reports for your Looker models now automatically appear in your knowledge base under Internal and stay up to date after every nightly analysis.
These reports include executive summaries, dashboard analysis, user activity, field catalogs, data quality assessments, usage patterns, proactive intelligence, and user personas—giving you instant access to rich context about your data without manual compilation.
2.16.2
You can now connect a LookML repository to warehouse data sources such as Snowflake, BigQuery, or Postgres, not only to Looker connections. If your business logic lives in LookML but Orion queries your warehouse directly, that logic can now reach Orion without a Looker connection in between.
You can also copy an existing LookML repository configuration from a Looker connection to a warehouse data source instead of entering the repository and token a second time.
2.15.10
You can now add catalog metrics to a project directly from the project's own settings. Open Project Settings, go to the Knowledge Base tab, and the Metrics Catalog appears at the top of the list alongside your wiki pages. Select metrics and folders with checkboxes instead of managing them one at a time from the Knowledge Base interface.
When working with LookML integrations, you can now browse the exact files Orion pulled from your GitHub repository in the Augmentation tab, so you know precisely what Orion is reading. When a sync fails, Orion now tells you what went wrong and which specific setting to change, instead of reporting a generic error message.
2.15.5
Orion can now complete your entire metrics catalog workflow without handoff. It creates the folder structure, files metrics into the right folders as it promotes them, reorganizes the catalog for clarity, and writes knowledge base pages that explain how your metrics fit together. What previously required you to finish the organization and documentation by hand is now fully automated.
2.15.2

You can now record who is responsible for each metric in your Metrics Catalog as people or teams. When you're about to edit a shared metric, Orion shows you every published report that depends on it, so definition changes become conversations with stakeholders instead of surprises.
2.14.2

You can now connect Orion to MotherDuck and analyze your data the same way you would with any other warehouse.
Add your MotherDuck database using a token, and Orion automatically reads your schema, answers questions about your data in chat, and pulls tables into your notebook for analysis. Read Scaling tokens are supported and recommended, and your table and column comments are automatically used by Orion to understand which tables are relevant to your questions.
2.13.20
The Schema tab now displays your data source's table relationships as an interactive diagram, letting you see the shape of your schema at a glance. Relationship lines are color-coded to show their origin, and dashed lines indicate relationships your warehouse declares but does not enforce.
Orion now understands how your tables relate to each other by reading the foreign keys your warehouse declares and any dbt relationship tests you have written.
When Orion writes queries, it uses these verified paths. The Schema tab shows you which joins are verified and which are not, and you can correct relationships Orion misidentified or add ones your warehouse never declared.
2.13.18
2.13.17
Dashboard headers can now display a count of unique values—such as unique sessions, unique customers, or unique users—instead of only showing a row count. This gives you more flexibility in summarizing what your data represents at a glance.
Orion can now raise questions or suggest analyses directly in chat when it needs your input on something. These annotation cards appear alongside the reply and persist in the conversation, so you can see them again when you return to the chat.
2.13.13
2.13.6
Orion now suggests analyses worth running directly in your conversations, surfacing opportunities at the moment you're already discussing the relevant topic.
When you click through on a recommendation, a short intake conversation opens to clarify exactly what you want—whether that's a slide deck, dashboard, metrics report, or something else—before any analysis work begins. This ensures the final result matches what you asked for rather than a generic guess.
2.11.13
You can now edit a data source's dbt configuration after it is created. Update dbt Cloud, GitHub, or uploaded-manifest settings and rotate dbt credentials directly from the data source's Connection tab, without deleting and recreating the connection.
2.11.6
Data source admins can now control, per data source, whether newly discovered tables and explores are enabled or disabled by default. This gives you fine-grained control over which new schema elements appear in your workspace without requiring manual review of every discovery.
2.11.0
Open the Workspace panel (or click "Sources for this reply" under any answer) to see exactly which knowledge base pages, memory, metrics, and project settings Orion used to reach that result.
Each source is linked directly so you can open a Knowledge Base page to verify or edit it. This makes it much easier to understand and trust how Orion reached a conclusion.
2.10.9
2.10.6
You can now rename your chats from the history sidebar to keep past conversations organized and easy to find. Give your conversations meaningful names that reflect their purpose, making it simple to locate and revisit important analyses.
2.10.0
You can now connect Amazon Athena as a data source. Orion introspects your AWS Glue catalog, learns which tables and columns your team queries most, and runs analyses directly against Athena.
2.9.1
You can now connect your own Google account to a BigQuery data source that uses per-user access, so Orion runs your queries under your own BigQuery permissions.
Connect or disconnect any time from the data source's Connection tab. Admins can configure the OAuth credentials directly in the datasource settings instead of coordinating separately.
When you state a durable company fact or a personal preference, Orion now offers to save it to the right place: facts to the knowledge-base wiki, preferences to your personal memory.
It only offers to save things you actually said, won't re-add what's already in your knowledge base, and no longer files company definitions away as personal memories.
2.8.27
2.8.26
2.8.18

You can now control what Orion draws on for any conversation by toggling memory, knowledge base, and past chats on or off. Use the new Context control in the chat box to customize which information sources are active before you send your first message. This lets you have focused conversations that ignore your history, or leverage your full context when you need it.
2.8.14
The weekly digest email now features a cleaner, more scannable design with a clear headline, key metrics at a glance, and concise per-project findings, each linking directly to its source for quick exploration.
• Looker explores now surface the fields people actually use more reliably, leading to faster and more relevant query construction
• Workflow run deletion is now available throughout the product for easier history management
2.8.11

Knowledge Base reviewers now see proposed changes rendered directly in the markdown, similar to suggestion mode in Google Docs. This makes it dramatically easier to understand exactly what's changing and why. A visual minimap helps you navigate longer documents, while clear indicators show you which edits you've already reviewed.
Submitters can preview their pending changes in the same beautiful rendered format before submission, ensuring their contributions look exactly as intended.
• Backend infrastructure improvements enabling enhanced workflow context tracking across artifact pages
2.8.5
Orion now understands how your Looker fields are actually used—query frequency, common filters, co-queried fields, and importance—even when you don't have a connected LookML repo or have AI descriptions disabled. This means your analysis reflects real usage patterns in more cases, and the system's understanding stays fresh after each nightly refresh.
Orion now understands who uses each Looker explore and what business questions their query patterns answer. This lets the system frame analysis around the people and decisions an explore actually serves and proactively suggest the next useful question based on real usage behavior.