Suggested replies are now a capability you switch on per version

Quick replies, the tappable suggestions under the assistant's answer, moved from the Chat tools list to the Capabilities list, where they are called Suggested replies.

What changes for you

• The assistant no longer decides to call a tool to offer them. After it finishes its answer, the server makes a separate short call that proposes the chips. If that call fails or takes longer than 6 seconds, the shopper gets the answer with no row.
• Agent versions that had Quick replies on keep them: they now have Suggested replies on.
• A new version starts with Suggested replies off. Before, it started on. Tick it under Capabilities to turn it on.
• Only Shopping assistant agents can use them. A custom agent doesn't list the option, and saving one with it is refused.
• The server no longer reads your product descriptions and policy pages to check that a chip's answer exists there. The other checks stay, for example no "Go to checkout" before something is in the cart.

API and MCP. Agent versions now carry a capabilities list in the REST API (attachment, voice_dictation, quick_replies), and a version can be created with enabledCapabilities. The suggest_replies tool key is no longer accepted in enabledTools: the request fails with 400. The MCP get_agent_version tool prints the capabilities and lists capability changes between two versions. Conversations still return the row as a quick_replies block, including the rows saved before this change.