What's New¶
Product updates to Anychat, newest first. Each entry links to the guide or reference page with the full details.
August 19, 2026 — Media library: rich cards and carousels from your own pictures¶
Every agent has a media library: the pictures
(and, as rich channels allow, videos) it may show in rich cards,
swipeable carousels and media messages. Upload files or add by URL at
Settings · Media; each item gets a stable id, a name and a usage hint
for people, and a description written by a vision model for the agent.
Message templates and playbooks refer to items by id (media:
image:<id>), so a menu-as-a-carousel or a "here's what we do" showcase
early in the conversation is plain authored copy. Drop a new file on an
item to update the picture everywhere it is used; removing an item
deletes the hosted file, and any message that still mentions it sends
without the picture. In AML: [[carousel]] (one
card per line) and card buttons (link: / reply: / dial:). Also in
the Agent API and the
Anychat MCP server 0.6.0 (list_media,
add_media, update_media, replace_media_content, describe_media,
delete_media).
August 18, 2026 — Framework v2 preview: capability manifests, deterministic paths, turn traces¶
A new agent runtime is available as an opt-in preview. It reads the
same Definition you already author, but with fewer moving parts: the
model sees exactly what you wrote (nothing injected behind your back),
each playbook declares the capabilities it uses,
a playbook can carry a deterministic path
(a Flow — generated from the playbook text, then edited) for the parts
that must not vary, and every turn leaves a
trace you can open from the Messages
page to see which playbook, tools and rules were in play. A
Definition lint on the Overview
points out gaps with one-click fixes, and works on every agent, v1 or v2.
Orgs in the preview see Switch to v2 preview on an agent's Overview;
switching back is one click and changes nothing else. Also in the
Agent API and the
Anychat MCP server 0.4.0 (lint_agent,
list_turns, generate_playbook_flow, update_agent framework).
The agent framework (v2 preview)
August 17, 2026 — Copilot: files, memory, and the command line¶
Anychat Copilot can now work with files: upload a
CSV or notes to a chat's Files strip (or drop them on the panel), let
Copilot read them, and download whatever it writes back — reports,
cleaned-up lists, exports. It also keeps short notes about your
preferences ("What Copilot remembers about me…" in the sessions menu, with
a one-click Forget everything), confirms only what the console actually
did when it opens a page for you, and shows a field-by-field diff even for
whole-document changes such as importing a definition or applying a
template update. And it's in the CLI: anychat copilot for an interactive
session, anychat copilot ask "…" for one-shot questions.
August 16, 2026 — Agent API: manage testers via /v1¶
Inviting people to try an agent in the tester app before it launches no
longer needs the console. The new
Testers resource lists an agent's
testers, invites one by email (the response carries their one-time
sign-in link for you to share), disables or re-enables them,
regenerates a lost link, and removes them: the same actions as
Settings · Testers, with the same guarantees (a link is returned
once, on invite or regenerate, and never on list). The
Anychat MCP server 0.3.3 adds the matching
tools (list_testers, invite_tester, set_tester_disabled,
regenerate_tester_link, remove_tester), so "invite jane@example.com
to test the medspa agent" works from Claude Code or Cursor too.
August 16, 2026 — Agent API: configure scheduling, People fields, products and custom tools; send outreach¶
Four capabilities that you could previously configure only in the
console, or by round-tripping a whole export document, are now their own
resources in the Agent API: the
Scheduling configuration
(hours, reminders, representatives), your
People fields, the
product catalog, and the
contracts of your custom integrations.
Each is a plain GET / PUT (custom tools also get per-tool PUT and
DELETE), returns exactly what an export shows for that slice, and
reports validation problems by field path. And the People page's Send
and Follow up buttons have an API equivalent:
POST .../people/{personId}/outreach
opens the outreach conversation (with an optional per-send Playbook or
greeting), and .../outreach/follow-up sends a nudge now, with the same
checks and outcomes as the console. Playbook POST and PUT also carry
procedures now, so a full-playbook save keeps its procedures.
Anychat Copilot can carry these steps out without handing you off to a console page, and the Anychat MCP server 0.3.0 exposes them as tools, so "add a representative", "declare a budget field", or "send outreach to Jane" work from Claude Code or Cursor as well.
August 16, 2026 — Copilot: see exactly what will change, stop a turn, guided jobs¶
Approval cards in Anychat Copilot now show a field-by-field diff of what an edit will change (current value → new value) before you approve. A Stop button (or Escape) ends a turn mid-way and withdraws any pending change. And Copilot has built-in procedures for common jobs — setting up a channel, configuring outreach, diagnosing a conversation, reviewing an agent against best practice, creating an agent from a website — so "Set up WhatsApp for this agent" walks the whole job with you, one approval at a time.
August 15, 2026 — Meet Anychat Copilot, your assistant inside the console¶
Anychat Copilot is a new panel in the console (the sparkle button in the header, or ⌘J / Ctrl+J) that knows the docs, your workspace, and the page you're on. Ask it how scheduling handles same-day bookings and what this agent is set to; ask which agents have no channel connected; or ask it to add a pricing playbook to the agent you're editing. Reads happen on the spot. Anything that changes your agent arrives as an approval card first, with the exact change one click away, and deleting or provisioning always asks. It can open pages for you and refreshes what you're looking at after a change. Copilot acts with your own permissions and is enabled per workspace; ask your Anychat contact to turn it on.
August 15, 2026 — Template updates become one reviewed merge¶
When the template your agent was created from publishes a new version, you now review the whole update in one place instead of piece by piece. The agent's Definition page shows a quiet "new version available" note; opening it lists every difference between your agent and the new template — changes the template made, changes you made, and the few places where both changed — and you decide, item by item, whether to take the template's version or keep yours. Nothing changes until you apply, and your own additions are never touched. The per-piece update pills and the Settings · Updates page are retired.
Template updates in the Agent API
August 15, 2026 — Drive Anychat from Claude Code, Claude Desktop, or Cursor¶
Your own AI agent can now operate your Anychat workspace. The new
@anychat-ai/mcp server connects any MCP host (Claude Code, Claude
Desktop, Cursor, and others) to your account with an API key, so you can
ask it to review an agent's guardrails, add a Playbook, set up a WhatsApp
channel, or dig through yesterday's conversations, in plain language,
from the tool you already work in. It reads and writes through the same
Agent API the console uses, with your key's scopes; anything that changes
your agent asks for your approval first, and it can consult these docs on
its own before acting.
Use Anychat from Claude Code, Claude Desktop & Cursor
August 15, 2026 — A sharper Sales Development template, and an honest agent preview¶
New agents created from the Sales Development Agent template now start with a tighter, industry-neutral setup: three ranked objectives instead of six (book the call, understand the lead, answer product questions — greeting and confirmation live in the Playbooks where they belong), guardrails and lead fields that fit any business rather than one vertical, and a discovery Playbook that adapts to whether the customer messaged first or your agent reached out. Existing agents are unchanged — as always, template updates only apply when you choose them on Settings · Updates.
The agent Chat Preview now says what it's simulating. A new Outreach / Inbound toggle lets you watch both kinds of conversation start — the outreach opening with sample (or real) lead intake, or a visitor messaging first — with a caption naming the active scenario. And when you Build Agent from a concept, the concept's opening line only becomes your outreach greeting when the concept actually demonstrates outreach; inbound demo openers no longer leak into outreach conversations.
August 13, 2026 — Your branding on concept pages, with a whitelabel add-on¶
Concept pages you publish can now carry your brand by default. The new Workspace · Branding page holds your company name, brand color, logo, favicon, and footer; every concept you generate picks them up, and publishing fills any gaps a concept left blank. Already-published pages list right on the Branding page with a one-click Republish to apply a change everywhere. With the new whitelabel add-on, Anychat attribution disappears from your published pages entirely — your favicon, your footer, your brand only — so the demo you send a prospect reads as yours.
August 10, 2026 — Pick the Playbook for each outreach send, and preview the exact message¶
The Send outreach dialog now decides the whole conversation, not only the greeting. Pick the Playbook the conversation follows (confirm an appointment, qualify and book a call, whatever the moment calls for), and the dialog renders the exact opening message against the recipient's real record before you send, so you can sanity-check what is going out. A template that cannot render for this person disables sending instead of surprising you. On Settings · Playbooks you can now mark any Playbook available for outreach and attach its own opening message; outreach Playbooks stay out of regular conversations unless you choose otherwise.
August 9, 2026 — Claude Sonnet 5 and Claude Opus 5 in the Model picker¶
Settings · Model now offers Claude Sonnet 5 and Claude Opus 5
alongside the existing options, so you can move an agent to the newest
models with one selection. The page and the agent header now show the
model your agent actually runs, including agents that predate the
picker, and newly created agents start on the platform default (Claude
Sonnet 4.6) until you choose otherwise. Your selection is saved in the
agent's llm block and travels with export and
import.
August 9, 2026 — Playbooks carry their procedures¶
A Playbook now owns its step-by-step instruction blocks — its procedures — instead of referencing them from a separate Skills library. Everything about one situation lives in one place: open a Playbook and its exact mechanics (like the full call-booking procedure) are right there, editable inline, with catalog lineage per procedure. Existing agents were converted with a per-agent verification that the instructions the model receives are byte-for-byte identical, so live behavior is unchanged. The Settings · Skills page retires; its route lands on Playbooks.
August 9, 2026 — Capabilities: what your agent can do, in one place¶
The console's new Capabilities page shows everything your agent can
do beyond conversing — scheduling, knowledge, people memory, outreach,
notifications, custom integrations — as one roster, each card
describing the ability in plain terms with its configuration status and
links. Representatives now sit with Scheduling, where they belong:
they're who the booked calls are with, and the page tells you when none
are configured. Custom HTTP abilities are now called Custom
integrations. The exported agent file was reorganized to match — a
definition layer (what you author) and a capabilities layer (what
you configure) — and the Capabilities
concept page joins The Agent Definition in the docs.
August 8, 2026 — Your agent as one document: the Definition view¶
An agent is defined by a single document, and the console now shows it that way. The new Definition page presents everything you've authored — identity, personality, guardrails, objectives, playbooks, tools, knowledge, content, people — as one outline-navigable view, with each section marked by when it applies (every turn, the active Playbook, or on demand) and linked to its editor. The documentation was rebuilt around the same model: The Agent Definition walks the document section by section, How a Turn Is Composed shows what the runtime does with it, and seven new authoring guides cover Playbooks, Objectives, Guardrails, Personality, Capabilities, Knowledge & Products, and Message Templates.
August 6, 2026 — Create and publish concepts from the CLI¶
Concept pages can now be managed end-to-end from the anychat CLI:
author a concept as a YAML or JSON document — branding, page copy, and
the scripted conversation flows — then anychat concepts create
--input concept.yaml --publish takes it straight to a live page on
concepts.anychat.ai. List, update, republish, and unpublish work the
same way, so a batch of demo pages can be built and kept in version
control instead of assembled by hand in Concept Studio.
Concepts — From the command line
August 3, 2026 — Filter People, save segments, export the view¶
The People list now filters by tag, source, whether a phone number is on file, and RCS reachability, alongside the existing search and status filter. A combination you use often can be saved as a named segment and reapplied from a picker in one step; segments stay live, matching whoever fits the filter today. Export follows the active filters, so the CSV you download is exactly the list on your screen. The same filters and segments are available through the Agent API.
People — Filtering and segments
July 30, 2026 — Turn off same-day bookings¶
If your team needs lead time before a call, the Scheduling page now has an Allow same-day bookings toggle. Turn it off and the earliest bookable day becomes tomorrow: the agent stops offering today's times and steers anyone asking for "today" to times from tomorrow onward. The cutoff follows your agent's timezone, so a person a few timezones ahead can't book into what is still today for your team.
July 29, 2026 — A Calls page, and calls that don't disappear¶
Your agent now has a Calls page in the sidebar: every call it has ever booked — upcoming, completed, and cancelled — with the person, the rep, and when it was booked. Calls stay on the list after they happen, so a same-day booking you weren't watching for is still there when you check in. The People list keeps the most recent past call visible in its Scheduled Call column too, instead of going blank once the call time passes. Agents also got better at booking in the right timezone: the platform now infers a lead's likely timezone from their phone number so "9 AM" means 9 AM where they are.
Scheduling — Where calls show up
July 22, 2026 — Bigger phones on concept pages¶
Published concept pages now give the phone nearly the full height of the browser window, so the demo reads clearly across a desk or on a projector. A new Phone size control in the concept editor adjusts it per concept, from 0.85× to 1.3× of the phone's natural size; every page still scales down to fit small screens. Already-published pages pick up the roomier layout automatically.
July 21, 2026 — People: search, export, and a scalable list¶
The People page now searches by name, email, phone, or company, filters by funnel status, and loads large lists incrementally. An Export button downloads the whole CRM as a spreadsheet-ready CSV whose columns match the import template, so a round trip through your own tools is straightforward.
July 21, 2026 — Smarter imports and duplicate merging¶
Re-importing an updated list now updates matched records instead of skipping them: choose fill empty fields only (the default) or update matched records at import time. Possible duplicates are flagged as records arrive, and a side-by-side merge dialog lets you combine a pair field by field, or mark them "not duplicates" for good.
July 21, 2026 — Provenance, field locks, and tags on People¶
Every People field now shows who set its current value (your team, an import, or the agent) and when. Contact details the agent learned in conversation read as unverified until a person on your team confirms them, and any field can be locked so the agent can never change it. Records also carry free-form tags, editable by your team and addable by the agent.
July 20, 2026 — Choose a concept's playback speed¶
Concepts can now play at the pace you choose — from 0.5× for an audience reading along to 2× for a quick teaser. Pick the speed in the concept editor and it applies everywhere the concept plays: the live preview, the published page, and exported videos.
July 16, 2026 — One-tap replies on call reminders¶
Pre-call reminders now offer three quick replies — Confirm, Cancel, and Reschedule — so the person can act the moment the reminder lands. Cancel double-checks before cancelling; Reschedule offers new times right away. On channels without tappable replies, typing the same words works just as well.
July 16, 2026 — Export and import agents¶
You can now export an agent as a portable definition file and import it into another agent — or another account — to duplicate a proven setup, move an agent between environments, or keep a versioned backup. Secrets and people data never leave with the file.
July 14, 2026 — Concept videos and branding¶
Concepts picked up two upgrades: export a concept as a video (MP4/MOV) to drop into a pitch deck or send to a stakeholder who won't click a link, and upload a logo to have the concept page match the brand's colours automatically.
July 6, 2026 — Export a conversation history for a call¶
Prepping to call a lead? Open their record on the People page and click Export for call to download a clean, printable summary — their key details, what the agent has learned about them, and the full conversation transcript — so you can walk into the call fully briefed.
July 6, 2026 — Automatic follow-ups¶
Anychat can now automatically follow up with people who don't reply to your initial outreach. Turn it on for an agent — "if no reply after 2 days, send a check-in" — and Anychat sends one follow-up to quiet contacts on schedule and cancels it the moment they respond, so no one who's already talking to the agent gets pestered.
You stay in control: a status chip on the People page shows where each person is, quiet hours keep the follow-up out of the middle of the night, and you can send follow-ups by hand (as many as you like), or pause / resume / stop the automatic one for any person. Follow-ups are RCS-only for now, off until you turn them on, and only ever apply to people you contact after enabling them.
Following up with people who don't reply
June 25, 2026 — Concept Studio¶
Show a prospect what an Anychat agent would feel like for their business — before building anything. Point Concept Studio at a website and it generates a polished, shareable concept page with a scripted agent conversation playing in a channel emulator; refine it, publish it at its own link, and when the prospect says yes, turn the concept into a real agent.
June 10, 2026 — WhatsApp conversational messaging¶
Agents can now hold two-way conversations on WhatsApp through the Meta Cloud API, alongside RCS, Apple Messages for Business, and SMS — so you can meet customers on the channel they already use.