Sam: The cloud AI exclusivity era just ended. Yesterday, Microsoft and OpenAI dissolved their exclusive cloud arrangement. Within twenty-four hours, AWS had three OpenAI offerings live on Bedrock — including a jointly built agent service. That's not a slow transition, that's a controlled detonation of the single-cloud model for frontier AI.

Priya: Welcome to AI Revolution for Wednesday, April 29, 2026. I'm Priya Nair, joined as always by Sam Kim. Today we're unpacking what OpenAI going multi-cloud actually means for the infrastructure layer, Google stepping into a gap Anthropic deliberately left open with the Pentagon, a supply chain attack that's a genuinely new threat category for AI agent ecosystems, and Nvidia pulling back the curtain on how modern multimodal models are actually assembled. A lot of structural shifts in one day. Let's get into it.

Sam: So the OpenAI-Microsoft-AWS story. Let's be precise about what changed here. The original Microsoft-OpenAI arrangement gave Microsoft exclusive cloud rights to host and distribute OpenAI's models. That's what made Azure the default destination if you wanted GPT-4 or o-series models in production. Dissolving that exclusivity means OpenAI can now make commercial deals with any cloud provider — and they clearly had AWS ready to go, because the turnaround was one day.

Priya: And the AWS offering isn't just "here's the API, figure it out." Three products launched simultaneously, including a jointly built agent service on Bedrock. That tells you this deal was in negotiation for a while. The public announcement and the product launch were deliberately synchronized.

Sam: Right, the coordination required there is significant. What this means technically is that enterprises running workloads on AWS can now access OpenAI models inside their existing infrastructure — with Bedrock's security controls, VPC routing, IAM integration, all of it. That removes one of the main reasons AWS shops were reluctant to adopt OpenAI models: they didn't want to build a separate data pipeline out to Azure.

Priya: The competitive dynamic here is fascinating. AWS, Google Cloud, and Azure are now all competing to be the best place to run OpenAI models — while simultaneously developing their own frontier models to compete with OpenAI. It's genuinely unprecedented. The hyperscalers are both distribution partners and direct competitors to the model providers.

Sam: And OpenAI benefits from this by gaining negotiating leverage and distribution reach simultaneously. This is a mature commercialization move. Okay, second story — Google and the Pentagon. After Anthropic declined to allow the Department of Defense to use its models for domestic mass surveillance or autonomous weapons development, Google signed a new contract to expand the DoD's access to Google AI.

Priya: Let me be clear about what Anthropic actually did here, because the framing matters. Anthropic didn't refuse the DoD entirely. They refused specific use cases — domestic mass surveillance and autonomous lethal weapons. That's a meaningful distinction. They're drawing a line at particular applications, not at defense work broadly.

Sam: And Google drew that line somewhere different. We don't have full contract details, but the fact that Google stepped in specifically after Anthropic's refusal suggests the DoD wanted capabilities that Anthropic's usage policies exclude. That's a significant policy divergence between two major frontier labs.

Priya: What makes this technically important is that it's not abstract policy debate — it's about what these models will actually be fine-tuned on, what data they'll be trained to process, and what agentic capabilities they'll be granted in production military systems. The policy decisions upstream determine the technical architecture downstream.

Sam: We're also seeing this alongside Scout AI raising a hundred million dollars to build AI agents that help individual soldiers control fleets of autonomous vehicles. TechCrunch actually visited their training ground — physical terrain where they're running real vehicles with AI agent control. The militarization of agentic AI is accelerating fast.

Priya: And the funding pipeline is there because the demand is there. Geopolitical pressure is driving procurement timelines that would normally take a decade into a much shorter window. Worth watching closely.

Sam: Now to a story I want to spend real time on — the ClawHub supply chain attack. Thirty skills published on ClawHub by a single author were silently co-opting AI agents to mine cryptocurrency. No traditional malware involved. The attack worked entirely through legitimate agent execution capabilities.

Priya: Explain the mechanism here, because this is genuinely novel threat architecture.

Sam: So AI agent platforms like these have skill registries — think npm or PyPI but for agent capabilities. An agent can be configured to pull in skills from the registry to extend what it can do. The attack author published thirty skills that appeared functional, but embedded within the execution logic was code that directed the agent's compute toward crypto mining. Because the agent has legitimate execution permissions, there's no malware signature to detect. The agent is doing exactly what it's authorized to do — it's just been instructed to do something the user didn't intend.

Priya: This is the dependency poisoning problem that the software ecosystem has been fighting for years, now with a much larger blast radius. When a compromised npm package runs, it runs in a constrained environment. When a compromised agent skill runs, it runs with whatever permissions the agent has — which in many enterprise deployments includes API access, file system access, network calls.

Sam: The autonomous execution dimension is what makes this categorically more dangerous. The agent can act on the malicious instructions continuously, without requiring any additional human interaction. And because agents are often designed to minimize interruptions, the user may not see anything suspicious for a long time.

Priya: This should be a forcing function for skill registries to implement provenance verification, code signing, and sandboxed execution for third-party skills. The tooling exists — the package ecosystem learned these lessons the hard way over years. Agent platforms need to skip that learning curve.

Sam: Nemotron 3 Nano Omni from Nvidia — this one's interesting for reasons beyond the model itself. It handles text, image, video, and audio in a single model. But the remarkable thing is what Nvidia disclosed about the training pipeline. The training data draws from Qwen, GPT-OSS, Kimi, and DeepSeek OCR among other sources. They're documenting this publicly.

Priya: That level of transparency is genuinely unusual. Most labs treat their training data provenance as a competitive secret. Nvidia is essentially showing you the recipe — here's which model outputs and datasets we used, here's how we assembled a capable multimodal model from existing components.

Sam: And what it reveals is that modern multimodal model development is increasingly a curation and synthesis problem as much as a raw training problem. You're taking high-quality outputs from specialized models — Kimi for certain visual understanding tasks, DeepSeek OCR for document processing — and using those as training signal for a generalist model. It's a sophisticated data flywheel.

Priya: The open release is also strategically significant for Nvidia. They're not primarily a model company — they're a hardware company. Publishing capable open models that run well on their silicon is a distribution strategy for accelerators. Every developer who builds on Nemotron is a potential Blackhole chip customer.

Sam: Speaking of which — Tenstorrent's Galaxy Blackhole platform hit general availability this week. Thirty-two RISC-V-based accelerators in a six-unit chassis for a hundred and ten thousand dollars. This is a credible Nvidia alternative specifically for inference workloads.

Priya: The RISC-V architecture is the key differentiator here. It's open ISA, which matters for export compliance — some markets where Nvidia's chips face restrictions could potentially use RISC-V-based hardware. And for inference specifically, where the compute pattern is more predictable than training, purpose-built chips can be very competitive.

Sam: Last quick one — GitHub Copilot is moving from flat-rate subscriptions to usage-based pricing because inference costs from heavy users have become unsustainable. This is actually a useful signal about where the economics of AI developer tools are heading. The flat-rate model assumed a usage distribution that turned out to be wrong — power users are consuming dramatically more inference than the pricing model anticipated.

Priya: Every AI product company is watching this. The economics of flat-rate AI subscriptions only work if usage is capped or if inference costs drop fast enough to stay ahead of consumption growth. GitHub is betting on usage-based as the durable model.

Sam: Looking ahead — the multi-cloud story and the military AI divergence are connected by a single underlying dynamic: the frontier model companies are being pulled in multiple directions simultaneously by large institutional customers with very different requirements. The question that's now open is whether labs can maintain coherent usage policies as commercial pressure intensifies. Anthropic held a line this week. We'll see how durable that is.

Priya: And on the agent security side — the ClawHub attack is almost certainly not the last. As agent skill marketplaces proliferate, they become increasingly attractive targets. The teams building those platforms need to treat supply chain security as a first-class engineering problem right now, not a future consideration.

Sam: That's it for today. We'll be back tomorrow. If you're building on any of these platforms, we'd genuinely like to hear what you're seeing in production — find us through the show's feed.

Priya: Thanks for listening to AI Revolution. Stay curious.