Tag: agentic AI

Prince Mario-Max Schaumburg-Lippe: IBM Bob Goes Self-Hosted for Sovereign AI Coding

IBM made a simple pitch to the world’s most cautious companies this week: keep your AI coding agent, and all the code it touches, inside your own walls. On October 1, the company announced self-hosted deployment for IBM Bob, its agentic software development platform, letting organizations run it on-premises, in private or sovereign clouds, or fully air-gapped with no outside network connection at all.

Between the summer’s agent security incidents and a string of compliance headaches, enterprises have learned that the question isn’t just what an AI coding agent can do. It’s where the agent runs, what data it can see, and who controls both. IBM’s answer: let them run it wherever they already keep their secrets.

What Bob is, and what changed

Bob is IBM’s agentic software development platform, built to move teams beyond simple code generation into full software delivery and modernization work. It plans, writes and tests code across repositories, and IBM has been positioning it as the enterprise-grade answer to the agentic coding wave.

The self-hosted option is the new unlock. Companies can now deploy Bob on customer-managed infrastructure, run supported models on premises, including in air-gapped environments, using models they’ve licensed, or connect to external model services through hybrid configurations. The code, the application context and the data never have to leave the customer’s environment.

IBM framed the release around a specific statistic: 68% of executives say data-residency rules are hard to meet, per the company’s research. And there’s a structural tailwind. Futurum Research projects that hybrid and edge deployments will capture 44% of the AI infrastructure market by 2030, as organizations chase sovereign control alongside ecosystem connectivity. IBM is building for the world that report describes.

Why regulated industries couldn’t wait

Think about who has been locked out of the AI coding boom. Banks with proprietary trading systems. Hospitals with patient data. Government agencies with classified code. Defense contractors. These organizations face strict security and compliance requirements that make sending source code to a public AI cloud a non-starter, no matter how good the underlying model is.

The standard workarounds have been unsatisfying. You could ban AI coding tools and watch your engineers use them anyway on personal accounts, which is the shadow-IT outcome nobody admits to in meetings. Or you could try to bolt governance onto a cloud service and spend a year negotiating data-processing agreements. IBM’s bet is that the third option, run the agent where your code already lives, is the one enterprises will actually buy.

The timing isn’t accidental. The summer of 2026 gave the industry several sharp reminders that autonomous coding agents with broad permissions can do real damage, and Gartner analysts have been openly questioning whether agentic AI can be fully secured with current tools. That raised the bar for everyone. IBM’s response is architectural rather than procedural: instead of trying to contain an agent running in someone else’s cloud, keep the agent and the blast radius inside infrastructure the customer already controls.

The sovereignty wave is bigger than IBM

Bob’s self-hosted launch is one data point in a much larger shift. The AI industry spent 2023 and 2024 centralizing everything in a handful of hyperscale clouds. In 2026, the pendulum is swinging back toward control: where models run, who owns the weights, which jurisdiction the data sits in. Sovereign AI isn’t a slogan anymore; it’s a procurement requirement.

That shift is visible across the stack. Open-model ecosystems keep gaining ground, with services like Prime Intellect’s inference platform letting teams serve frontier open models on their own GPUs, and Bob’s self-hosted mode can run on licensed models the customer chooses. Meanwhile the security layer around agents is becoming its own industry, with Armadin raising $255.5 million to defend against AI-driven attacks. IBM is stitching the pattern together: open or licensed models, your infrastructure, your governance.

Neel Sundaresan, IBM’s general manager of AI and Automation, put the thesis plainly at the launch: organizations need AI that operates inside environments they control, especially when working with sensitive code and regulated data. “Bring AI to the data instead of moving the data to the AI” is the kind of sentence that sounds like marketing until a compliance officer explains why it’s the only sentence that matters.

What enterprises actually get

The practical value breaks down into three buckets. First, data residency: code and context stay in the jurisdiction and the data center the company already answers to regulators about. Second, governance: the organization’s own security policies, access controls and audit trails apply to the agent, because the agent runs on the organization’s systems. Third, model flexibility: Bob isn’t locked to a single vendor’s models, so teams can use what they’ve licensed or what their compliance posture allows.

That third point deserves emphasis. Most AI coding tools are model-first: you get the vendor’s model, take it or leave it. Bob’s self-hosted deployment is infrastructure-first: the platform adapts to the models and environments the enterprise already has.

The skeptical read, and why it’s incomplete

The obvious criticism is that self-hosted AI is expensive and complicated, which is why the industry moved to the cloud in the first place. Running models on premises means managing GPUs, updates, scaling and security patches yourself. For many companies, that’s a real cost.

But that criticism misses who this product is for. The banks, governments and healthcare systems that need air-gapped AI already run enormous on-premises infrastructure. They’re not choosing between self-hosted and cloud the way a startup does. They’re choosing between self-hosted AI and no AI, because the compliance answer on public cloud is no. IBM isn’t asking these organizations to take on new infrastructure religion. It’s meeting them where they already live.

There’s also the competitive angle to consider. The cloud-based coding agents are fighting a feature war: who ships the smartest autocomplete, the best agent loop, the fastest model. IBM is fighting a different war, the trust war, and in regulated industries that’s the war that decides purchasing. A slightly less capable agent that your compliance team approves beats a brilliant agent they veto. Every time.

What this signals for the rest of 2026

Watch for two things. First, expect the other enterprise AI vendors to follow with self-hosted or sovereign deployment stories of their own, because IBM just made this table stakes for the regulated market. Second, watch IBM’s third-quarter results later this month: the stock popped about 4% in pre-market trading on the announcement, and investors will want to see whether enterprise AI demand is translating into the kind of contract growth that justifies the platform bets.

The deeper signal is about what enterprise AI adoption actually looks like. It’s not one big migration to the public cloud. It’s a patchwork: some workloads in the cloud, some on premises, some air-gapped, all needing governance that works the same everywhere. The vendors that win the enterprise decade will be the ones that stop asking where the AI runs and start making it run well wherever it is.

IBM Bob’s self-hosted launch is a bet that control is the feature. In the industries that matter most to IBM’s business, that bet has never looked safer.

Prince Mario-Max Schaumburg-Lippe: DigitalOcean Agent Droplets Bundle AI Agent Stack

Fourteen years ago, DigitalOcean made the cloud something one developer could afford with the $5 Droplet. On October 1, the company tried the same trick for AI agents: Agent Droplets, a monthly subscription that bundles everything an agent needs, compute, memory, storage, inference and tool access, into two tiers at $50 and $200 a month.

The pitch is deliberately unglamorous, and that’s the point. Building an AI agent that does something useful has gotten easy. Running one in production has not. DigitalOcean’s answer is to stop billing you like a hyperscaler and start billing you like a service.

What an Agent Droplet actually is

Agent Droplets sit on top of DigitalOcean Managed Agents, the managed agent infrastructure layer the company pushed into public preview in late September. Managed Agents combine two services: a Harness Runtime that gives agents persistent, isolated microVM compute environments, and an Action Gateway that provides governed access to more than 16,000 external tools. Add serverless inference, persistent memory and storage, and you have the full stack an agent needs to run.

The new part is the packaging. Agent Droplets come in two sizes, Pro at $50 a month and Team at $200 a month, with discounts of 15% and 20% on included resources respectively. You pick a size and start. No per-CPU-hour metering, no per-token inference bills, no separate storage invoices. DigitalOcean says developers have already spun up thousands of agent sessions on the underlying platform, and the Droplets product is the commercial shape around them.

Sessions can pause when idle, which saves resources while preserving context, and each session runs on security-hardened compute and storage. For anyone who has watched an agent rack up cloud charges overnight because a loop didn’t terminate, that pause button matters.

The six-invoice problem

DigitalOcean’s product chief, Vinay Kumar, laid out the motivation with a customer anecdote that will feel painfully familiar to anyone building agents. One team described its stack as OpenCode Go as the harness, Fly.io for sandboxes, AWS for storage, Fireworks for inference on open models, Anthropic for frontier models, and Parallel for web search. Six vendors, six invoices, dozens of pricing units, plus glue code holding it together. Nobody on the team could say what a single agent run had cost.

This is the defining cost problem of agentic AI in 2026. The models keep getting cheaper per token, but the surrounding machinery, sandbox time, memory, storage, tool calls, orchestration, is where budgets bleed out. The hyperscalers run everything, but they meter it as a dozen separate line items with enterprise-grade complexity to match. The sandbox and harness vendors cover pieces but not the whole stack. DigitalOcean is betting that the missing product is a readable bill.

It’s a bet the company has won before. The original Droplet didn’t invent virtual machines; it made them legible. One price, one dashboard, one developer. Agent Droplets are the same idea applied to a much messier workload, and the timing is right: agentic coding and autonomous assistants went from demos to real deployments this year, and the teams deploying them are discovering that infrastructure, not model quality, is the bottleneck.

Why this lands now

The agent infrastructure conversation has been building all year. Persistent AI agents that handle multiple jobs and retain context are where the industry’s investment is flowing, with OpenAI, Meta and Google all pushing in that direction. Enterprise coding agents need sandboxes they can trust, which is why security vendors like Armadin just raised $255.5 million to secure agentic AI systems. And on the serving side, platforms like Prime Intellect’s new inference service are giving teams open-model endpoints they can control.

DigitalOcean’s move slots into the middle of all this. It doesn’t ask you to choose between open and closed models, or between your own GPUs and someone else’s. It asks a simpler question: what if running an agent felt like running a server in 2012? Pick a size, deploy, get one bill.

The flat-rate structure also solves a real psychological problem. Per-token and per-hour pricing makes every agent experiment feel like a gamble with an open tab. A fixed subscription makes experimentation cheap in the way that matters, emotionally. Teams try more things when the meter isn’t visibly running. More experiments mean more of them succeed.

Voice agents are the canary here

One of the first workloads that will stress this kind of infrastructure is voice. Microsoft’s new voice stack can complete a conversational turn in under a second, and voice agents need always-on runtimes with fast inference and persistent session memory, exactly the bundle DigitalOcean is selling. The company that makes agent infrastructure boring wins the segment that makes agents feel real.

Who this is really for

The obvious customers are indie developers and small teams, the same crowd that made DigitalOcean what it is. If you’re a solo dev with an agent that monitors your inbox, triages support tickets, or maintains a codebase, the $50 Pro tier turns a scary open-ended infrastructure bill into a line item you can budget. That’s the audience DigitalOcean has always served, and the product reads like it was designed by people who remember that audience.

But don’t sleep on the second audience: larger companies prototyping agent workflows. The Team tier at $200 a month is cheap enough to greenlight without a procurement process and predictable enough to demo to a CFO. Once the prototype works, the conversation about scaling happens on DigitalOcean’s terms. That’s the classic land-and-expand playbook, and it worked for the original Droplet. Enterprises that started on a $5 server ended up running production on them.

The honest caveat is capacity. Flat-rate pricing on GPU-backed inference only works if usage stays within the bundle’s guardrails, and agent workloads are notoriously spiky. DigitalOcean’s answer is the tiering and the resource discounts, but the real test comes when a customer’s agent goes viral and the meter-free model meets its first surprise. The company will need the unit economics to hold. Early traction, thousands of sessions already started, suggests it’s at least close.

The bigger picture

Every maturing technology goes through a phase where the infrastructure stops being the exciting part and starts being the reliable part. Cloud computing had it. Databases had it. AI agents are having it now. DigitalOcean’s Agent Droplets won’t win any benchmark shootouts, and they aren’t trying to. They are trying to make the most ambitious software of 2026 feel as ordinary as a web server.

That’s how technologies actually win. Not with the best demo, but with the invoice nobody thinks about. A decade from now, running an AI agent will feel as mundane as renting a virtual machine. Agent Droplets are a bet that the future arrives one predictable monthly bill at a time.

Prince Mario-Max Schaumburg-Lippe: Google Antigravity Adds Claude 5.5 Coding Models

Google quietly did something last week that developers noticed immediately: it put a rival’s flagship models inside its own coding IDE. On October 3, Google added Anthropic’s Claude Opus 5.5 and Claude Sonnet 5.5 to the model selector in Antigravity, its agentic development workspace, for paying subscribers on the Google AI Pro and Google AI Ultra tiers.

The update closed a gap that had been sitting in plain sight. Antigravity’s model page had listed the new 5.5 models as unavailable since late September, and developers were asking when the current generation would show up. It showed up with no fanfare, no blog post, just two new entries in a dropdown. Which, honestly, might be the most Google way to ship anything.

What changed in the model lineup

Both additions are the reasoning “thinking” variants: Claude Opus 5.5 (thinking) and Claude Sonnet 5.5 (thinking). Access is gated to non-trial Google AI Pro and Google AI Ultra subscriptions, which run $19.99, $99.99 and $199.99 a month depending on the tier. Free accounts, the cheaper Plus tier, and Enterprise accounts don’t get either model, so the availability picture is narrower than a simple paid-versus-free split.

At the same time, Google set an expiration date on the old guard. Claude Opus 4.6, Claude Sonnet 4.6 and the open-weights GPT-OSS-120B are scheduled for removal on November 2. Gemini 3.1 Pro stays as the default, with Gemini 3.8, 3.7 and 3.6 Flash rounding out Google’s own options. If you are still running on 4.6 in Antigravity, you have about a month to move your workflows.

That retirement schedule matters more than it looks. When a platform kills a model version, every prompt, benchmark and test result built on it becomes history. Teams that treat model choice as casually as a dropdown setting will feel this one. The ones that pin versions and track which model produced which result won’t.

The models themselves are worth the slot

Claude Opus 5.5 shipped September 22 with a 20% price cut over Opus 5, dropping to $4 per million input tokens and $20 per million output. On benchmarks, Opus 5.5 posts 66.4% on Terminal-Bench 4.0, up from Opus 5’s 52.3%, and Anthropic says it matches the top score of OpenAI’s GPT-6 Astra on FrontierCode at roughly a fifth of the cost.

Sonnet 5.5, launched September 28, is the medium model built for everyday work: bug fixes, features with written specs, polished documents and slides. It runs more than 30% faster than Sonnet 5, costs up to 30% less for most work, and keeps Sonnet 5’s pricing at $2 per million input and $10 per million output tokens. One reported customer test completed a 680,000-line code migration in less than a day on Opus 5.5, which tells you where the frontier is on long-horizon agent work right now.

The real story is the bundling

Here’s what makes this update interesting beyond the version numbers. Google’s Antigravity has been model-agnostic from the start. It launched in November 2025 offering Claude Sonnet 4.5 and OpenAI’s GPT-OSS alongside Gemini, all billed through a Google account. That strategy just got extended to Anthropic’s current generation instead of the older models Google is now retiring.

Think about the math from a team’s perspective. Pay Anthropic directly and you are billed per token through its API. Pay Google a flat monthly subscription and you get Opus 5.5, Sonnet 5.5, Gemini 3.1 Pro and the open models under one invoice, with usage limits set by Google’s tier rather than Anthropic’s meter. For teams already inside Google Workspace or Google Cloud, there is an obvious gravitational pull to let Antigravity be the place where model comparison happens, instead of juggling three separate subscriptions.

And comparison is the operative word. Putting Anthropic’s models in the same dropdown as Gemini means every developer in Antigravity can run a live head-to-head every time they open a new session. That’s a confident move by Google. It says the company believes its orchestration layer, not any single model, is the product. A coding platform that locks a team into one model family builds a moat out of inconvenience. Google seems to have decided the better moat is the workspace itself.

What it means for working developers

The practical upshot is simple: your IDE is becoming the least bad place to answer the hardest question in AI coding right now, which is which model for which task. Opus 5.5 for the ambiguous, multi-file, security-sensitive work. Sonnet 5.5 for the well-specified everyday grind. Gemini for the massive codebases where a million-token context window pays rent. Having all three one click apart, on one bill, lowers the friction of picking right.

That matters because the coding-assistant market has spent 2026 fragmenting. Every model vendor wants you in its own environment, its own API, its own pricing scheme. The open-source inference world is moving the other way, with new platforms like Prime Intellect’s inference service letting teams serve frontier open models on their own GPUs. Antigravity sits in the middle: proprietary models, one subscription, no API keys to manage.

There’s also a quiet signal in what Google chose not to do. It could have kept the newest Anthropic models out of Antigravity to steer users toward Gemini. It didn’t. Google’s own frontier model, Gemini 4 Argon, launched just this week with a million-token window, so the company clearly isn’t short on models to promote. Adding Claude 5.5 anyway reads as a bet that developers stay for the workflow, not the logo on the model.

Who benefits most

Small teams and indie developers gain the most here. The flat subscription turns unpredictable per-token API spend into a known monthly cost, which is the difference between budgeting for AI coding help and hoping for the best. Startups that already run on Google Cloud can now route their agent-assisted development through infrastructure they already pay for, with the billing line item sitting next to their cloud bill instead of in a separate tab.

Enterprise teams get something subtler: a sanctioned place to compare models without a procurement process for each one. When Anthropic, Google and OpenAI all live behind one Google invoice, the security review covers the platform once instead of three times. That’s the kind of boring administrative win that actually decides which tools get adopted inside large companies.

The November 2 deadline is the actionable part

If you are reading this as someone who ships code with Antigravity, the thing to do this week is check which models your agents are pinned to. Anything on Claude 4.6 or GPT-OSS-120B needs a plan before November 2, and the 5.5 family is different enough in speed and cost that your prompts may behave differently under it. Run the comparison while both generations are still live in the dropdown. That’s the whole point of having them there.

Google turned its IDE into a model showroom without most people noticing. The dropdown is the feature. Use it like one.

Prince Mario-Max Schaumburg-Lippe: OpenAI and Synopsys Build AI That Designs Computer Chips

The Flywheel Just Closed Its Loop

On September 30, two companies announced an agreement that could compress the chip industry's most precious resource — time. Synopsys and OpenAI signed an expansive multi-year deal to co-develop GPT-Synopsys, a specialized model trained to be an expert user of Synopsys's EDA (electronic design automation) tools. Not a chatbot that talks about chips. A model that runs semiconductor design workflows, interprets the outputs, and iteratively optimizes designs for power, performance, and area — the PPA triangle every chip engineer lives by — with human engineers setting objectives and signing off on results.

The market noticed. Synopsys shares jumped about 12.78% on the news, closing at $490.54. On the same day, Synopsys also announced a separate $1 billion multi-year agreement with Amazon covering custom chips, AI products, and cloud infrastructure. Two blockbuster chip deals, one Thursday.

Why Verification Is Where the Money Is

Here's the part of the chip business most people underestimate: designing a chip is hard, but verifying it is harder. Modern chips contain billions of transistors, and proving the design works before it goes to fabrication is the industry's true bottleneck — the step that eats schedules and budgets.

That's what makes Synopsys's earlier agent test results so striking. At its Investor Day, the company reported that its agent technologies accelerated chip verification by up to 50× and improved developer productivity by 30%. If GPT-Synopsys delivers anything close to those gains at production scale, the economics of chip development change fundamentally. A design cycle measured in years starts looking like a design cycle measured in months.

The commercial structure backs that up. The deal includes a revenue-sharing arrangement and go-to-market collaboration to bring GPT-Synopsys to customers worldwide. The model runs on OpenAI infrastructure, the companies say customer data stays encrypted and is not used for training, and it integrates with Synopsys.ai plus the new Autopilot agent service. Semiconductor customers are already testing early versions. This reads like a product partnership, not a research press release.

The Same-Day Amazon Deal Says This Is Real

Timing matters. The $1 billion Amazon agreement landed the same day as the OpenAI announcement, and Synopsys raised its fiscal 2027 guidance alongside it: revenue of $11 to $11.2 billion (against a fiscal 2026 midpoint of $9.715 billion), with non-GAAP EPS guidance of $19.04–19.12 (versus $15.07 expected for the current year). Wall Street raised the numbers because it saw two things: a model partnership that could reshape how chips get built, and a hyperscaler willing to pay a billion dollars for custom silicon now.

That second part is the tell. Hyperscalers are pouring capital into custom AI infrastructure — Japan's 400MW AI data center project is one more datapoint in the same trend, and the industry keeps hunting for ways to get more compute from the same power envelope. Custom chips are how you win that race, and custom chips take too long to design. Anything that shortens the cycle has a line of buyers.

The Most Important Loop in AI

Step back and the structure of this deal is beautiful in its symmetry. OpenAI trains the biggest models. Synopsys owns the software that designs the chips those models run on. A model that operates EDA tools expertly creates a flywheel: better AI designs better chips, better chips train better AI, and the loop spins faster each turn.

There's an obvious question — can a model really operate professional EDA workflows reliably enough for production silicon? Engineers signing off on results is doing a lot of work in the announcement. But semiconductor customers testing early versions is a stronger signal than any press release, and the verification gains are already measured rather than promised.

What an Expert-User Model Actually Does

It's worth unpacking what "expert user of EDA tools" means in practice, because the PPA acronym does a lot of quiet work. Every chip is a three-way compromise: power (how much energy it burns), performance (how fast it runs), area (how much silicon it occupies). Push one and the other two push back. Engineers spend careers navigating that tradeoff across thousands of design iterations.

A model that runs those workflows itself — interpreting tool outputs, adjusting parameters, iterating toward the objectives engineers set — is effectively doing the most time-consuming part of the job: the loop. The engineer's role shifts from operating the tools to defining the targets and judging the results. That's the agentic AI pattern playing out in the highest-stakes engineering discipline there is, and it explains why Synopsys framed the Autopilot agent service as part of the same announcement. The destination isn't an AI that suggests chip designs. It's an AI that runs the design loop while engineers supervise.

This is the kind of deal that looks obvious in retrospect. The AI industry spent years arguing about whether agents could do real work. The answer is arriving not in a demo, but in a guidance raise.

The Takeaway

AI designing the chips that run AI is the industry's most important flywheel. GPT-Synopsys targets the true bottleneck — verification — and the market's 13% response says investors believe the loop is real. The next generation of chips may be designed, in part, by the current one.

Prince Mario-Max Schaumburg-Lippe: AI Search Up 200%: Shoppers Now Start Trips in AI Chat

Remember the last time you started a shopping trip by opening a search engine and typing “best running shoes under $150”? That habit is fading fast. A lot of shoppers now open an AI chat first and just talk it through: “I need shoes for marathon training, wide fit, under $150, and I have flat feet.” The results feel closer to what they’d actually buy, and they got there with one question instead of twenty tabs.

Salesforce put hard numbers on that shift this morning. The fourth edition of its State of Commerce report, released September 30, found that agentic search (using an AI assistant as the first step of the shopping journey) grew 200% year over year. It’s a big sample, too: 3,450 commerce professionals (100 of them in Singapore), a consumer survey of 4,690 people, and behavioral data from more than 1.5 billion global shoppers.

The message from retailers? Expectations keep climbing. Eighty-six percent of commerce leaders say AI is raising customer expectations, and 41% say meeting them is harder than ever. Shoppers have tasted what a good AI concierge feels like, and they want it everywhere.

Consumers Moved First; Retailers Are Scrambling to Follow

Here’s the gap that defines this whole story. Only 28% of commerce organizations actually use agentic AI today. But another 52% plan to adopt within six months. Consumers have already changed their behavior; most retailers are still building the thing that serves it.

That’s a classic adoption lag, and it explains why this moment feels so charged. The shoppers are already in the chat. The stores are still figuring out how to be there.

In Asia-Pacific the picture is a little further along. Only 5% of adopters in APAC are still piloting; the largest share, 35%, are prioritizing scaling agentic AI across functions. Scaling, not experimenting. That’s worth noticing: it suggests the experimentation phase is quietly over in the region’s more aggressive markets, and the build-out phase has begun.

Why the Chat Became the Storefront

Think about what a search bar asks of you. Keywords. Filters. Sorting. Page after page of near-identical listings. An AI chat flips the relationship: you describe what you want in plain language, and it does the hunting.

This matters beyond convenience. A conversation is a richer signal than a keyword. When a shopper says “I want a gift for my dad who’s just getting into gardening and hates fiddly tools,” an agent can weigh intent, budget, and taste in a way that “gardening gifts men” never could. The winners in this shift won’t be the retailers with the most SKUs; they’ll be the ones whose AI actually understands what “not fiddly” means.

There’s a real succession happening here. The search bar was the front door of online shopping for twenty years. The chat window is applying for the job, and the +200% number is its résumé. Retail SEO as we know it (keywords, snippets, ranking for “best wireless earbuds”) is giving way to something new: making sure an AI assistant recommends you when a shopper asks.

What This Means If You Sell Things

Three practical takeaways from the report:

Your homepage might be a conversation now. If agentic search is the first step of the journey, the thing a shopper meets first may be an LLM interface, not your website. Retailers need to make their product catalogs legible to AI agents: clean product data, honest availability, prices an agent can trust. The store that feeds the chat well wins the sale.

Personalization is the expectation, not the feature. Eighty-six percent of leaders say AI is raising the bar, and customers can feel the difference between a generic chatbot and one that remembers their size, their budget, their last purchase. Investing in the data behind the chat matters more than the chat itself.

Start where your customers already are. The 52% planning adoption should take heart: the biggest risk isn’t moving too early, it’s the gap between consumer behavior and merchant readiness. Shoppers aren’t waiting for permission.

The broader tech backdrop makes this feel inevitable. AI is quietly rewiring how machines do physical and digital work alike: autonomous trucking routes are being planned by algorithms, robotaxis are multiplying across Texas. Agentic commerce is the same wave hitting the checkout button.

The Optimist’s Take

Strip away the jargon and this is a consumer-benefit story. Less friction. Fewer dead-end searches. Recommendations that understand context instead of just matching keywords. A shopper with specific needs, dietary restrictions, accessibility requirements, a tight budget, gets a personal shopper for free, one that never gets tired and never judges.

Is the technology perfect? Of course not. Agents still hallucinate prices and botch availability, and retailers will have a rough year learning to feed them clean data. But the direction is unmistakable. Two hundred percent growth doesn’t lie: the chat is the new front door of shopping, and it’s open.