Changelog

2026-11-01Copy Anchor Link

• Every admin point now shows: panels beside a product, collection, order or customer, a block in the shop's settings, actions in a record's Apps menu, and actions on the rows ticked in the products, orders and customers lists. Those get the ticked ids as context.selection, inside the signed session. The points for customers, and the .detail.action points, are new.
• App Bridge version 2: a handshake that hands your page its context, theme and session at once, then toasts, a loading bar, a title bar, the admin's save bar, modals, confirm, a resource picker, navigation, and links off Storeware the merchant is shown first. createAppBridge in @storeware/plugin-sdk/bridge speaks it. Pages written for version 1 keep working.
• Two packages for React apps: @storeware/app-bridge-react, a provider and hooks over App Bridge, and @storeware/app-ui, components styled only by the admin's 13 --sw-* variables.
• The admin's theme reaches your page as the night colours it actually draws, with scheme set to dark. It said light.

2026-10-28Copy Anchor Link

• An agent's standing: what it did across Storeware shops, counted every night, shown to merchants beside each AI shopper and handed to the agent itself as a signed statement at https://api.storeware.ai/api/agent-standing/self. Merchants can hold orders from agents with no record, or with lost bank claims.
• Every shop answers questions from other AI assistants: Ask, UCP's draft ask capability, served now as ai.storeware.common.ask over UCP REST, UCP MCP, A2A and the shop's own MCP server. It never changes anything, and says so when a question asks it to.
• A REST reference for products, variants, collections, inventory, orders, customers, metafields, webhook deliveries and app billing, read from the OpenAPI document the API now serves at https://api.storeware.ai/api/v1/openapi.json.
• An app's access token lasts 24 hours. These pages said an hour.
• References read from the code: every manifest key, every CLI command, the SDK module by module, the theme schema and the storefront GraphQL API. Point your editor at the manifest's JSON Schema with #:schema https://storeware.ai/docs/schemas/storeware.app.json at the top of storeware.app.toml.
• New guides for AI agents: the MCP servers, how an agent signs in, UCP and ACP, answers, x402 and more. And for themes: the schema, the kit and the embeddable assistant.
• storeware app rollback 3 and storeware webhook trigger order.paid.v1 find the app from the manifest in the current directory. Before, they read the version or topic as the manifest's path.
• Development stores take test payments. Choose how each one ends (approve, decline, a check by the shopper's bank, or an error) and your app receives the same order events a real shop sends. No money moves.
• The guides that lived at storeware.ai/developers now lead to their pages here, and storeware.ai's menus link the docs.
• An app's token can no longer export or erase a customer's data, even with customers:read or customers:write. That is the merchant answering a privacy request, and your app hears about each one by its compliance webhooks. The API answers 403 with privacy_requests_are_for_the_merchant.
• An app can change or delete only the metafield definitions it declared. Changing the merchant's or another app's answers 403 with metafield_definition_not_yours.
• An app's metafield definitions come from [[metafields.definitions]] in its manifest. Creating one through the API answers 403 with apps_declare_metafields_in_the_manifest. Before, it made a field that belonged to the merchant, which your app could not fill in.

2026-10-27Copy Anchor Link

• The developer docs moved to storeware.ai/docs, with search, a Markdown copy of every page, and an llms.txt of their own.
• Apps can charge by use up to a cap the merchant approves, credit a shop, and lower a price for existing subscribers.