← Changelog
NewApps

Problems names a missing Shopify scope, and the assistant can ask for it

A synced Shopify model whose scope the app didn't ask for synced nothing and said nothing: shopifyOrder without read_orders stayed empty. Now Problems names the model and the scope, and warns about Admin API mutations in your code whose scope is missing. The assistant and the MCP server have request_scopes, which adds scopes once an admin approves, and POST /v1/apps/:app/shopify/scopes does the same from a script.

Before, scopes could only be changed in Settings → Shopify. An agent that wrote a synced model's schema or a productUpdate call had no way to ask for the scope it needed, and found out only when nothing arrived or Shopify answered ACCESS_DENIED.

request_scopes and the API only add scopes; taking one away stays in Settings, where the models that sync by it are chosen. Adding takes a team owner or admin, or a key with Apps Permissions. Every environment's Shopify app is released with the new scopes, and each installed store approves them the next time the merchant opens the app.

get_problems on the MCP server and in the assistant now answers with everything the console's Problems panel shows, Shopify release problems and settings that don't read included, not only type errors.

More in Shopify scopes in the API.