Previously, Sidekick only picked up extensions that declared tools. Now extensions that declare only intents are eligible too. However, extensions_summary is missing, the next deploy will fail validation.
admin.app.intent.link / admin.app.intent.render extensions that registered only intents were excluded, so Sidekick did not suggest the app.
The already-declared [[extensions.targeting.intents]] block alone makes it eligible. The configuration format itself hasn't changed.
admin.app.intent.link and admin.app.intent.render .[[extensions.targeting.intents]] the same block. No new syntax needed.
At least one extension declares intents without tools. It becomes eligible for Sidekick immediately.shopify.app.toml without extensions_summary will make your next deploy fail with a validation error naming that field.
Already eligible, and extensions_summary was already required. Nothing changes.
Apps without Sidekick extensions are unaffected.
| Item | Before | After |
|---|---|---|
| Sidekick eligibility requirement | tools required | Either tools or intents |
| Intents-only extensions | Skipped, not suggested | Immediately eligible for suggestions |
| Configuration format | [[extensions.targeting.intents]] |
No change (the same block is sufficient) |
| extensions_summary | Required only for apps that declare tools | Required even with intents only deploy fails without it |
| Scope | — | All apps and all stores. Independent of API version; no opt-in required |
Most apps need no changes. Only if you have an intents-only extension, do the following before your next deploy.
In each shopify.extension.toml , look for intent.link / intent.render entries that have a [[extensions.targeting.intents]] but no tools file.
If any match, check inshopify.app.toml , under [sidekick] , for extensions_summary . If it's missing, add it.
Against a development store, run shopify app deploy .
Ask Sidekick a question that matches your registered intent and check whether your app is suggested.
Example of shopify.app.toml shown in the article:
shopify.extension.toml , but the app-wide shopify.app.toml , in the [sidekick] section. For details on how to write the text, see the related doc "Add an extensions summary to your app" (not covered in this article).Only the eligibility logic changed; the configuration format did not. intents declarations written for app actions now qualify an app for Sidekick as-is.
Intents only +extensions_summary missing: your next shopify app deploy fails with a validation error naming the missing field. If you deploy automatically via CI/CD, fix this beforehand.
It isn't tied to an API version and has no feature preview or scope conditions. It applies to all stores at once, so the answer to "when will this affect me?" is "your next deploy."
Intents-only extensions become visible to Sidekick immediately. To be safe, check on a development store how your app appears in suggestions before this matters.
admin.app.intent.link or admin.app.intent.render target that has [[extensions.targeting.intents]] , andwith no tools file alongside itare affected. For apps with multiple extensions, check each shopify.extension.toml one by one.
shopify.app.toml add [sidekick] of extensions_summary ahead of time.admin.app.intent.link / admin.app.intent.render) and extensions_summary .extensions_summary wording are what Sidekick uses to decide which questions should surface your app. How suggestion accuracy and ranking work isn't documented.extensions_summary (e.g., searching and analyzing reviews).extensions_summary ."