Skip to content
Changelog9 min read

Shopify agents, group chats, and staged rollouts

New on Keiki, November 9–19: Shopify agents, iMessage group chats, staged rollouts, calls on your texting number, and MCP clients that answer customers.

Terraced marble citadel on a sea cliff at night, its temples lit warm amber under a deep blue starry sky above white roses

This update covers November 9–19, following our November 9 Changelog. First, the changes you can use from the dashboard. Then, the tools for developers building on Keiki.

What's new

Two agents for your Shopify store

Keiki now has a Shopify app. Installing it connects your store and sets up Sales and Customer Service agents. They can use your products, policies and store information to answer shoppers, with live tools for questions about orders and availability.

You decide which store actions each tool can take: Allow, Ask for approval, or Deny. Requests that need a person go to the approvals inbox. The storefront chat widget has Off, Test and Live modes, so you can try it in the theme editor before shoppers see it. Plans and credits are billed through Shopify.

The app also has an iMessage page for choosing the store's Sales and Customer Service numbers. The storefront only shows a number while it still routes to the right agent.

Bring your agent into iMessage group chats

Turn on Group chats on your agent to let it take part in supported iMessage groups, including groups on shared numbers. It answers when someone addresses it by name or replies to it, and quietly keeps the rest as context. Follow-ups get a second look so “and tomorrow?” can reach the agent without everyone having to repeat its name.

Replies stay in the group's thread, on the number the group used. Group chats are off by default for new agents, and not every line supports them. Telegram uses the same group-chat behavior. Read about group chats.

On supported iMessage lines, questions with choices can now arrive as native polls in groups as well as private chats. Votes come back to the agent.

Try a change before giving it to everyone

You can now Stage changes to an agent and choose how to Roll out the update. Full updates everyone, Manual starts with the share of conversations you choose, and Auto increases the share while quality holds. Auto can roll back and alert your team if quality drops.

The rollout splits conversations, not individual messages. From Versions, you can change the share, promote the candidate or roll it back. This applies to the agent's prompt, model and other per-turn settings; tools, integrations, skills and lines still change for everyone and need a Full save.

One place to see who is answering

The conversation view now says who is handling the thread, just above the composer. Take over to pause the agent, reply yourself, then hand it back with a note. If the agent is already working, the view says so before you interrupt it.

Peer-agent requests and direct API follow-ups are now visible in the conversation transcript too. Approvals lives inside Logs, next to Activity, so requests waiting for a person and the work that produced them are in one place.

Calls on the number your agent already texts from

Under Channels → Phone calls → Add line, you can now choose Use the agent's iMessage line. Customers call the number they already know; Keiki forwards the call to your agent. Forwarding has its own monthly line cost, shown during setup.

Some lines connect immediately, some need provider setup, and others offer a request for the team to help. Shared numbers can't forward calls. Read about phone calls.

More ways to shop and interact

  • Shopping with a customer's own card. The new opencommerce add-on lets an agent build a cart at supported USD stores and show it to the shopper. The shopper must confirm before checkout, and adds their card through a Vault link, never in chat. Order and platform fees apply. Browse add-ons.
  • Telegram widgets. With Dynamic UI on, an agent can send an interactive HTML widget in a private Telegram chat and update it as the customer interacts. Telegram button presses can also get a private, temporary response. Read about Telegram widgets.
  • Browser sign-ins that last. When you help the agent sign in through its browser handoff, later browser tasks can reuse that sign-in instead of asking you to start again.

Getting started and everyday improvements

  • New accounts can sign up without an invitation by default. Sandbox workspaces let you explore agents and Live Test, with a Request access flow for the rest of the platform.
  • The shared-number onboarding test works without a paid plan while onboarding is open and for a short window afterward, under Live Test limits. Shared-number groups can also switch agents by sending the new join code.
  • Organization members, not just owners and admins, can now install, enable and remove agent add-ons. Viewers remain read-only.
  • Settings → Billing → Manage billing opens subscription management for directly billed workspaces. Shopify workspaces manage billing through Shopify instead.
  • Settings → Secrets is back, and dark mode has clearer fields and buttons on a dark gray canvas.
  • Channels now shows each line's source: Keiki or your connected account, with account problems shown beside it.
  • Quality reviews now consider recorded tool results and distinguish scheduled updates from replies to a new question, so a scheduled task isn't graded as an unsupported promise just because it hasn't finished yet.
  • Supported new iMessage lines turn on read receipts, and saving an agent's contact card also turns on automatic name and photo sharing where supported.
  • Voice notes re-encoded for iMessage now use the right audio filename so they play correctly. Long Telegram replies are split into messages, and temporary send failures are retried.

For developers

Let an MCP client be your agent

An MCP client can now drive a Keiki agent over OAuth, without a separate webhook server. Connect to https://onkeiki.com/api/v1/harness/mcp, sign in, and select or create an agent. The client calls next_message to wait for incoming messages, answers with reply and the agent's tools, then listens again.

A plan-less agent connected this way gets a one-time allowance of five inbound and five outbound shared-line messages. Reconnecting doesn't reset it; a plan lifts the cap. This is a harness connection for answering customers, separate from the administrative MCP connection below.

Code Mode is now the default Keiki MCP server

Connect a coding assistant to https://onkeiki.com/mcp to manage Keiki through search and execute. Search finds the operation; execute runs JavaScript that calls it. The catalog now covers more of the dashboard, including skills, version diffs, eval editing and runs, connected apps, webhooks and domain setup.

You can delegate work to Coder, ask Oracle to investigate organization telemetry, and use Tool Builder to write and test a disabled tool draft before publishing the approved source. Large results can be read later with read_result, and connect_mcp returns the authorization or credential-entry link for a saved connection. check_notifications brings your organization's Keiki announcements into the client. Read the MCP guide.

External harnesses can opt into their own Code Mode switch under Setup → Connect your agent. Non-delivery tools become searchable JavaScript calls; reply and other delivery tools stay direct. The model loop still runs in your app. Read external harness Code Mode.

Make a messaging demo without recording your phone

The new message demo editor turns a scripted conversation into a phone-accurate animation for iMessage, SMS, Apple Messages for Business, WhatsApp or Telegram. Download a video in the aspect ratio you need, or use message-ui from React or the CLI to render the same script.

More control from your own runtime

  • Start an iMessage conversation. The developer API can start a conversation on an eligible dedicated line, rather than requiring an inbound text first. Shared lines and lines that need a recipient reply remain restricted. Read the agent API.
  • Use your own iMessage extension. Configure an agent's card-app identity after verifying its URL domains. App cards can open in your extension; Keiki approval and payment cards still use Vault. Setup is available through Code Mode without an SSO plan. Read the app-card guide.
  • Manage skills as code. Create, update and delete organization skills through the developer API, then attach skill IDs to partner deployments. Read about partner deployments.
  • Use channel-native card layouts. When the shared card catalog isn't enough, send_card can accept native channel JSON after the agent reads the on-demand format guide. message_privately lets a Slack agent send a private message without treating it as the public answer.
  • Channel-neutral tools. Agents use send_widget, user_lookup and reply across channels, with channel-specific options where supported. @onkeiki/channels 0.1.7 and @onkeiki/ai-sdk 0.1.9 include the latest turn-handling fixes.
  • Clearer turn errors. Finished turns return 409 turn_closed, not an authentication error. Unavailable actions and unknown message targets return 400. Attachment sends no longer need the code sandbox, and tool context includes the iMessage group chat ID.

Action needed

If your MCP client caches Keiki's old individual administrative tools, refresh its tool list or reconnect to https://onkeiki.com/mcp. That URL now serves search and execute; clients should discover operations rather than call the old tool list directly.

If your external harness hard-codes channel-named tools, update it to the channel-neutral names above. In particular, app-card sending is now send_widget, and Slack-private replies use reply with ephemeral. Discover the current tool schemas rather than assuming every channel supports every option.

Frequently asked questions

Do I need to turn on group chats?

Yes. Enable Group chats on the agent. New agents have it off, and iMessage groups need a supported line. Private chats are unaffected.

Can I roll out a new integration to only some conversations?

No. Staged rollouts cover per-turn settings such as the prompt and model. Tools, skills, integrations and lines still apply to every conversation.

Is the MCP harness the same as Keiki's administrative MCP server?

No. The harness endpoint lets a client receive messages and answer as one agent. The main /mcp endpoint manages your Keiki workspace through Code Mode.

Published · Changelog