Beyond the Hype: Agents, Agendas, and the Vibe Coding Revolution
November 12, 2026 • 10:56
Audio Player
Episode Theme
Beyond the Hype: How AI Agents, Revenue, and Vibe Coding Are Reshaping Real-World Software and Business
Sources
United won’t let your AI agent book your flight
The Verge AI
Transcript
Alex:
Good morning, everyone, and welcome back to Daily AI Digest! It's November 12th, 2026, and we've got a packed show for you today.
Jordan:
We really do. We're talking OpenAI crossing ten billion dollars in quarterly revenue, an agent reliability startup borrowing tricks from self-driving cars, United Airlines drawing a line in the sand against booking agents, Databricks' truth-telling AI, and Google's new vibe coding tool for regular folks.
Alex:
So much to get into. But first, Jordan, did you see the Nvidia headline? Jensen Huang's job reportedly on the line, FBI investigating, board holding urgent talks?
Jordan:
I did. Wild timing because his keynotes practically run on vibes and confidence at this point.
Alex:
Right, if there's one thing AI can't predict, it's corporate boardroom drama. No model saw that one coming.
Jordan:
No GPU cluster in the world could've forecasted that plot twist. Okay, let's get into stories AI actually can help us understand.
Alex:
Let's start big. OpenAI's quarterly revenue reportedly crossed ten billion dollars for the first time, according to TechCrunch. That is not a small number.
Jordan:
It is not. And what's wild is the growth rate, not just the raw figure. We're talking roughly fifty percent jump from the previous quarter, which was six point seven billion.
Alex:
Wait, fifty percent quarter over quarter? That's not normal growth, that's rocket ship growth.
Jordan:
Exactly, and for a company this size, that kind of jump usually means either explosive new enterprise adoption, a pricing change, or both. It suggests ChatGPT and the API business aren't plateauing, they're accelerating.
Alex:
Okay but here's my skeptical question. Revenue is great, but what about the elephant in the room, the compute costs? Is OpenAI actually making money, or just making noise?
Jordan:
That's the real tension in this story. Revenue is a demand signal, it tells you people and businesses are genuinely paying for this stuff. But profitability is a totally separate conversation given how much they're spending on infrastructure and compute commitments.
Alex:
So it's less 'we found a profitable business' and more 'we found a very expensive, very popular business.'
Jordan:
That's a good way to put it. And this number now becomes the benchmark everyone else gets measured against. Anthropic, Google, even Meta's AI efforts, they all get compared to this ten billion dollar bar now.
Alex:
It's like OpenAI just moved the goalposts for the entire industry.
Jordan:
Pretty much. And honestly, for practitioners building on top of these models, this is reassuring in one sense. It means the provider you depend on isn't some fragile experiment, there's real commercial gravity here.
Alex:
Fair point. Okay, speaking of things that need to actually work reliably in the real world, let's talk about agents. Because this next story feels very timely.
Jordan:
This one's fascinating. According to TechCrunch, there's a startup called Plurai that's trying to make AI agents more reliable using the same playbook that helped self-driving cars get road-ready.
Alex:
Wait, so they're treating AI agents kind of like autonomous vehicles? What's the actual connection there?
Jordan:
The connection is simulation-based testing. Self-driving cars didn't get safe by just driving around randomly and hoping for the best, companies built massive simulated environments to test edge cases, weird weather, pedestrians jaywalking, sensor failures, all before the cars ever hit real roads.
Alex:
And Plurai wants to do that, but for software agents instead of cars.
Jordan:
Exactly. Because agents face a similar problem, they're probabilistic systems operating in unpredictable environments, except instead of avoiding a pedestrian, it's avoiding sending the wrong email to the wrong client or booking the wrong meeting.
Alex:
Okay, that actually makes a lot of sense when you frame it that way. Because right now most agent demos look amazing, but the second you put them in a messy real business environment, things fall apart.
Jordan:
That's the whole reliability gap the story highlights. Demos are controlled, scripted, forgiving. Production environments are chaotic. You've got weird edge cases, ambiguous instructions, systems that change underneath you.
Alex:
So simulation infrastructure could become like, the crash test dummies of the agent world?
Jordan:
That's a great analogy actually. And it raises this interesting question the story points to, what does 'safety validation' even mean for a software agent versus a two-ton vehicle? The stakes are different, but the need for rigorous testing before deployment might be just as real.
Alex:
I like this because it feels like an actual engineering answer to a problem, instead of just more hype about how agents will change everything.
Jordan:
Right, and if you're building or evaluating agentic systems for your company, this is the kind of infrastructure question you should be asking vendors. Not 'can your agent do cool stuff in a demo,' but 'how was this tested against edge cases before it touched my customers.'
Alex:
Which, funny enough, leads us right into our next story, because apparently not everyone wants agents touching their customers yet.
Jordan:
Oh, this is a good one. According to The Verge, United Airlines has said flatly that it will block AI agents from booking flights on behalf of users.
Alex:
Wait, they're actively blocking them? Like, technically preventing agents from completing bookings?
Jordan:
That's the reporting, yeah. United cited privacy and regulatory concerns. And what's interesting is they said this even though they haven't seen heavy agent usage yet. This is a preemptive defensive move.
Alex:
That's kind of telling though, right? If they're building walls before there's even a flood, they're clearly worried about something specific.
Jordan:
I think it comes down to liability and authentication. If an AI agent books a flight using your credit card and your personal information, who's responsible if something goes wrong? Is it the airline, the agent developer, the user, the platform the agent runs on?
Alex:
Nobody wants to be left holding that bag.
Jordan:
Exactly, and the story points out this isn't unique to United. DoorDash has taken a similar defensive posture against autonomous agent transactions. It seems like a pattern forming across industries that deal with real money and real personal data.
Alex:
So this is the gap between the vision of 'my AI assistant will just handle my whole life' and the reality of 'actually, no, come back when you have proper credentials.'
Jordan:
That's exactly the tension here. The agentic AI narrative promises frictionless automation, but real businesses have legal exposure, fraud concerns, and regulatory obligations that don't just disappear because the request came from a bot instead of a human typing on a keyboard.
Alex:
Does this mean we eventually need some kind of agent-specific API or identity standard, like a passport for bots?
Jordan:
That's probably where this is heading. Some kind of authenticated, permissioned way for agents to transact on your behalf that satisfies the airline's legal team and still lets the agent do its job. We're just not there yet.
Alex:
It's a good reminder that 'agents will do everything for you' is still more roadmap than reality.
Jordan:
Which is honestly a useful gut check for anyone building agent products right now. The tech might be ready before the business and legal infrastructure is.
Alex:
Okay, well, let's pivot to a story where an agent is very much welcome inside the house, just not booking flights, but telling the CEO uncomfortable truths.
Jordan:
This one's genuinely fun. According to TechCrunch, Databricks has an internal AI agent called Genie, and they've revised it to give CEO Ali Ghodsi candid, unfiltered insights into what's actually happening across the company.
Alex:
Wait, unfiltered how? Like it's telling him things employees wouldn't say to his face?
Jordan:
Pretty much. Ghodsi himself has said these are insights people wouldn't volunteer directly. So think about it, with twelve thousand employees, there's no way the CEO has visibility into everything happening on the ground. This agent is apparently surfacing that.
Alex:
That's a genuinely novel use case. We usually hear about agents writing code or answering customer support tickets, not basically functioning as organizational truth serum.
Jordan:
Right, this is agents moving into executive decision-making workflows, which is a different category entirely. It's less about productivity and more about visibility and organizational intelligence.
Alex:
Okay but doesn't this get a little uncomfortable? Like, how does this data even get collected? Are employees aware the AI is essentially reporting on them upward?
Jordan:
That's exactly the tension the story raises. There's a real trust and surveillance question here. If people know an AI system is synthesizing information that flows straight to the CEO, does that change how openly they communicate internally? Does it build trust or erode it?
Alex:
It's a double-edged sword. On one hand, leadership gets real visibility instead of filtered reports. On the other hand, it could make people more guarded if they feel like they're being watched by a bot.
Jordan:
Exactly, and I think this is going to be a template other companies watch closely. If you're building internal tools, this is a creative direction, agents not just helping individuals do their jobs, but helping leadership understand the organization as a whole.
Alex:
It's almost like a corporate nervous system. The CEO gets signals he wouldn't normally get, but it raises real questions about consent and culture.
Jordan:
Well said. And speaking of agents reshaping how organizations function, let's talk about our last story, which flips the lens to consumers building their own tools.
Alex:
Yes, this is the Google one, right? Something called Tabletop?
Jordan:
Right, according to The Verge, Google's experimental Tabletop tool lets users basically vibecode custom collaboration apps just by describing what they want.
Alex:
Okay wait, break that down. What does that actually look like in practice?
Jordan:
So imagine you want something like an Asana or Monday.com board, but customized exactly to how your team works. Instead of hiring a developer or wrestling with templates, you just describe what you want in plain language, and Tabletop generates an interactive hub that matches that description.
Alex:
So it's not writing code you then have to maintain, it's generating the actual working app from a description?
Jordan:
That's the idea, yeah. And what's notable is this isn't aimed at developers. This is a mainstream, non-technical audience experiment. It's bringing vibe coding, which we've mostly talked about in the context of engineers building software faster, into the hands of everyday users.
Alex:
That feels like a pretty big shift. We've talked a lot on this show about vibe coding as a developer productivity trend, but this sounds like it's skipping the developer entirely.
Jordan:
Right, and that's the bigger signal here. If major platforms like Google are productizing natural-language app generation for regular consumers, that could reshape how everyday software gets built and customized going forward.
Alex:
So instead of picking from a marketplace of templates, you just describe your version of the tool and it exists.
Jordan:
Exactly, and that has real implications for the software development lifecycle more broadly. If non-developers can generate working internal tools on demand, that changes what 'building software' even means for a huge chunk of the market.
Alex:
It's funny, we started this episode talking about OpenAI's ten billion dollar quarter, and we're ending with Google letting anyone vibecode a project management app in their spare time. That's a pretty wide spread of what counts as 'AI progress' these days.
Jordan:
That's the beauty of where we are right now. It's revenue milestones, safety frameworks borrowed from self-driving cars, corporate pushback on agents, internal truth-telling bots, and consumer-facing app generation, all happening in the same news cycle.
Alex:
Beyond the hype indeed. Okay, so quick recap for everyone following along at home. OpenAI's revenue is exploding, but profitability questions remain. Plurai wants to bring self-driving-style simulation testing to agents. United is drawing a hard line against booking agents. Databricks is using agents for internal transparency, not just productivity. And Google's Tabletop is bringing vibe coding to everyday consumers.
Jordan:
That about covers it. Lots of threads, but they all point to the same theme, AI is maturing from flashy demos into systems that have to deal with real business constraints, real money, and real organizational dynamics.
Alex:
Which honestly is a more interesting story than just 'AI is amazing,' because now we're watching it bump into the messy, complicated real world.
Jordan:
Exactly, and that's where the actual lessons are for anyone building in this space.
Alex:
Well, that's a wrap for today's episode of Daily AI Digest. Thanks for hanging out with us.
Jordan:
We'll be back tomorrow with more stories cutting through the noise. Until then, stay curious, and maybe don't let your AI agent try to book your next flight.
Alex:
See you all next time!