Solutions Channels Your web appYour iOS appYour Android appYour Flutter appWhatsAppInstagram Use cases BookingsOrdersSupportOnboardingAll guides →
Resources Learn DocsGuidesConnect Claude CodeContinuous improvement Compare Lovable appsChoosing how to build your app’s agentGlossaryChangelog
PricingSecurity
Log in

Changelog

What changed in Vatio, week by week. The CLI and the platform are released together, so one entry covers both. Follow it with the RSS feed, or read every entry on one page in the docs.

Replies never invent a price

October 19–25, 2026 · Every agent now checks the amounts of money in its replies against what your tools and prompt said. API keys became one concept, quiet hours let you choose when the agent stays silent, and a few surfaces were removed so the CLI and the MCP are the way in.

  • No invented amounts: a price in a reply must come from a tool, your instructions or a quote that adds up from them, or the agent says it is not confirmed.
  • Two kinds of API keys, publishable and secret, on one page in the inbox and under vatio keys; secret keys now say live or preview.
  • Quiet hours: a weekly schedule in which the agent stays silent on every channel, set in the inbox or with vatio quiet-hours.
  • Tools can send photos on WhatsApp and take the files a visitor sent, and failed WhatsApp sends are retried a bounded number of times.
  • Export and erase a person from the CLI or the MCP, and safer sign-in: inviting people and minting server keys need two-step verification.

Build and run your agent from a chat

October 12–18, 2026 · Vatio is now an MCP server: add vatio.ai/mcp to Claude or ChatGPT and work on your agent from a chat. The way in is still two lines in your app's project, and reported replies now double as a test suite you replay on every version.

  • Vatio in Claude and ChatGPT: add https://vatio.ai/mcp, sign in, and create, edit, test and publish your agent from a chat.
  • Reported replies become tests: vatio flags add reports a reply from the terminal, vatio test add keeps one that is already right, and vatio test replays them all on every version.
  • A Flutter SDK, and a guide to the AI agent runtime that follows one message from your customer to the reply.
  • vatio pull brings the agent Vatio runs back into your files, and vatio push no longer overwrites edits made outside them.
  • A new agent's live follows preview until someone outside your team talks to it, so there is nothing to publish at first.
  • The inbox got simpler: knowledge is read-only there, Test shows the next version only when there is one, and vatio.ai now has a Spanish landing at vatio.ai/es.

October 5–11, 2026

Vatio 0.62.1, 0.63.0, 0.64.0, 0.65.0, 0.66.0, 0.67.0, 0.68.0, 0.69.0, 0.70.0, 0.71.0, 0.72.0, 0.73.0, 0.75.0, 0.76.0, 0.77.0, 0.78.0 and 0.79.0

  • The console is part of the inbox now.
  • The CLI names the inbox's sections.
  • Skills 1.11.0.
  • A routine is a tool the agent decides to use.
  • The agent can answer only some numbers on your WhatsApp number.
  • Live
  • A routine's token is checked when you save it.
  • A WhatsApp message can start a Claude Code routine.
  • A server key reads a conversation:
  • vatio share-session leaves out the people a session is about.
  • A shared session is deleted 30 days after it arrives.
  • vatio share-session --list marks the sessions already sent
  • vatio flags and vatio eval say when the Vatio skills are out of date.
  • Skills 1.7.0.
  • vatio flags and vatio eval say when the Vatio skills are missing.
  • The inbox's Continuous improvement page is simpler.
  • One loop: your coding agent fixes, Vatio verifies.
  • vatio publish checks preview first.
  • vatio push does not overwrite an unpublished push from another branch.
  • vatio logout revokes the token.
  • CLI tokens expire after 90 days without use.
  • Two-step verification.
  • base_url keeps its path.
  • A reply makes at most 12 tool calls.
  • A failing tool's own words reach the agent.
  • Start by installing the skills.
  • vatio-new is now vatio-init, and it looks first.
  • vatio share-session: send the Vatio team your Claude Code session.
  • Tool metrics for your coding agent.
  • Tools
  • The last hour.
  • Publish through your tests.
  • A failing case is retried.
  • Test values for secrets.
  • The docs live at [vatio.ai/docs](https://vatio.ai/docs/).
  • The widget is on npm, and open source.
  • The skills are on npm.
  • vatio propose: a fix the owner accepts from the inbox, without GitHub.
  • Ask for an improvement, from the inbox.
  • vatio whatsapp and vatio instagram link to a page you can see.
  • Integrations

September 28 – October 4, 2026

Vatio 0.48.0, 0.48.1, 0.49.0, 0.50.0, 0.51.0, 0.52.0, 0.53.0, 0.54.0, 0.54.1, 0.55.0, 0.56.0, 0.57.0, 0.58.0, 0.58.1, 0.59.0, 0.60.0, 0.61.0 and 0.62.0

  • Sign in with Supabase, with no code.
  • Send WhatsApp messages from your backend.
  • Server keys.
  • New commands.
  • Signing in works when a coding agent runs the CLI.
  • Test
  • The hosted pages at vatio.ai/w/ are gone.
  • vatio feedback.
  • Errors say what to do next.
  • Telemetry.
  • A flag's note is what should have happened.
  • The judge sees tool calls.
  • Analytics and Learning in the inbox.
  • The brand belongs to the business too.
  • The business and its hours belong to whoever runs it.
  • Business
  • hours: is ignored in vatio.yml.
  • One agent per workspace.
  • vatio issue is gone; report on GitHub.
  • A smaller CLI.
  • Flagged replies become work your coding agent can do.
  • Source and issues are public.
  • Every git branch is an environment of its own.
  • Knowledge changes belong to an environment, and go live with it.
  • A deployment is a snapshot of the whole agent.
  • The workspace's brand is edited in the console, not in vatio.yml.
  • Brand
  • Allowed origins belong to each publishable token.
  • With GitHub connected, live changes only by merging.
  • Every GitHub deploy shows on its commit.
  • vatio publish without GitHub prints a notice.
  • Knowledge has a draft, a live version, and history.
  • Supervisors can edit knowledge from the inbox.
  • vatio secrets set KEY asks for the value.
  • The CLI tells you when a new release is out.
  • The identity token can enrich the inbox.
  • vatio update now points to the correct npm package.
  • A bare vatio publish promotes your latest push.
  • vatio chat show CHAT_ID reads any chat in the workspace.

September 21–27, 2026

Vatio 0.33.0, 0.34.0, 0.35.0, 0.36.0, 0.37.0, 0.37.1, 0.37.2, 0.38.0, 0.39.0, 0.40.0, 0.41.0, 0.41.1, 0.42.0, 0.43.0, 0.44.0, 0.45.0, 0.46.0, 0.47.0 and 0.47.1

  • init no longer asks for an account, and push asks by email.
  • The console opens as your agent exists.
  • The docs are their own site: [docs.vatio.ai](https://docs.vatio.ai).
  • vatio issue sends the workspace, not just the sentence.
  • vatio issue list shows your issues.
  • vatio kb create takes several names.
  • Docs:
  • A workspace can run several agents, and the manifest says which one answers.
  • knowledge: and links: move onto the agent.
  • A tool is one HTTP call to your backend. JavaScript tools are gone.
  • Authentication is one JWT you sign, on every channel.
  • Signing in no longer costs you the conversation.
  • Breaking.
  • A knowledge base holds entries, and an entry is Markdown.
  • A site is one URL.
  • Same actions everywhere.
  • One API, one view, and environment said out loud.
  • view is gone from the chat endpoints.
  • environment is required on POST /chats and POST /chats/:id/reset.
  • The SDK is on npm, and the widget is the only thing you paste into a page.
  • The inbox is a page in Vatio, and there is no credential anywhere near it.
  • Building a supervisor UI inside your own product is not supported for now.
  • The package is @vatio-ai/cli.
  • vatio whatsapp connect opens the browser too.
  • vatio whatsapp connect prints a link, and pasted credentials are gone.
  • The CLI is an npm package now.
  • Why:
  • What carries over:
  • A chat is you, and vatio chat can talk to live.
  • A chat against live is a real conversation.
  • One flag picks the deployment: --env.
  • The CLI stopped parsing your workspace; Vatio does it.

September 14–20, 2026

Vatio 0.27.0, 0.28.0, 0.29.0, 0.30.0, 0.31.0 and 0.32.0

  • vatio.yml owns the whole widget, and the snippet drops to two attributes.
  • A key widget: does not recognise fails the push.
  • A source name belongs to one kind of source, permanently.
  • A batch upload is all-or-nothing.
  • vatio issue --template is prompts now, not a form.
  • The mail around an issue says less, and the thread says it instead.
  • An issue is now a conversation, and it lives in the CLI.
  • links: now survives a push.
  • An unknown key in vatio.yml is now an error.
  • vatio update says what it is about to install.
  • links: — the URLs your agent is allowed to share.