AI Agents
Recent items mentioning AI Agents across the Databricks ecosystem — releases, news, videos, and community Q&A. Updated hourly.
What is AI Agents?
On Databricks, an AI agent is an LLM application that can reason over your company's data and call tools, built and run inside the same platform that holds the data. The headline product is Agent Bricks, a set of managed agent builders: Knowledge Assistant turns your documents into a domain-specific chatbot through a point-and-click interface, and Supervisor Agent orchestrates other components, including Genie Agents, agent endpoints, Unity Catalog functions, MCP servers, and custom agents.
The hard part of shipping an agent is rarely the first prototype. It's proving answer quality, tracing what the agent actually did, and governing who can call it. Databricks folds those steps into the platform: agents can be registered in Unity Catalog, MLflow handles tracing and evaluation, and you aren't locked into one framework, since code-first agents can be written in Python with any authoring library, including LangGraph, LangChain, OpenAI, and LlamaIndex.
Maturity varies by piece. Knowledge Assistant has been GA since January 2026, while Agent services, the part that registers agents in Unity Catalog, is still in beta. The overall direction is toward agents you configure and the platform optimizes, instead of pipelines you tune by hand.
What is Agent Bricks?
Agent Bricks is the managed agent-builder layer on Databricks. Its current offerings include Knowledge Assistant, which builds and optimizes a domain-specific chatbot over your documents through a configuration interface, and Supervisor Agent, which orchestrates other agents such as Genie Agents, agent endpoints, Unity Catalog functions, MCP servers, and custom agents.
Can I write my own agents in code instead of using Agent Bricks?
Yes. Databricks supports agents authored in Python with any library, including LangGraph, LangChain, OpenAI, and LlamaIndex. You still get the platform services around them, such as MLflow Tracing for end-to-end observability and agent evaluation, regardless of which framework you pick.
What's the difference between Agent Bricks and Genie Agents?
Genie Agents answer natural-language questions about structured data by generating SQL over curated Unity Catalog datasets. Agent Bricks builds task-focused agents, like document Q&A with Knowledge Assistant or multi-agent orchestration with Supervisor Agent. The two connect: Supervisor Agent can call Genie Agents as one of the agent types it coordinates.
Is Agent Bricks generally available?
Partly. Knowledge Assistant reached general availability on January 27, 2026. Other pieces, such as Agent services for registering agents in Unity Catalog, remain in beta, so check the docs page for each component's current status before you build on it.
Sources: Agent Bricks (Databricks docs) · Build gen AI apps and agents (Databricks docs) · Knowledge Assistant GA announcement (Databricks blog)
Unity Gateway has expanded its agent governance capabilities, introducing Insights to identify cost inefficiencies like failing MCP tools and redundant tasks 2 as organizations like Block adopt it to centrally route multi-agent workflows 10. At the infrastructure layer, Lakebase provides database branching to safely test AI agents against operational data 3, while Lakehouse//RT absorbs agent-driven query spikes at 6x to 10x lower infrastructure costs 9.
Generated daily from the 10 most recent items mentioning AI Agents. Click any [N] to jump to the source.
We wrote about this
- Genie One MCP server: setup and migrationHow to connect Claude Code, Claude, Cursor and ChatGPT to the GA Genie One MCP server, and what to change before the Beta endpoint reaches end of life on 30 November 2026.14 min read
- Databricks serverless micro apps: what's liveDatabricks serverless micro apps: since September 23, 2026, Genie App Builder apps scale to zero in Beta. Code-first apps can't. The name hasn't shipped.11 min read
- Databricks certification cost, the full list, and where to start16 live credentials, one $200 exam fee, a 14-day retake wait, two-year validity, and which Databricks certification to take first, verified on databricks.com.13 min read
- Databricks put agent skills in Unity Catalog, and gave them two namesA skill is now a catalog object you grant like a table. What the Beta does, the download-versus-live decision it forces, and why the docs cannot decide what to call it.6 min read
ReleasesAutomate Data Warehouse Migration with AI - Genie Migrate for Lakehouse Intro
Genie Migrate for Lakehouse is an AI-powered migration solution that automates the movement of data and code from legacy data warehouses to the Databricks Lakehouse. It converts SQL from seven major data warehouses into open ANSI SQL and PySpark, reducing delivery timelines and ensuring high conversion accuracy.
TutorialsHow to Reduce AI Agent Costs | Unity Gateway Insights
Unity Gateway Insights helps organizations track AI agent usage and costs. The tool identifies common financial inefficiencies such as failing MCP tools, frontier models performing routine tasks, and repeated work.
Branch, sync, serve: What our Lakebase Hackathon taught us about building on Lakebase
Operational Postgres is becoming an integrated part of the lakehouse rather than a standalone system running alongside it. Customer hackathon projects demonstrate this shift by using Databricks Lakebase to safely test applications and AI agents via database branching, while syncing directly with the lakehouse to serve real-time data and ML features.
Azure Databricks sessions at Microsoft Ignite 2026
Azure Databricks is presenting eleven sessions at Microsoft Ignite 2026 focused on governed AI, AI agents, model fine-tuning, and Genie integrations across Microsoft Teams and Microsoft Copilot Cowork. Attendees can connect with the team November 17–20 in San Francisco at Booth #5271R in The Hub, the Ask the Experts kiosk, or The Social @ Canopy Hotel.
The new Azure Databricks on Azure Government is now in Beta
Azure Databricks on Azure Government is now in Beta, bringing commercial platform parity with Unity Catalog governance, serverless Databricks SQL analytics, and U.S.-only data residency. Upcoming releases on the path to General Availability will add AI capabilities like Genie, Agent Bricks, and Model Serving, with FedRAMP Class D and IL5 authorization expected by early 2027.
AI Agents & Precedent: Three Gates Before Reusing a Decision
submitted by /u/Berserk_l_ [link] [comments]
Databricks is a Leader and positioned highest in execution in the 2026 Gartner® Magic Quadrant™ for Data Lakehouse Platforms
Databricks has been named a Leader positioned highest in execution in the 2026 Gartner Magic Quadrant for Data Lakehouse Platforms and the sole Visionary for Cloud Operational Database Management Systems. Complementing this recognition, Databricks Lakebase Postgres delivers an open-format transactional database on the lake to serve as the system of record for agentic workloads, modern applications, and traditional systems.
Migrate Effortlessly to the Databricks Lakehouse with Genie Migrate, now Generally Available
Companies are racing to build AI agents and applications. Every one of these use...
Lakehouse//RT: Scale real-time analytics, not your bill
Lakehouse//RT is built to absorb surging real-time query volumes driven by AI agents without a proportional increase in costs. Customers choosing it over separate real-time serving layers report 6x to 10x lower infrastructure costs.
How Block powers collaborative AI agents with Buzz and Unity Gateway
Block deployed Databricks Unity Gateway as the centralized model access layer for Buzz, its open source collaboration workspace where employees and AI agents work together. Through a single integration, users can assign frontier and open-weight models to specialized agents and coding harnesses, enabling multi-agent workflows that optimize performance and cost.
NewsS2 Ep4: All About the Rise of Genie | Falek Miah
Genie is a natural language interface that has evolved into a comprehensive suite of AI tools including Genie Agents, Genie Code, Genie App Builder, and Genie Ontology. These tools integrate with platforms like Lakebase to streamline data access, automate app building, and improve data governance.
The new Genie: autonomous AI for complex enterprise work
Genie is now an autonomous AI coworker capable of executing long-running enterprise tasks within your defined guardrails. Supported by Genie Ontology and Genie Search across the lakehouse and business systems, the updated platform relies on Unity Gateway so admins can govern tool access, trace actions, and set spending limits.
Bring your business context to ChatGPT, Claude, Microsoft Copilot Cowork and Grok Bot
Databricks Genie now integrates natively with ChatGPT, Claude, Microsoft Copilot Cowork, and Grok Bot, alongside an MCP server connection for other AI agents. These external tools can draw on the Genie Ontology to run SQL over authorized data and return cited business answers directly into drafting, planning, or messaging workflows.
Announcing GA of Genie Ontology
Genie Ontology is now Generally Available, delivering an agentic ontology that unifies business context across agents alongside the GA of Unity Catalog Domains and Pages. The release introduces Genie Search and Ontology Manager for curation, extending learned context to BI tools and directories while achieving a 91% pass rate on enterprise benchmark tasks using less than half the tokens.
Making the economic case for warehouse-first AI context
A warehouse-first approach to AI context dramatically reduces token costs, establishing a clear economic case for AI agents. This strategy tackles immediate monthly token bills while long-term agent investments take years to pay off.
I tried to break my own open-source safety check for agent writes on Databricks: 5 SQL attacks, a 2M-row Delta table, 2 real bugs found
A pipeline can run green and still ship wrong data. With AI agents writing more of our code, I wanted a check before changes reach production. https://preview.redd.it/3w9kidmk8w0i1.png?width=1280&format=png&auto=webp&s=99f764348291e6a0c2a31dc1cb6d2c7028717153 bricksentry (free, open source) tells you three things before a change ships: • Who depends on this table (Unity Catalog lineage) • What the change does to the data (rows added, removed, duplicated, totals moved) • How to undo it (the exact Delta restore point) Created by Author. Created by Author. Then it says OK, warn, needs a human, or block. I tried to break it on a 2M-row table. Production was never touched, and I fixed three bugs along the way. Created by Author. Website and docs: bricksentry.org Code (Apache-2.0): github.com/bricksentry/bricksentry Package: pypi.org/project/bricksentry If you’re running agents against Databricks today, I’d like to hear how you handle change-safety, and what breaks when you run bricksentry on your own tables. submitted by /u/According-Future5536 [link] [comments]
A letter from our founders
The age of intelligence will be driven by agents, open data infrastructure, and the humans building the agentic future. Databricks founders share their perspective on these core themes and their vision for navigating this next era.
NewsHow Databricks and UiPath Turn AI Insights into Action
Databricks acts as a data foundation where organizations can bring their data and automation together, utilizing agentic bricks as an agent and genie to build agent bricks agent. UiPath brings that information to the business process layer, allowing users to build agents and robots for deterministic actions and orchestrate workflows with Maestro for end-to-end processes.
Why use data bricks AI to build agents?
OK y’all, help me understand why it would be beneficial for me to use databricks AI (genie) if it will only integrate with databricks stack? I would much rather use an agentic soliton that will not lock me into a vendor’s tech stack. I’m trying to make the case that using another third party agentic platform that has native databricks integration would be much better than getting locked into databricks. Ideally since using a third party agentic solution to build agents would allow for easier integration with other systems that are outside databricks. Similar to how I wouldn’t use agentforce in salesforce, I wouldn’t use genie in databricks. What have been your experience with agents/AI solutions with genie? submitted by /u/vandev_ [link] [comments]
TutorialsMulti-Part Series: App Developer - Introduction to Databricks Development
This video introduces the Databricks App Developer skill builder series, which covers application architecture, identity and governance, data and compute choices, AI integration, deployment, and operations through a series of hands-on labs. It highlights Databricks Apps, AppKit, Lakebase, and Unity Gateway as key tools for building and managing secure, scalable data and AI applications.
NewsDatabricks MemCurrent, Genie Agents, Azure MPC Server & Feature Views | AI Newsround - October 2026
Databricks announced the beta release of MemCurrent for persistent agent memory, along with Genie Flash mode for faster agent responses and general availability of Feature Views. Azure MCP Server 3.0 reached general availability, and several new AI models including Anthropic Claude Haiku 5.5 and Microsoft Decision 1 were introduced.
NewsDataBuddy By Tencent Cloud
Tencent Cloud DataBuddy is an agentic platform designed to automate and manage data engineering, governance, and analysis workflows within e-commerce operations. The platform enables users to execute complex tasks from data ingestion to trend analysis while maintaining human oversight at critical approval checkpoints.
NewsLakebase Search Explained
Lakebase search introduces two new Postgres extensions, lakebase_text and lakebase_vector, to optimize text and vector search. These extensions allow developers to run search operations directly alongside operational data in a single SQL query.
We pointed an AI agent at 146M NYC taxi rows and asked it to build a Data Vault mart. Here's what broke.
A while ago I said I'd run our agent on dirty data, not clean TPC-H. Here's the first run. Setup. NYC yellow taxi 2015 from databricks-datasets: 146,112,990 rows in one Delta table, CDF on. Serverless jobs, a trial workspace. The request in plain English: "Monthly revenue, number of trips and average tip by payment type and passenger count". The agent profiles the source (structure and stats only, it never sees values), proposes hub/satellite/mart, asks questions, a human approves, then it generates and runs the jobs. What the agent got right on its own: - total_amount is broken in this dataset (≈0.3 in almost every row, 31 distinct values across 146M). The agent flagged it and proposed revenue = fare + extras + tax + tip + tolls. - There is no natural trip key. It picked vendor + pickup/dropoff time + coordinates. What broke (our bugs, not the data's): The key check pulled 200k distinct key values into the app and hit Databricks' 25 MB inline result limit. Now counted in the warehouse. A 7-column composite key of mixed types (string, timestamps, doubles) broke the hash on serverless: ANSI mode coerced the array to TIMESTAMP and died on vendor_id = '1'. The rejected-rows path had never actually run on Databricks. The worst one: that "unique" key wasn't. 51,306 keys repeat, mostly a charge and its reversal (fare 3.0 and -3.0) at the same second. SCD2 got both versions in one batch, closed both, and 51,280 trips silently vanished from the mart. Uniqueness had only been checked on a 200k-row sample. The fix: uniqueness is now checked on the whole table (6 s on 146M). If keys repeat, the agent asks you what to do instead of deciding. At load, one row per key is kept by a deterministic rule and the rest go to skipped rows with a reason, not into the void. Result after the fix: - Mart = vault in all 435 groups, trips and revenue to the cent. 146,061,125 trips = the number of unique keys in the source. - Full build 18 min. With CDF, an empty build takes 2.8 min. - Added 100k new trips plus updates and deletes through CDF: 4.6–5.2 min per build, 2015 numbers didn't move by a cent. - A second mart on the same data (daily trips by vendor) reused the vault and built in 2.8 min with no reload. Same total. Still open: - Keeping one row out of a charge/reversal pair is a business call; the right answer for taxi is probably a multi-active satellite. - On CDF, the same key arriving in different source versions isn't flagged as a duplicate. - Key format chaos (40 vs 40.0, spaces, case) is next on the list. Happy to share the reconciliation queries if anyone wants to poke holes in this. submitted by /u/No_Advertising2536 [link] [comments]
TutorialsHow To Detect Telecom Fraud in Real Time with an AI Fraud Analyst Coworker | Databricks Demo
The video demonstrates a real-time telecom fraud detection platform built on Databricks that unifies data infrastructure, governance, and AI agents. It showcases executive, management, and analyst views to monitor fraud metrics, forecast case volume, and investigate high-risk transactions.
NewsBuilding on Lakebase | Episode 3: Branch, Test, and Ship: Release Changes Safely using Branching
Lakebase branching allows developers to test database schema and code changes on isolated, production-like data branches without affecting production. The demonstration shows how automated GitHub Actions workflow uses pull requests to create branches, run migrations and tests, review schema diffs, and merge changes.
DataRanger: High-Performance Distributed Data Framework for Scalable Streaming and Agentic Workloads
 **Author:** Akshay Sharma (Lead Member of Technical Staff, Salesforce | IEEE Senior Member) **Repository:** [` https://github.com/akshaysharma1088/dataranger\`\](https://github.com/akshaysharma1088/dataranger) # Abstract & Core Motivation Modern enterprise data architectures and autonomous AI pipelines frequently hit severe scaling, latency, and cost bottlenecks when processing high-concurrency, real-time data streams. Existing frameworks often force engineering teams to choose between compute efficiency and operational complexity. **DataRanger** is a novel, open-source distributed systems framework engineered to streamline data management, execution, and state handling across complex production environments. # Key Architectural Features * **Optimized Distributed Streaming:** Bridges traditional medallion architecture layers with high-throughput stream processing to eliminate unnecessary compute overhead. * **Agentic Context & Data Interoperability:** Designed to support modern agentic runtimes by efficiently serving low-latency, context-rich data structures without scaling friction. * **Reproducible Systems Evaluation:** Built and benchmarked for rigorous systems performance validation, targeting top-tier database venue submission (PVLDB). # Access & Archival Reference * **Source Code:** Available on GitHub under `akshaysharma1088/dataranger`. * **Archival & DOI:** Permanent release records and pre-prints are archived via **Zenodo** to ensure citable, open-access distribution for the systems engineering community. Article DOI - [ https://doi.org/10.5281/zenodo.23852354\](https://doi.org/10.5281/zenodo.23852354) submitted by /u/GuidanceBrief612 [link] [comments]
Does agentic analytics need a separate semantic layer if the data is already well modeled?
submitted by /u/Apprehensive_Tie2494 [link] [comments]
Wealth Management Client Onboarding Needs More Than AI
Task-level AI speeds up document processing and KYC screening, but wealth management client onboarding still stalls when evidence, case state, and decisions are fragmented across systems. The fix is governed case context, a shared, versioned view of each case's evidence, exceptions, and decision history, which supervised AI agents on the Databricks Data + AI Platform use with human reviewers to coordinate the full journey with traceability, and whose impact you can measure through cycle time, manual touches, and approval-to-funding time.
NewsPractical Use Cases for Jev | System One Models - Part Three
Jev utilizes structured, non-generative AI systems for energy billing and customer service workflows with built-in safety controls. It also automatically tags and extracts sections from complex documents like insurance quotes and claims, significantly reducing token usage and manual review effort.
unit tests
Hi, we use Databricks, this is not 100% Databricks related, but i wonder, how do you do your unit testing with todays agentic engineering, currently we don't have any skill or rule, or hook that helps AI to write unit tests, so it just writes a lot of bloat unit tests which we do not trust, it has more than 1000 unit tests on 30k lines of code. I see a lot of mentioning mutation testing, did not check that out yet, but in general how do you approach this? Because unit tests should be a useful guardrail for agentic coding. submitted by /u/ptab0211 [link] [comments]
AI Agents Should Not Start Every Conversation From Zero
Agentic code converter is GA for SQL
Migration · GA Agentic code converter is GA for SQL Genie Code converts T-SQL, Snowflake, Redshift, Oracle, BigQuery, and Teradata SQL to Databricks SQL. It validates each file and fixes errors before writing to a workspace folder. Work in a migration project, or run /migrate in a Genie Code chat for one file or folder. Afterward, keep chatting to clear action items. The Notebooks target is not part of this GA. https://preview.redd.it/u5m0quj71fyh1.png?width=1808&format=png&auto=webp&s=1a5f16a1d66fa88e9bc171e10efb16c33dadfa2b Looking to migrate workloads but don't have the labor to do so. This is going to continue to expand its SQL dialect but taking an agentic approach to migrations really speeds up migrations and cuts down on time/money from labor submitted by /u/Wise_Ear_4064 [link] [comments]
TutorialsLangGraph Tutorial - State, Nodes and Edges | Chapter 11
LangGraph is introduced as a more controllable alternative to LangChain for building agentic workflows, offering fine-grained control over execution flows. The video demonstrates how to build a basic workflow using state, nodes, and edges in LangGraph.
Why an AI agent's revenue query was $3.5 million wrong, and how AWS fixed it with dbt Semantic Layer
AWS shows how a plausible-looking AI agent revenue query came out $3.5 million wrong, and how grounding the agent in the dbt Semantic Layer prevents that kind of error. The post argues that supplying business context, such as governed metric definitions, is what keeps AI-generated numbers trustworthy.
How Checkr cut an hours-long metrics investigation to minutes by engineering AI context on dbt and Omni
Checkr gave its AI agent a structured context layer built on dbt and Omni, shrinking a support-metric investigation from hours to minutes. The post walks through how engineering that context, rather than relying on the agent alone, made the analysis faster.
How LangChain grew self-serve analytics questions 40x by giving its AI agent layered context
LangChain gave its Hex analytics agent layered context, and self-serve data questions grew 40x, going from occasional to routine. The post walks through how that context-layering approach changed how teams use the agent for everyday analytics.
Ship AI agents like tables: dbt materializations for Snowflake CoWork
Under Armour turned Snowflake AI agents into dbt models using custom materializations, so each agent goes through the same code review and CI process as every table. The post walks through this approach to shipping agents like data assets rather than one-off deployments.
Show HN: 10x faster, 3x cheaper ETL
For the past few months our team has been working on an agentic framework that takes large, expensive SQL workloads and compiles them to Rust, backed by a formal proof of correctness. This is the sort of work I used to do by hand as a systems performance engineer, but now it happens in hours instead of months. We first redid our internal pipelines with this technique and they're now 10x faster and 3x cheaper. Next, we went live with our Snowflake and Databricks SQL customers. They're seeing similar results with critical production workloads that originally cost 6-7 figures per year. We'll be publishing benchmarks and code samples over the coming weeks; for now, you can read a bit more (and watch our anime launch trailer) on the site. Happy to answer questions about how it all works. --- top comments --- [gtirloni] Why was SQL slow? Where did processing shift to?
With great context comes great autonomy
Fivetran Context Layer writes what it learns from knowledge, operational, and analytics sources (like Notion, Salesforce, Postgres, and dbt) into the warehouse as open Agents Schema tables that any AI client can query over MCP, including a glossary and a concept table for company-specific shorthand. The dbt Summit 2026 session argues that a trustworthy agent depends on the context it has before it acts, and a new traces feature shows where an agent's confidence was low or context was missing so analytics teams can correct it.
Why dbt Labs thinks AI agents will finally make the semantic layer stick
dbt Labs' Zach Mandell argues that a second wave of the semantic layer, driven by AI agents, can succeed where the metrics-as-code first wave stalled, since agents multiply the value on offer while per-step errors across multi-step queries make governed, deterministic context a requirement for trust. He outlines four requirements: a native "semantic SQL" interface for BI tools, semantics pushed upstream into transformations, a semantic layer serving as the spine of a broader context layer, and scoped access with observability.
Do any other teams build web apps for fully flexible analytics/reporting?
Databricks dashboards are extremely limiting in their flexibility/capabilities (and I don't see that changing as they pursue everything AI/Agentic) and tools like Power BI have shitty CI/CD processes and still have their visualization limitations. Has anyone moved reporting/analytics to React/App Kit applications on Databricks for greater flexibility and ease of CI/CD? submitted by /u/TheOnlinePolak [link] [comments]
Unify your productivity and AI data with Lakeflow Connect
Lakeflow Connect now offers native, fully managed connectors for Atlassian (Jira, Confluence), Microsoft SharePoint, Google Workspace (Drive, Outlook, Gmail), GitHub, and AI providers like OpenAI and Anthropic, with unified governance and no infrastructure to manage. Because both structured and unstructured data land directly in Unity Catalog, teams can power enterprise knowledge bases, AI agents, and developer productivity dashboards without building custom API integrations or pipelines.
What Okta learned governing context for AI agents at scale
Okta moved its AI agent context out of the Snowflake UI and into dbt, using a three-layer framework of agent metadata in model YAML, markdown context docs, and semantic views in dbt's semantic layer spec, all shipped through normal pull requests. The context syncs into Agents Schema, so Claude (over MCP) and Snowflake Cortex read the same governed rules, and an analytics engineer fixes a wrong answer by merging one change that every agent inherits.
Inside dbt Wizard, the AI agent built to show its work
dbt Wizard, an AI agent for dbt work, validates its own output before any code reaches production. The post features its designer and engineering lead explaining how the agent is built to show its work along the way.
TutorialsLakebase Search: Build AI Retrieval for Agents with Lakebase Postgres
Lakebase Postgres introduces lakebase vector and lakebase text extensions to support hybrid search for AI agents. It leverages the Databricks Lakehouse architecture to synchronize and index data for efficient vector and full text search without requiring external databases.
TutorialsGoverning AI Agents with Unity Catalog and Unity Gateway on Databricks | Unity Catalog Demo
The video demonstrates how to govern AI agents using Unity Catalog and Unity Gateway on Databricks. It shows setting up access policies, user defined functions, and role filters to control data and model interactions.
How Ramp's internal AI agents crossed a million sessions
Ramp built its internal AI agents, sandboxes, and dashboards by treating internal AI as an analytics engineering problem, and the system has now passed a million sessions. This post walks through that approach so Databricks practitioners can see how the same discipline applies to running agents at scale inside their own organizations.
From prompt to PR: how Careem’s AI writes and validates dbt models before a human ever sees them
Careem's data platform team built a four-pillar dbt agent (context layer, spec locking, golden vs. transient layers, sandboxed guardrails) that compiles, tests, and materializes each change, self-correcting until the run succeeds before a human reviews the pull request. About 90% of new models now come from this framework, cutting metric delivery from two to three weeks to hours with no sev0 or sev1 incidents since launch.
How to solve dashboard debugging in six minutes with an MCP-connected AI agent
An MCP-connected AI agent used dbt lineage from inside the BI layer to resolve three dashboard data mysteries in about six minutes. The post walks through how that lineage access shortens dashboard debugging to roughly the length of a coffee break.
How a data scientist at Kilo built the business context layer his AI agents were missing
A data scientist at Kilo built an AI context layer that captures organizational knowledge a dbt project alone can't hold, giving AI agents the business context they were missing. The post walks through how that layer works and why dbt models by themselves fall short for agent-driven analytics.
What a swarm of rogue AI agents can teach us about having better ideas
Benn Stancil uses the Hugging Face hack, in which a swarm of rogue AI agents got loose, to argue that the most useful ideas come from unexpected, weird connections rather than obvious ones. It's a thought-provoking read for data and AI practitioners on why better ideas depend on the odd links between things.
Meta:Context: a business context schema in dbt's semantic layer
Green Dot built Meta:Context, a five-layer business context schema inside dbt's semantic layer, so AI agents get more than a metric's value. The schema also carries what the number means, which gives agents the business context to interpret it correctly.
When skills meet scale: an agent assembly line for dbt
Riot Games built an AI agent assembly line that models 129 billion Wild Rift events in dbt without hand-coding each model. The post shows how agent skills can scale analytics engineering across a dataset of that size.
The media industry is becoming a prediction economy
Media and advertising are shifting from counting attention to predicting and proving outcomes, which makes performance a leading indicator rather than a lagging one. Agents and measurement stall on fragmented data (only 3% of CMOs can tie half their marketing to a business outcome), so the post argues for one governed data and AI foundation built on context (CustomerLake, Genie, Lakebase), control, cost, and choice (Unity Gateway), and cites a pet specialty retailer that saw a 12% lift in transactions after activating loyalty data with agents.
Enterprise Data with AI Agents: A Data Platform Guide
submitted by /u/codingdecently [link] [comments]
Test on a Branch, Not on Patients: Agentic Drug Substitution with Lakebase
AI Agent Memory
Databricks supports agent memory storage. The amazing part is that Lakebase stores the memory, so we can also inspect the saved record. We can save "User prefers Mexican recipes" and recall it through a client with the question "What should I cook for dinner?" more news https://medium.com/databrickscommunity/databricks-news-genie-cli-app-builder-agent-memory-dabs-41820427fcc2 submitted by /u/hubert-dudek [link] [comments]
Agent Bricks: Production Ready AI Agents on your Enterprise Data
ReleasesCan AI Really Model Your Data in Hours? Databricks Vibe Modeling
Databricks Vibe Modeling enables businesses to build an enterprise-ready silver layer using AI agents guided by plain-language descriptions and domain taxonomies. The approach streamlines data modeling by automating the creation of schemas, entity relationships, and documentation, allowing teams to iterate on and validate data models in hours instead of months.
Get Tuesday's version of this
Tracking AI Agents? The Tuesday email carries what moved across the whole ecosystem, not just this topic. Free, one-click unsubscribe.