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)
Zepto's evaluation-first agent stack cut customer support costs 65% with payback under a month 10, while one team eliminated $1M/year in wasted AI agent spend in a single hour 8. Databricks is packaging agent tooling directly into workflows—Genie and Agent Bricks now drive governed action pipelines for energy theft investigations 2, and Consort extends agentic development to branching database testing 9.
Generated daily from the 10 most recent items mentioning AI Agents. Click any [N] to jump to the source.
We wrote about this
- Databricks serverless micro apps: scale to zero, not out yetDatabricks serverless micro apps, announced June 16, 2026: one VM per app, scale to zero, usage-based billing promised. Nothing shipped by September 16, 2026.6 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.11 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
Workshop, Sep 19: build explainable AI apps with Neo4j, GraphRAG, Cypher and LLM Agents
There's a hands-on workshop on September 19 relevant if your team runs its data platform on Databricks and is looking at adding an explainable, graph-backed RAG layer on top for reasoning over structured and unstructured data. You build: A knowledge graph in Neo4j that becomes your single source of truth for an agentic RAG system Agentic retrieval combining vector search, keyword search, and graph navigation Multi-step, verified entity and relationship extraction Text-to-Cypher for natural language graph querying Explainable, source-traceable answers with evaluation built in Runs on real financial filings and news data, working through a complete production use case. Led by Dr. Alessandro Negro, Chief Scientist at GraphAware, bestselling author. Link if you want to check it out submitted by /u/camerongreen95 [link] [comments]
How energy teams turn theft detection into governed action with Genie and AI business processes
A Databricks App orchestrates the full lifecycle of energy theft detection—turning ML-flagged suspicious accounts into prioritized investigations, dispatch-ready reports, and tracked recovery workflows, with Lakebase keeping live case state and recovery totals. Genie One, Unity Catalog, Unity Gateway, and Agent Bricks tie this together on one platform, delivering trusted metrics, governed AI usage, and automated executive reporting.
Could a “Data → Agent” composer be useful for Databricks?
I've been thinking about a gap between Databricks data and agent frameworks. Databricks already has a lot of the building blocks: - Unity Catalog - Genie / Genie Agents - MCP - Vector Search - AI Gateway - Agent skills/tools - MLflow - Omnigent / Kasal And tools like Omnigent and Kasal already solve a lot of the agent orchestration/execution side. But I'm wondering about the step before that: What if a customer already has a large, curated and governed Databricks data estate — how do we turn that data estate into an agent-ready configuration without manually wiring everything together? Something like: Existing Databricks Data Estate ↓ Data-to-Agent Composer ↓ ┌────────┼─────────┐ ↓ ↓ ↓ Domains Semantics Metrics ↓ ↓ ↓ Genie MCP Skills └────────┼─────────┘ ↓ Agent Configuration ↓ Omnigent / Kasal ↓ Agent The idea wouldn't be to build another chatbot or another agent framework. It would be a Databricks-native composition/bootstrapping layer that understands an existing Unity Catalog/data estate and generates the pieces needed for agents to work with that data — domain boundaries, semantic context, approved tools, Genie configuration, MCP exposure, skills, policies, evaluation setup, etc. In other words: Kasal/Omnigent: Agent → Tools/Data Proposed layer: Data Estate → Agent I'm curious if this is already solved somewhere in the Databricks ecosystem, or if people are currently doing this manually when building enterprise data agents. Would love to hear how others are approaching the “existing data estate → production-ready data agent” problem. submitted by /u/imsuryya [link] [comments]
Community BrickTalk | Real-Time Data & AI: Tripwise Demo
Hey r/Databricks ! Join us for community BrickTalk on Thursday, September 24 , focusing on real-time data streaming, AI agents, and governance using Databricks. BrickTalks is a community event series where Databricks experts share real-world use cases, demos, and practical insights for building with Data and AI, giving customers a direct line to the people behind the products. In this session, we'll walk through a live demonstration of the Tripwise Demo , featuring: Sub-Second Transactions & Streaming: Device registration into Lakebase with sub-second reads/writes, plus telemetry streaming via Zerobus through a governed Medallion architecture. AI-Generated Offers & Pricing: Generating real-time agent offers using Foundation Model APIs and scoring behavioral data for usage-based renewal pricing. Natural Language Analytics: Enabling underwriters, product managers, and marketing teams to query governed insurance data in seconds using AI/BI Dashboards and Genie. Unified Governance: Managing safety, compliance, and control end-to-end with Unity Catalog. This is a great chance to see real-world architecture in action and ask questions directly to Databricks experts. When: Thursday, September 24 9:00 AM PT 12:00 PM ET 5:00 PM BST (London) 9:30 PM IST Register here and save your spot submitted by /u/Subject_Ant1789 [link] [comments]
Subject: Possible incorrect answer key — Evaluating AI Agents assessment (Generative AI Engineer)
Google Drive connector in Lakeflow Connect is now generally available (GA)
The Lakeflow Connect connector for Google Drive is now generally available ! It’s now easier than ever to ingest structured and unstructured files from Google Drive into Delta tables for analytics and AI workloads. You can configure a managed ingestion pipeline through the UI or managed API. Managed pipelines automatically handle incremental processing, automatic retries with exponential backoff for source API rate limits, failure recovery, and provide rich Google Drive metadata. For direct control over ingestion logic, you can also just use the Spark + SQL APIs directly: spark.read , Auto Loader, read_files, or COPY INTO pointed at Google Drive URLs. https://preview.redd.it/j65yaaft3uoh1.png?width=2048&format=png&auto=webp&s=0f9f13cc63572b991232a8fa617aa1fe6697369c Link to public docs + references: Google Drive managed connector documentation Spark + SQL APIs and examples Community blog and video tutorial: From PDF to insights Data + AI Summit session: Intelligent Document Processing with Lakeflow Common workloads include: Loading Google Sheets, Excels, CSV, JSON, and other structured files into Delta tables. Ingesting PDFs, Google Docs, Google Slides, and images. Parsing documents with ai_parse_document to prepare content for extraction, search, and agents. Examples of using the Spark + SQL APIs: Read an Excel sheet from Google Drive with spark.read : df = (spark.read .format("excel") .option("databricks.connection", "my_gdrive_conn") .load("https://docs.google.com/spreadsheets/d/9k8j7i6f...")) Ingest unstructured documents + PDFs from a Google Drive URL with read_files , then easily parse them using ai_parse_document : CREATE OR REFRESH STREAMING TABLE gdrive_documents_table AS SELECT *, "_metadata" FROM STREAM read_files( "https://drive.google.com/drive/folders/1a2b3c4d...", format => "binaryFile", `databricks.connection` => "my_gdrive_conn", pathGlobFilter => "*.{pdf,docx}"); CREATE OR REFRESH STREAMING TABLE documents_parsed AS SELECT *, ai_parse_document(content, map('version', '2.0')) AS parsed_content FROM STREAM gdrive_documents_table; Coming soon: Ingest Google Drive’s per-file permissions and ACL metadata to power permission-aware AI agents, enterprise search, and more. If you try it, share what you are building and let us know if you hit any friction! submitted by /u/BricksterJ [link] [comments]
SharePoint connector in Lakeflow Connect is now generally available (GA)
The Lakeflow Connect connector for Microsoft SharePoint is now generally available! It’s now easier than ever to ingest structured and unstructured files from SharePoint into Delta tables for analytics and AI workloads. You can configure a managed ingestion pipeline through the UI or managed API. Managed pipelines automatically handle incremental processing, automatic retries with exponential backoff for source API rate limits, failure recovery, and provide rich SharePoint metadata. Soon, our managed connectors will also support ingesting SharePoint Lists and per-file permissions metadata. For direct control over ingestion logic, you can also just use the Spark + SQL APIs directly: spark.read , Auto Loader, read_files, or COPY INTO pointed at SharePoint URLs. Common workloads include: Loading Excel, CSV, JSON, and other structured files into Delta tables. Ingesting PDFs, Word documents, PowerPoint files, and images. Parsing documents with ai_parse_document to prepare content for extraction, search, and agents. https://preview.redd.it/89i379aattoh1.png?width=2180&format=png&auto=webp&s=292350dfddfc9bc1a4daf3fc4447394821206054 Link to public docs + references: SharePoint managed connector documentation Spark + SQL APIs and examples Community blog and video tutorial: From PDF to insights Data + AI Summit session: Intelligent Document Processing with Lakeflow Examples of using the Spark + SQL APIs (after first creating a UC connection ) : Read an Excel sheet from SharePoint with spark.read : excel_df = (spark.read .format("excel") .option("databricks.connection", "my_sharepoint_conn") .option("headerRows", 1) .option("dataAddress", "Sheet1!A1:M20") .load(" https://mytenant.sharepoint.com/sites/Finance/Shared%20Documents/Monthly/Report-Oct.xlsx") ) Ingest unstructured documents + PDFs from a SharePoint URL with read_files , then easily parse them using ai_parse_document CREATE OR REFRESH STREAMING TABLE sharepoint_documents_table AS SELECT , "_metadata" FROM STREAM read_files( " https://mytenant.sharepoint.com/sites/Marketing/Shared%20Documents ", format => "binaryFile", databricks.connection => "my_sharepoint_conn", pathGlobFilter => " .{pdf,docx}"); CREATE OR REFRESH STREAMING TABLE documents_parsed AS SELECT *, ai_parse_document(content, map('version', '2.0')) AS parsed_content FROM STREAM sharepoint_documents_table; Coming soon: Ingest SharePoint Lists into Delta tables (coming super super soon) Ingest SharePoint’s per-file permissions and ACL metadata to power permission-aware AI agents, enterprise search, and more. If you try it, share what you are ingesting and where you hit friction! Don't hesitate to ask questions! submitted by /u/BricksterJ [link] [comments]
Announcement | How we eliminated $1 million a year of wasted AI agent spend in one hour
Introducing Consort: Test-driven development on a branching database
Consort brings test-driven development to database branching, giving each branch its own isolated copy of data so tests run against realistic state without touching production. The post walks through what changes when your database can branch like code, demonstrates an agentic development workflow built on it, and shows how to try Consort yourself.
Evaluation-First AI Agents: How Zepto Scales Customer Support on Databricks and MLflow
Zepto built its customer support agents on Databricks and MLflow using an evaluation-first approach, treating traces, golden datasets, and LLM-as-judge checks as core infrastructure and connecting development and production through a dual-loop architecture with a strict quality gate. The result: 65% lower support costs and payback in under a month, giving other AI builders a reusable blueprint for engineering reliability, cost, and risk into production-grade agents.
I merged two databases (Postgres and Elasticsearch) into Lakebase, then threw 200 AI agents at it.
submitted by /u/Limp-Park7849 [link] [comments]
Tutorials3. What is Unity AI Gateway | How to Control AI Spending
Unity AI Gateway sits in front of multiple AI models and lets you abstract them behind a single endpoint, enabling seamless model swaps without changing application code. Every request gets logged to system tables, giving you centralized visibility into spending and usage per model, user, and tool.
Community BrickTalk | One Platform, Any Source: Unifying Enterprise Data with Lakeflow Connect
Hey r/Databricks ! We’re hosting a free, community-sponsored BrickTalk on Thursday, September 17, 2026, focusing on how to simplify and scale data ingestion using Lakeflow Connect! BrickTalks is a community event series where Databricks experts share real-world use cases, live demos, and practical insights, giving you a direct line to the people building the products. Stop struggling with fragmented data across disparate sources. In this session, we'll demonstrate how Lakeflow Connect enables seamless data ingestion from SaaS apps, databases, and cloud storage directly into the Databricks Platform with zero infrastructure management. 🛠️ What We’ll Cover Native Data Ingestion: Learn how Lakeflow Connect provides fully managed ingestion directly into Unity Catalog as governed Delta tables. Simple Integration: See how to easily connect data sources using a simple UI or API. Accelerated AI & Analytics: Discover how unifying your data powers Customer 360, Operations, and downstream AI agent workloads. ⏱️ Global Times PT: 9:00 AM ET: 12:00 PM BST (London): 5:00 PM IST: 9:30 PM 👉 Register here to save your spot! submitted by /u/Subject_Ant1789 [link] [comments]
The 40-year-old database rule agents just broke: How LTAP unifies OLTP and OLAP workloads
LTAP (Lake Transactional/Analytical Processing) resolves the decades-old row-versus-column tradeoff between OLTP and OLAP systems by unifying transactional and analytical workloads at the storage layer rather than the engine layer, succeeding where HTAP has historically stalled. This shift is driven by AI agents, which need near-real-time read and write access to live operational data at a speed and cost neither traditional pipelines nor HTAP architectures can deliver.
Databricks-Native AI Agent for Job Incident Detection, RCA & Safe Remediation
Governance beyond security: knowledge, context & ontology on the lakehouse
Existing governance artifacts like classification tags, data contracts, and lineage provide the semantic foundation needed to run catalog-centered AI agent lifecycles directly within Unity Catalog. Anchoring this business context in catalog metadata keeps production PHI within governed boundaries while allowing cheaper models to deliver trusted results.
Agentic AI moves fast. Your data decisions should move faster.
submitted by /u/ConstantNo2668 [link] [comments]
Tutorials2. AI Agent Policies: How to Control What Agents Can Do
AI agent policies sit between agents and their tools to evaluate actions and enforce spending limits, tool usage restrictions, and risk scores. Using the open-source Omnigent framework, developers can configure these policies to automatically pause execution and require human approval when thresholds are crossed.
Announcing the Databricks Big Book of AgentOps
The Databricks Big Book of AgentOps provides a practical blueprint for building, evaluating, governing, and improving AI agents in production. It delivers field-tested architectures, technical best practices, and guidance across observability, cost management, and stakeholder alignment while highlighting common pitfalls to avoid.
How we eliminated $1 million a year of wasted AI agent spend in one hour
Broken MCP tool calls and silent retries can quietly waste over $1 million annually in tokens and engineering hours across AI agent fleets. Tracing tool calls with Unity Gateway and analyzing spend with Genie One enables teams to rapidly deploy fixes and design tools that gracefully handle ambiguous LLM inputs.
How Discovery Bank delivers hyper-personalized banking at scale: behavioral AI, governed data, and real-time decisioning
Discovery Bank achieved a 40% uplift in client engagement impact by building reusable, AI-driven data products and real-time next-best action models on Databricks. Their architecture accelerates data pipeline workflows by 20x and data product creation by 5x while ensuring AI agents operate within existing governance controls.
Building Agentic Applications on Databricks - file not found for ./Includes/Classroom-Setup-2
News1. AI Model Routing: How Smart Routing Picks the Right LLM
Smart routing evaluates individual development tasks separately to assign them to the most cost-effective capable language model. The approach automatically splits work across different models and runs agents in parallel to build applications more efficiently.
Building for the AI Era: Lakebase, Streaming, and Lakehouse Innovations at VLDB 2026
Databricks is bringing Lakebase, Structured Streaming, and Lakehouse optimizations to VLDB 2026, spotlighting Lakebase as a third-generation cloud database that decouples transactional compute from storage to support agentic workflows. The company's Engineering and Recruiting teams will also be on-site at the conference.
Vertical Advantage: Transforming Industries with Lakebase and Agentic AI
Databricks Lakebase partners are shipping production-ready, industry-specific solutions—from fraud and regulatory-change agents to real-time claims, prior authorization, dynamic pricing, and grid intelligence—built on a single governed foundation for operational data, analytics, and AI. Powered by Lakebase's serverless Postgres, sub-10ms operational serving, zero-copy branching, and agent-native memory, these solutions are deployable today and designed to turn platform capability into measurable business value.
Object Storage + WAL: Lakebase Postgres for the agentic era
Lakebase Postgres now decouples storage from compute by pairing object storage with a write-ahead log, targeting the I/O bottlenecks agentic workloads create in traditional OLTP setups. The architecture is built for new deployments handling agent-driven database interactions rather than retrofitted onto existing ones.
Introducing Governance Hub: Intelligent, account-level governance over your Databricks estate
Governance Hub gives Databricks admins a single, account-level view of data governance, AI usage, and cost across their entire estate, with each vertical surfacing KPIs and drill-downs so teams can assess governance health without building custom dashboards. A built-in Genie layer adds agentic insights, surfacing anomalies and governance gaps enriched with context about the underlying assets and workloads.
TutorialsPages in Unity Catalog: Govern Business Knowledge for Humans and AI
Databricks' Pages feature enables teams to author and publish authoritative definitions of business concepts, metrics, and terms within Unity Catalog Semantics, organized by domain. Genie AI uses these human-curated pages to answer questions with verified sources and citations, replacing guesswork with trustworthy, governed knowledge.
How Databricks Uses AI to Accelerate Incident Investigation
Databricks' AI SRE now handles over 2,000 daily investigations across 150+ teams, helping engineers troubleshoot 100s of microservices spread across 1,500 Kubernetes clusters in 70+ regions and three clouds. Rather than relying on black-box reasoning, the system uses composable agentic runbooks and ties every diagnostic recommendation to verifiable raw evidence, embedding a context-first approach into its design.
An AI agent that validates and PRs your Unity Catalog access requests, and knows when to say no
Evaluating AI Agents Live at the Grounded Reasoning Cup
EventsBuilding Governed Agents with Databricks
Databricks extends its Unity Catalog governance layer to AI agents, MCP servers, and tools to solve "agent sprawl" by providing centralized discovery, access controls, and audit logging. The system allows developers to quickly build agents while IT teams enforce fine-grained policies, manage credentials, and track end-to-end request and response lineage.
EventsFrom Primitives to Production: How Anthropic Builds Agents
Anthropic defines agents as LLMs in loops with tool access, leaning on model intelligence over rigid workflows, and uses domain-specific skills, MCPs, and evals to build effective agents across sectors. A demo showed a site reliability agent autonomously identifying a database pool issue, fixing the code, and generating a postmortem.
Learn Databricks Agent Bricks | Build Enterprise RAG Agents
Agentic AI Projects?
Hi, Curious. What are some agentic AI projects you guys have worked on or implemented and how have they added value? I’m a newbie working in this space and trying to spar for some interesting project ideas :). One idea I’m thinking of already is an agentic conversational data reporting agent that also generates PowerPoints, emails, etc. suited to some pre-defined templates in addition to just being a conversational data explorer. submitted by /u/BearPros2920 [link] [comments]
Designing effective Genie Agents from a single prompt
Genie Agents let teams turn trusted business context into domain-specific AI agents from a single prompt, reasoning across structured data, documents, and files governed by Unity Catalog without constant prompt tweaking. The post argues that weak agent answers usually stem from missing context rather than bad prompts, and recommends starting with one focused, benchmarked use case as the foundation for expanding with more knowledge, tools, and workflows.
Databricks Document Intelligence: pushing the frontier for complex document extraction
Databricks Document Intelligence's new Precision Mode targets the failure points of complex document extraction—cross-page reconciliation, long outputs like thousands of invoice line items, and schemas requiring reasoning and computation—by pairing custom finetuned extraction models with an agentic harness that reasons in stages and merges parallel subagent outputs. Across six complex document benchmarks, it outperforms the next best frontier model by seven points on accuracy.
Evaluating AI Agents Live at the Grounded Reasoning Cup
Stanford's team won the Grounded Reasoning Cup with 63.3% accuracy on OfficeQA Pro V2, a new 120,000-page U.S. Treasury document benchmark, using an end-to-end agent optimization approach combining reusable skills, document-representation fallbacks, and adaptive verification. Across all 11 academic teams, out-of-the-box frontier agents averaged under 30% accuracy, showing that agent performance tuned on one benchmark doesn't reliably generalize to a new corpus.
The prototyping tax is killing your AI roadmap
Platform-native agents grounded in business semantics—like Databricks Genie plus Unity Catalog—eliminate the "prototyping tax" of fragmented context and siloed domain knowledge, hitting 77% accuracy versus 56–72% for general coding agents at roughly half the cost. Abacus Insights proved the approach even in regulated settings, cutting new-client onboarding time by about 50% and manual data-mapping effort by 40% inside a HIPAA-grade environment.
Why agentics projects fail and how to fix them
Why do some Databricks agentic AI deployments succeed while so many fail? The data points to specific, identifiable failure patterns—and this post breaks down what they are and how teams can fix them.
Databricks App architecture with AppKit - agentic app with governed write-back functionality
Electric joins Databricks to bring WASM Postgres to AI agent sandboxes
Electric is joining Databricks to bring WASM Postgres and data primitives like PGlite to AI agent sandboxes. This extends Databricks Postgres capabilities to the edge, allowing lightweight agent databases to sync back to a centralized Lakebase on durable object storage.
Innocent until combined: Blocking the lethal trifecta with Omnigent Contextual Policies
Omnigent Contextual Policies prevent AI agent data exfiltration by tracking the lethal trifecta—private data access, untrusted content exposure, and outbound transfer—and blocking the outbound step once two legs are active. Configured by humans rather than the model, the policy only triggers when data is actually accessed so ordinary single-leg operations remain unblocked.
NewsHow AI Helps Match Doctors With Communities in Need | Databricks for Good
Databricks provides pro bono services and compute discounts to help nonprofits stay lean through its Databricks for Good program. The video demonstrates the Virtue Foundation agent, which uses Genie and interactive hex maps to identify underserved populations and medical facility distribution in Kenya.
NewsOmnigent: Open-Source Meta-Harness for AI Agents | Matei Zaharia
Omnigen is an open-source meta-harness developed by Databricks that acts as an orchestration and control layer to wrap, manage, and combine multiple AI coding agents. The platform introduces contextual security policies, cost controls, multi-agent task routing, and sandbox integrations to enable collaborative workflows and centralized governance.
Managing AI Coding Costs at Scale
AI coding tools deliver immense value: at Databricks, agentic coding has measurably...
What is an AI Assistant?
Enterprise AI assistants use large language models, retrieval-augmented generation, and agentic frameworks to execute workflows ranging from data analysis to autonomous pipeline management. Choosing the right tool requires evaluating data integration depth, governance controls, extensibility, and alignment with your team's existing workflows and skill levels.
TutorialsLangChain Tutorial - Build an AI Agent with Tools | Chapter 10
This video teaches how to build AI agents using the LangChain framework in Python. It demonstrates initializing a model, registering Python functions as structured tools, and creating both single agents and supervisor-sub-agent architectures.
NewsBuilding Agents on Databricks with Custom Apps and Omnigent
This video demonstrates how to build, update, and govern custom AI agents on Databricks using Agent Bricks, Databricks Apps, and Omnigent. The tutorial shows how to integrate Model Context Protocol servers, track execution with MLflow traces, schedule automated agent tasks, and manage security policies through Unity AI Gateway.
Building an Agentic HR Front Door on Databricks
What are Agentic Workflows?
Agentic workflows move beyond rigid, traditional automation by using autonomous AI agents that dynamically plan, select tools, and adapt to intermediate results at runtime. Deploying these workflows for enterprise efficiency and scalability requires strong governance, clear business objectives, and production-grade infrastructure.
What is Tool Calling?
Tool calling transforms basic chatbots into action-oriented AI agents by executing a structured loop to interact with external tools, APIs, and systems. Databricks Agent Bricks provides a governed environment to build these agents grounded in enterprise data, featuring native support for the Model Context Protocol and Unity Catalog governance.
From analytics engineer to context engineer
Data modeling is shifting from powering dashboards to structuring context for AI agents, marking the rise of the context engineer. This first installment in a new series examines the transition, starting with how to model internal Gong data.
TutorialsBuilding Agents on Databricks with Custom Apps and Omnigent
The video demonstrates how to build, update, and govern a store operations AI agent on Databricks using Model Context Protocol servers and custom apps. It shows how to use Omnigent and CodeX to add new context and tools, redeploy the application, and manage governance and traces through the Unity AI gateway.
Databricks joins the Open Secure AI Alliance to advance AI safety and security
Databricks has joined the Open Secure AI Alliance as an inaugural member to help secure the full AI stack through open research, tooling, and architecture alongside partners like NVIDIA. To advance this effort, Databricks is contributing open technologies including the Omnigent agent meta-harness, the DASF 3.0 security framework, BlackIce red teaming, and the Lakewatch Security Lakehouse architecture for threat detection and response.
Breaking changes include removal of direct AWS and Azure credential fields from model provider configurations and State field type changes in bundle deployment operations. New features add KinesisStreamConfig support for ML streaming sources, a Mode field for pipeline updates, and Pi coding agent attribution in the User-Agent header.
Ingest semi-structured data faster and more efficiently with Variant - Now Generally Available
Databricks Variant is now Generally Available, enabling teams to achieve up to 30x faster reads on semi-structured data while handling unpredictable schema changes without pipeline updates. The feature is broadly integrated across the platform, supporting data workloads like Auto Loader and Spark Declarative Pipelines alongside AI tools like Agent Bricks and AI Functions.
Databricks Completes Acquisition of Panther: Accelerating the Security Lakehouse Era
Databricks has officially completed its acquisition of Panther, integrating its software-driven detection engine and SOC workflows with Lakewatch's open security lakehouse foundation. This enables security teams to retain petabytes of telemetry in open formats, deploy autonomous AI agents for real-time triage, and run detections-as-code to accelerate incident response.
NewsClaude vs GPT: Live AI Debate with Omnigent
OmniGen is a new open-source project that orchestrates different AI agents like ChatGPT and Claude to collaborate and communicate within a single system. The architecture consists of a runner that sandboxes agents into uniform sessions and a server that manages control layers, policies, and chat history.
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.
