The shopper asking for it might be software.
Browsers now ship an assistant that can act on the page it is looking at. A GemBoss storefront hands it real controls: search the catalog, read a product, change the cart, open checkout. It works on the same cart the shopper can see, and it lands in the same numbers you already read.
Shopify opened this door in August.
On 5 August 2026 Shopify began serving a small script on every storefront it renders, which registers tools with the browser so an in-tab agent can search a catalog and build a cart without scraping the page. That is a confirmation, not a threat. The question it raises for a merchant is narrower: when an agent arrives, what can it actually do on your store?
Ten tools, and no room for an eleventh.
Shopify's script carries a fixed set. We read the version live on merchant storefronts in August 2026: the earlier build could accept one extra tool from a store, and the shipping build dropped that path entirely. A merchant on a Shopify-rendered theme gets that set, and only that set.
A theme gets the list
Catalog, cart, checkout, orders. Useful, identical for every store on the platform, and closed to anything a particular brand needs an agent to understand.
A GemBoss store registers its own
Your storefront is rendered by us, so the tools are declared by us. The five that ship today cover the shopping path. The list is ours to extend, which is the part a shared script cannot offer.
One cart, not two.
The obvious way to bolt this on is to point an agent at a separate commerce endpoint. It works in a demo and fails in real life, because that endpoint keeps its own basket: the agent fills a cart the shopper never sees, and the two disagree at checkout.
Same cart
Every tool goes through the same code path as your buy button, carrying the same session. What the agent adds is what the shopper is holding.
Same screen
Add something through an agent and the cart drawer opens with it. A change nobody can see is not a change worth shipping.
Same checkout
Checkout stays Shopify's, and the shopper still enters payment themselves. An agent can bring them to the door. It does not walk through it.
It shows up in your numbers.
An agent calling a tool touches no button, so nothing about it is visible to analytics unless the tools report it themselves. Ours do. An agent-driven add to cart is an add to cart, and reaching checkout is reaching checkout. Without that, every one of these sessions would read back to you as a visitor who abandoned a full basket.