June 2026 Summaries

Linq now enables developers to create iMessage Apps, interactive cards that run directly within Messages conversations and let users complete activities such as gaming, dating, payments, ticketing, booking, and media playback without leaving a chat. These cards are sent through an `imessage_app` message part and rendered by an installed Messages extension identified by its Apple team and bundle IDs, while a supplied URL provides the content and behavior of the in-thread experience. Developers control text captions on cards, but the extension renders images and interactive UI; recipients without the app instead see fallback captions and potentially an App Store prompt. Cards can be updated in place for changing states such as game scores or confirmed bookings, although updates require a delivered message, preserve the original app identity, and create a new message ID for later updates. The feature is limited to iMessage, cannot be combined with other message parts or SMS/RCS fallback, and may fail asynchronously for recipients who are not reachable via iMessage, making capability checks and webhook handling important.

Group chats are presented as a primary product surface for social, coordination, concierge, commerce, and community agents rather than merely expanded one-to-one conversations, because they allow agents to introduce participants, organize logistics, manage planning tasks, and step back while people interact. Linq’s Partner v3 API supports iMessage and RCS group chats with creation through multi-recipient messages, group display names and icons, participant management for iMessage groups, and webhooks for chat and membership changes, though initial messages cannot contain links, recipient limits vary by delivery channel, groups must retain at least three members, and group chats lack typing, delivery, and read receipts. The central engineering challenge is determining when an agent should participate, since replying to every message can be disruptive while inconsistent silence damages trust. Linq recommends separating this decision from response generation through a two-stage architecture: a small, inexpensive classifier evaluates each group message as respond, react, or ignore, while a more capable model generates content only after the classifier selects a response or reaction. This routing approach can reduce cost and latency, improve consistency, prevent reaction loops, and allow teams to independently tune participation behavior. Effective group agents also need sender-attributed conversation history and group-specific prompting so they can recognize who is speaking, address participants appropriately, keep replies brief, and account for the visibility of every response.

Linq has become an official vendor adapter for Vercel’s open-source Chat SDK, enabling developers to add iMessage, RCS, and SMS to bots and AI agents built with the same platform-agnostic API used for services such as Slack, Discord, Teams, WhatsApp, and Telegram. The Apache-2.0-licensed `@linqapp/chat-sdk-adapter` integrates Linq’s carrier infrastructure with Chat SDK’s event-driven framework and Vercel AI SDK features, supporting normalized iMessage tapback reactions, inbound media attachments, outbound files up to 100 MB, stable conversation thread IDs, and HMAC-SHA256 webhook verification with replay protection. Developers can install the adapter, configure it with a Linq API key and webhook secret, route incoming webhooks through their application, and use the Linq CLI to provision a sandbox number for local testing. The integration allows existing bot logic to operate across multiple messaging platforms without platform-specific branching and was accelerated by community contributor Fardeem Munir.