Imagine hiring someone with 20 PhDs, then giving them no access to your company’s meetings, documents, or data.
That’s how @OpenAI Co-founder and President @gdb describes the problem with even the most capable AI models: intelligence without business context can only go so far.
At DATA + AI LIVE, Greg and Databricks Co-founder and CEO @alighodsi discuss what it takes for autonomous AI agents to do real enterprise work: access to business context, plus the permissions and guardrails that make them safe to trust. Then see how the new Genie puts that into practice.
Watch the full conversation: https://t.co/9lgzNWhC8i
1/ Today we’re publishing the Databricks AI Index, showing trends from enterprises who manage AI with our Unity Gateway. Data covers >10,000 companies with broad representation (Digital Natives, Fortune 500, Global 2000, etc...). Enterprise AI consumption is changing quite a bit:
Big shifts happening in the AI landscape. These stats are crazy, and they come from our Unity Gateway, one of the largest router of proprietary/open source tokens (quadrillions of tokens per quarter). It's a cross-section of over 10,000 large enterprises using our gateway. Check these stats:
→ We've seen open source models go from single digit percentage 6 months ago to now over 30% of the tokens!
→ 6 months ago most enterprises had 1 model provider, today 75% have 2+ and 50% have 3+ model providers.
Read @pwendell's thread 👇
I just finished talks about my software factories at two conferences. Afterwards a bunch of people came up and told me what they were surprised about. Here is a distillation of what people thought were hot takes from my two talks.
First hot take: I tell everyone to slow down. Most speakers go on about how fast they're going, but I strongly believe in pacing AI outputs to human speeds. I regularly tell AI-pilled CIOs and CTOs to chill: almost nobody is _actually_ going fast with AI. Engineering still moves at engineering speeds, and business moves even slower. The ones pushing too hard are starting to see downtime for it.
If you don't pace your AI to human speeds, everything starts breaking around you, even at small operations like my online video game. I only have about a dozen humans working with my factory, and only a few hundred active old-timer players in the community who get along well, and still, introducing AI has still been very rocky.
My agents have, at times, overwhelmed my players with features, my accountant with emails, my merge queue with tickets, and my machines with load. Agents have pissed off my admins, resulting in name-calling, they've made messes in the game, and they've launched broken OSS without permission. The list goes on.
I can get away with all this chaos because everyone involved in my operation is very forgiving. They're excited by the potential. But even so, I had to learn to slow down, real fast. And so that's what I preach.
Hot take #2: Should you buy a software factory? Do you even need one? No. You probably don't need one. Factories take an extraordinary amount of upkeep. They turn into garbage mountains unless you put a frightening amount of time and tokens into curating them. I had to burn my previous five factories down since it eventually became cheaper to rewrite them than to fix them. So I'm not out there advocating for software factories or swarms just yet. If you do want one, be aware that it is a significant commitment of both money and human leadership to keep one running.
Several people told me that I was the only one who stood up onstage, at either conference, and said Build, don't Buy. But my experience is that software factories grow to be highly bespoke to your domain. Mine is super tangled up with my game, and I think that's inevitable. Because the factory is not just building my product, it's supporting it too. It's a company in a box. And they're easy for Claude to build for you.
Third and arguably hottest take: Next year will have a lot of human/agent and agent/agent office drama, resulting from bringing in AI employees, and it will be gloriously funny, but also frustrating.
Many of you are already on this bandwagon, but everyone next year will have a personal chief-of-staff agent. Busy people, even hobbyists, will have whole entourages of helper agents. The hot take is that people will become so dependent on these little private entourages, that they'll bring them to work. Your people will talk to my people, etc. Whole protocols will emerge for private entourages negotiating work between humans, inside companies big and small.
Nearly all humans will wind up having to start working with AI employees next year, and it'll be the beginning of the biggest cultural change we've seen in a hundred years.
So that's the hot takes. Slow down. Only build a factory if you think you really need one. And focus on empowering yourself with your own agentic chief of staff (or team). Your entourage will define how you work with others, so start by perfecting how you work with them yourself.
Zero Day Launch of Kimi 3.1! This is an amazing open source model. It seems particularly good at coding! Try it on Databricks. Even better, connect your models to Unity Gateway and use Smart Routing to control your cost vs quality.
It's official - LanceDB and @Databricks are hosting Afterdream, the Reverie after party, at Madarae!
Join AI researchers, research engineers, ML engineers, and technical leaders working on multimodal data as we close out #Reverie2026.
Space is limited. Approval is first come, first served. Register here: https://t.co/LVznaHzOP7
The master biographer reflects at 91. The Robert Caro interview.
0:00:00 – How Caro gets people to talk
0:05:03 – Does America need a little more Moses today?
0:12:42 – Moses the young idealist
0:17:57 – Watching Moses lose power
0:24:01 – Did Moses realize he was changing?
0:27:53 – Building during the Great Depression
0:32:51 – The threats and promises of Lyndon Johnson
0:36:08 – Could Kennedy have passed Johnson’s laws?
0:41:00 – Getting a book down to one sentence
0:46:21 – All the material that never made it into the books
0:52:59 – Loneliness
New York is becoming one of Databricks’ biggest AI hubs. 🗽
We’re expanding at 5 Bryant Park to ~120,000 square feet across five floors, including a dedicated Engineering and Research floor.
With teams building technologies behind Genie, Unity Gateway and CustomerLake, our momentum in NYC is only growing.
interpretability might be the most important scientific problem in the world right now, as I don't think we can solve alignment if we don't know what we're building. I think I have good news about it. I co-authored early work in mechanistic interpretability at OpenAI and came away pessimistic, because neural networks appeared to fold into arbitrary tangled knots. years later, I started openai's first large-scale automated interpretability project, finding about 2% of neurons legible with the primitive tools we had
with modern agentic tools and a much closer look, the picture looks totally different. the vast majority in models up to trillions of parameters are legible, and their circuits beautiful. many famous examples of tangled neurons turned out to be misunderstood. The roadblocks I expected mostly aren't there. I now think ambitious interpretability will be solved by the time we need it most, and possibly quite soon, as automated scientists keep improving. it may be a bitter lesson for interpretability: the simple thing, at absurd scale, works
https://t.co/zHij5zwKGT
Cheeky Pint is back! Mark Zuckerberg @finkd and Alexandr Wang @alexandr_wang came to the pub to discuss their new frontier model, Muse Wonder.
00:00:24 Muse’s breakout use cases
00:07:28 The model is the product
00:14:35 Muse Wonder
00:24:56 How frontier models are built
00:48:26 Betting $100B
01:07:21 Agentic commerce
01:19:34 OpenRouter
01:20:06 Beyond the smartphone
01:27:00 Funding
01:34:06 Why AI won’t be winner-take-all
01:40:46 Meta Superintelligence Labs (MSL)
02:08:11 Working for Mark Zuckerberg
Two-time Oscar winner Ben Affleck explains how transformer-based AI differs from classical computing.
Classical software is deterministic, these models generate answers by "running information through the attention layers" and inferring an output.
----
Full video on "One More Question and GQ" YouTube channel, (link in comment)
🎉 Introducing Databricks AI Decide: make fast decisions on your governed data
Following the TypeSafe AI Jev launch, we’ve seen increasing demand for a fast, low-cost API that turns raw text into structured decisions. However, many of our enterprise customers are unable to use Jev due to data privacy and access concerns.
AI Decide is our enterprise-grade function for fast decisions on customer’s governed data. It is supported for batch use cases like processing millions of documents with SQL and for realtime applications like model routing through our REST API. Starting early next week, customers will also be able to govern permissions on the ai_decide function through Databricks Unity Gateway.
A big shoutout to @mattydtweetz@ivanzhouyq@nihit_desai@hanlintang for getting this new function launched in less than a week!
I’ve seen a couple of posts about this so wanted to demystify. Today, every Muse user gets a free computer in the cloud. It's a real computer, and we’ve designed the security architecture of the Muse Secure VM carefully so you and your Muse can do almost anything you could with a computer sitting under your desk while keeping you and the system safe from threats like prompt injection. We wrote about this at length in our security blog post – https://t.co/7HmiTrzoTd. Activity in the “runtime cell”, which you share with your Muse is unfettered, but sensitive actions are all overseen by the Sentinel, which runs outside of that cell. Similarly, all sensitive secrets - like the passwords you enter into Muse’s secure credential storage - are also stored outside the runtime cell.
The runtime cell gets its own root filesystem (including a full Ubuntu linux image) separate from the host filesystem where your other more sensitive data lives. Because it is isolated from the sensitive stuff that runs on the same box, this means that we can, and do, offer users full visibility and control over the files in the runtime cell. Just as you can when you install Linux on your home computer, you can poke around and see all the files that make the system work - both debian system files and the binaries and data files that implement the parts of Muse which run in the runtime cell.
This was a very deliberate choice - your Muse Secure VM truly is your own computer in the cloud. You can install software in it, write and compile code, use the browser to surf the web: it is your own Linux box that you can operate as you choose with your Muse. Poking around in this computer doesn't give you any privileged access to Meta infrastructure, or to other people's data
If I may geek out a little here for a second… As a kid I loved to take things apart to see how they worked. As a teenager I got into computers and soon found myself drawn to C:\WINDOWS\SYSTEM and the system registry, later Slackware’s /dev/, /proc/ etc – I could see how the system was laid out and as I explored what DLL files and .so files actually did, I gradually became able to meld the computer to my own will.
We’re really proud to be able to put a real computer in millions of people’s hands with a similar level of transparency. We built a file explorer right into the Library tab of the UI. We want you to be able to see the markdown files Muse writes while it thinks about how to serve you better, and explore the internals of the system if you’d like to.
So, when you ask your Muse to show you its entire filesystem, and receive gigabytes of files you’re seeing the full contents of the runtime cell. It’s yours to explore and enjoy!
If you’re not a geek like me, or simply want to download the data that you personally have created directly with your Muse, we added a feature for that too in Settings > Data controls > Download your agent data.