Changelog

Stay up to date with what’s new. Subscribe to our newsletter or follow @auterynai for announcements.

September 2026

Agent runs use fewer credits Changed

Credits for agent runs have come down. Each agent action — a step through an Integration or in the sandbox — now costs 0.01 credits instead of 0.25, and context your agent has already seen in the conversation (cached context) bills at about 10% of the normal rate instead of 25%. In practice a quick chat message now costs roughly 5–40 credits — the low end once your agent’s context is cached, which it is after the first message — and a deep multi-step run roughly 50–500, depending on how many steps it takes. Your run receipt shows the new figures, and it no longer labels cached input with a fixed discount, because the rate depends on the model your agent uses. See Pricing & Credits.

Each model call in a run is counted once Fixed

When an agent streamed its reply, a single model call could be counted several times toward the run, so a run recorded more credit use than it actually had, and on the Free plan the per-run limit could stop a run earlier than it should have. Each model call is now counted once, when it completes, and a reply you stop partway through is counted once for what it used. See Pricing & Credits.

Describe it shows its progress, and says when it could not draft Fixed

When you describe an agent in plain words — Describe it on the home screen, or Draft with AI under Agents → New agent — the progress line now follows what the draft is doing, such as Researching the web… and Reading a source…, instead of sitting on its first line until the draft arrived. If no draft comes back, the page now says Couldn’t draft an agent with a Try again button, rather than showing only the closest templates as if the request had worked. Create skill from this chat shows the same step-by-step progress. See Your First Agent.

A sharper, smoother live browser you can watch full screen Changed

When you watch your agent browse, the view is now rendered at the full resolution of your display instead of being scaled up from a smaller image, so text on the page is legible rather than soft. The panel can be opened full screen, and the page the agent sees resizes to match the panel you are actually looking at — no more letterboxed bars or blur from the view being squeezed into a fixed shape. The stream also adjusts itself to your connection: on a fast link it runs at a higher frame rate, and on a slow one it steps down gently instead of stuttering or falling behind. See Computer Use & Browser Automation.

Deep that you choose is what starts a Goal Changed

When you pick Deep for a real request — on the Auto / Fast / Deep pill beside the send button, or as the agent’s default in its settings — the agent now treats it as a Goal: it checks its own result afterwards and can book a follow-up pass to finish, inside a credit budget you can see and stop. What changed is everything that used to do the same by accident. A greeting, an acknowledgement or a one-word reply never becomes a Goal, whichever mode is set; neither does a message the platform routed to Deep on its own — that run still gets the Deep model and budget, it simply books no follow-up passes; and neither does a scheduled run, a Loop, or a follow-up the agent booked for itself. Before this, saying “hi” to an agent set to Deep could start something that kept working and spending while you were away. Goals are on paid plans, and their passes count against your organisation’s daily allowance for unattended work. See Goals and Execution modes.

One place above the message box, in a fixed order Changed

Only three things now appear between the conversation and the message box, always in the same order: something waiting on you, one line of progress, and the background bar. Previously as many as six cards could stack there at once and stay after they stopped being true. The plan now lives in the conversation, at the turn that wrote it, as a single row — Plan v1 · 5 steps · ~150 credits with one status chip that moves from needing your go-ahead to approved, running, done, or superseded by a later version — and clicking it opens the whole plan in a Plan tab in the canvas, with a version switcher, rather than floating over your messages for the rest of the session. The goal card now says what is actually happening: In progress only while a run is working, Checking whether it’s done… while the result is being assessed, Next pass at 14:22 when one is booked, and Done, Budget reached or Pass limit reached when it has ended — and it keeps the credits it has spent up to date instead of reading zero all session. See While the agent works.

Your agent’s computer says what it is really doing Fixed

“Setting up your computer — this can take a minute or two” could stay on screen for the rest of a session, or appear over a computer that was already running because another conversation had just started one. Starting a new conversation could warn you that the sandbox was “being used by someone else” when the only thing holding it was the boot your own first message had triggered. The Files, Git and Terminal tabs could stay hidden after the computer was ready, and the Computer tab offered a button to start a machine that was already there. All of that now follows the real state: the status clears when the computer is ready, the tabs appear with it, the Computer tab connects to a running machine straight away and shows the start-up steps while one is still coming up, and “someone else” is said only when the holder genuinely is another conversation. A long browsing session also no longer stops collecting the page’s console messages partway through, so your agent keeps seeing the errors it is meant to report. See Sandboxes.

A message you queue, or send after Stop, is no longer lost Fixed

Typing while the agent worked and pressing Enter was supposed to queue your message as the next turn. Instead it was being rejected silently — no error, no queued message, nothing sent. It now queues and runs as intended. And a message you type after pressing Stop now reliably starts a new run rather than being treated as a steer for the run you just stopped; when a steer genuinely cannot be delivered, it stays on screen with the reason instead of disappearing. See While the agent works.

Finished conversations stop reporting on themselves Fixed

An ordinary conversation turn that had completed perfectly well could reappear on the background bar and, some minutes later, announce itself as having “stopped after 398s” — and the agent could then write you a long explanation of a failure that never happened. Chat turns no longer register as background work at all; the bar is for things that genuinely keep running after your turn ends. Where finished background work can wake a conversation that has already ended — still limited to a small set of organisations we run ourselves — it now does so only when there is actually something to read, and that turn appears as a system note, never as a message in your own words. See Background work.

Stopping a task now stops the commands it left running Fixed

When you cancelled a task that had started long-running commands on its computer, the workspace said it had stopped while the commands kept running — to their own time limit, and charging credits the whole way. Cancelling now reaches those commands, so what you are told matches what is happening and what you are billed for. See Background work.

Disconnecting a Connection clears its credentials from a running computer Fixed

When you disconnected a Connection, the credentials that had been handed to your agent’s computer were not reliably removed from computers that were already running — so an agent mid-session could still have held them. They are now cleared as soon as you disconnect. You do not need to do anything; if you disconnected something recently and want to be certain, stopping and restarting that agent’s computer clears it outright. We are sorry — a disconnect should mean disconnected. See Connecting an Integration.

Conversations are named after the first real thing you asked Changed

The conversation list filled up with rows called “Greeting and offering assistance” and “Initial Greeting and Assistance”, and a conversation could be renamed after whatever had gone wrong most recently. Names are now taken from the first substantive message, only once a run has finished successfully — and a name you set yourself is never overwritten.

A tidier conversation Changed

A handful of smaller things in the workspace. A new conversation no longer offers invented starter suggestions — it shows the agent’s name, its description and the message box — and starting from a template no longer drops a half-written prompt into your message box that then followed you into later conversations. The agent header carries one status dot instead of two, and it now says what it means when you hover it. A presentation fills the canvas instead of sitting small in the middle of it, on large screens especially. Costs read credits rather than cr. Mathematical arrows and symbols come through as symbols rather than raw markup. And the bell no longer notifies you about the conversation you are looking at.

Three ways to make your first agent, and a home that starts you off New

A brand-new organisation now opens on a home screen that greets you and offers three ways to make a first agent: describe what you want in plain words and get a draft to look over before anything is saved, start from a template, or start blank. Beside them is a one-line explanation of each part of Auteryn — Agents, Skills, Knowledge, Integrations, Loops and Contacts — and an offer to be shown around in five stops, which is only ever offered and never starts by itself. Make that first agent and you come back to the home screen with a Say hello card, a suggested first message, and a five-step setup list — an agent, a first conversation, a Connection, Knowledge, a Loop — that ticks itself off as you go and retires itself once it is done; owners and admins see the list. The first time you open a library page you have not met, a short card says what the noun is, gives a couple of examples, and goes away for good when you dismiss it. In the conversation there is now a welcome line on your first visit, a sentence explaining the wait the first time an agent’s computer is starting — and that it stays warm afterwards — and a quiet note when your first run finishes. See Quickstart.

A home screen built around what needs you Changed

Once your agents are working, the home screen leads with one line of plain status — agents healthy, what is running, today’s runs and how they went — and then with Needs you: approvals waiting on someone, runs that failed in the last day, Connections that have stopped working or need re-authorising, an agent that is still missing something, a low credit balance. Each has one action, and when there is nothing the lane says so rather than disappearing. Below it, Live now shows the runs in progress with the step they are on and how long they have been going, refreshing on its own, and keeps the last completed run there when nothing is running. Throughput now always renders its figures, showing a dash where a period is too thin instead of hiding the panel, and keeping the last good numbers with a note when a refresh fails. Your agents appear as tiles from the very first one, each with its recent activity, rather than only once you have several.

The chat workspace no longer dead-ends when you have no agents Fixed

Opening the chat workspace before you had made an agent showed “No agents are available for this organization” and nothing you could click, which is exactly the moment you most needed a way forward. That screen now explains what an agent is and offers to create your first one.

Helpers scale with your plan New

How far your agent can fan a job out now follows your plan: up to 4 helpers per fan-out on Pro, 8 on Business and 12 on Enterprise, with 1, 2 and 3 fan-outs running at once respectively. Free keeps single helpers. Whatever the width, only a couple of helpers work at the same moment and the rest queue — the group card now says so (Working with 8 helpers · 2 at a time), each waiting row says how many are ahead of it, and the fan-out confirmation names how many start at once. Nothing to switch on; the numbers are on the pricing page and explained under Helpers.

Stop on the background work bar works again Fixed

Stop and Stop all on the bar above the message box returned an error instead of stopping anything, so a command you had asked to stop carried on running — and carried on costing credits — until it hit its own time limit. Both buttons now work. If something genuinely cannot be stopped right then it says why, for example that the browser is in use, and Stop all tells you which items it could not stop rather than reporting a silent failure. See Background work.

Background work that finished no longer blocks the next one Fixed

When your agent left several background commands running and they finished on their own, the sandbox could refuse every new background command for the next couple of hours, saying five were already running when none were — and the command it suggested you stop had nothing left to stop. A command that ends on its own now gives its slot back immediately. See Background work.

Background work is charged for the time it was allowed to run Fixed

A background command could report a longer run than it was permitted, and that unchecked figure could reach both your charge and the duration shown on its row, so a row could say one thing while the credits said another. The charge is now bounded by the limit a background command may run for, on every path, and the duration you see on the row is the one you were charged for. See Background work.

A queued helper says how many are ahead of it Fixed

When your agent fanned a job out to several helpers, a helper waiting for a free slot could only say it was waiting, never how long the queue was. Its row now reads how many helpers are ahead of it and updates as the line moves. When your agent asks you to confirm a fan-out, the confirmation also says how many of those helpers actually start at once, instead of implying they all do. See Helpers.

Everything your agent left running, in one place New

When an agent starts something that keeps going while you carry on — a long command, a development server, a helper, a scheduled run, a document export — it now appears on a slim bar just above the message box: what it is, what it is doing, how long it has been going, and a way to open it, stop one thing, or stop everything at once. A command that runs past its time limit is moved into the background and carries on rather than being killed and thrown away, and your agent is told the moment background work finishes instead of re-running a command to find out. When you are not looking, a completion raises a bell entry, a toast if you are in another conversation, and a marker on the browser tab; whether it also reaches you by email follows your organisation’s notification preferences. One part is not on for everyone yet: letting finished work wake a conversation that has already ended, so the agent can read the result and tell you what happened, is limited to a small set of organisations we run ourselves while we watch it — where it runs, it spends credits while you are away, under a daily ceiling. See Background work.

Watch each helper work, and what it costs New

When your agent hands a piece of a job to a helper, the helper now appears in the conversation as a live card — what it was asked to do, the model it is using, the steps it has taken, and the credits it has spent so far — with the steps collapsing behind its summary when it finishes. A helper can work in the background while your agent carries on with something else, and on Pro and above an agent can fan a job out to several helpers at once, shown as a group card with a row and a running cost per helper. Stopping the run stops every helper it started. Before fanning out, the agent says plainly that it is about to spend roughly as many credits as running the job that many times, and it does not start if the estimate is more than your balance. A Skill can also be set to run as a helper, with the access you choose — read-only, edit, or shell — and a step budget. See Helpers.

See what your agent remembers, correct it, or switch it off New

Memory is no longer something that just happens out of sight. Quiet chips in the conversation say when something was recalled, saved or forgotten, and open a Memory panel listing what the agent holds, where each entry came from, and how full the memory is. You can edit an entry, forget it — deleted entries stay recoverable for a while and are then purged for good — or read its history and the evidence behind it. Three switches per agent control remembering across conversations, learning automatically, and keeping per-person preferences; Don’t remember this chat does it for a single conversation, where the agent still reads what it already knows and simply learns nothing new. A Me view shows your own memories across every agent in the organisation, you can ask your agent about things from your earlier conversations with it, and a voice call in the workspace uses the same memory as chat — while a phone call deliberately writes none, because we do not assume the caller is you. See Memory.

Run a Skill with /, and see which one your agent is following New

Type / in the message box to pick a Skill for that message. While a Skill is in effect, a Following skill pill names it in the run header and says whether you or the agent started it, and the activity rows name the Skill files it reads — so a Skill-driven run is not a black box. If a long conversation gets condensed, the Skill is re-attached afterwards and says so. Each Skill now has an Invocation setting deciding whether you, the agent, or both may start it, and a Skill can narrow what the agent is allowed to do while following it — never widen it, so adding one from a link at worst asks you more often than you are used to. Skills that ship scripts or reference documents place them in the agent’s sandbox, where nothing runs by itself. The Skills tab also shows when each Skill was last used on that agent, so you can detach the ones that never are. See Using Skills.

A panel that tells you which Integrations your agent can actually reach New

The workspace side panel now lists every Integration the agent is bound to with its real state — connected, needs authorisation, unavailable with the reason, or changed since you approved it — and expands to show each ability and whether it reads, writes, deletes, or always confirms. Your agent is told up front which Connections are unavailable for a run, so it tells you which one to fix instead of improvising around it. Abilities that a service itself marks as needing a person always ask, at every autonomy level, with no option to remember your answer, and are refused where there is nobody to ask — a scheduled Flow, a customer conversation, a run delegated from a phone call. An Integration can also ask you for something mid-run, as a short form or a link to finish on its own site, and images and links it returns arrive as artifacts and links rather than being flattened into text. In the Console, a Custom Integration can now sign in with OAuth instead of a static key. See Integration health & prompts and Custom Integrations.

Undo a file your agent changed, and give each conversation its own branch New

Every file an agent edits directly is recorded with the version that was there before. Each file-change card now has Undo, the group header has Undo all in this run, and hovering any of your own messages offers to put the files back the way they were when you sent it, telling you first how many files across how many runs. Changes made by a command have no per-file version to restore — the card says so and offers to restore a checkpoint instead. While another conversation is using the sandbox, anything that needs it waits its turn instead of hanging, and the workspace names the conversation holding it. When a sandbox comes back from a snapshot you get a card saying exactly what came back and what did not: unsaved files, dropped variables, commands that were stopped. Agents working in a code repository can be given a branch per conversation, with Apply to main workspace and Discard branch in the Git tab, and helpers can each work on their own branch so two never overwrite each other’s edits. See Undo & branches.

Keep typing while the agent works New

The message box no longer locks during a run. Enter queues your message as the next turn; ⌘/Ctrl + Enter steers the current one. A queued message sitting behind other runs tells you how many are ahead, and a steer that arrives just as a run ends is carried into one follow-up turn and marked carried — or marked dropped, with the reason — rather than being lost. Some questions no longer stop the run at all: the card says you can answer any time and the agent carries on without you. When a run reaches its budget it takes one short final turn to tell you where it got to and what it would do next, with Continue to pick up from there. You can also condense a long conversation deliberately with Compact now, saying what must survive, and a run interrupted by a restart replays the steps it had already taken rather than performing them again, so an email is not sent twice. Scheduled runs are now spread across a few minutes rather than all firing on the same tick, and a recurring loop your agent proposed — not one you created — expires after a while instead of running indefinitely. See While the agent works and Scheduling.

Organisation-wide approval rules and a minimum approval level New

Console → Settings → Governance sets rules that apply to every agent in the organisation at once: a minimum approval level that an individual agent may be stricter than but never looser than, always-allow / must-ask / never rules written by action — where never is the one control that cannot be worked around from inside an agent’s own settings — and a final confirmation on spending money and handling credentials, on by default. Owners and admins can see the page; only the organisation owner can change it. The same page can have Auteryn call an HTTPS endpoint you run at key moments in a run, letting your own systems block a message with a reason, add context the agent must take into account, decide an approval, or ask for one more pass; that part is limited to a small set of organisations we run ourselves for now. See Organisation governance and Autonomy & approvals.

A task waiting on a background command no longer says it has finished Fixed

When your agent started a long command — a build, a test run, an export — and stepped away to wait for it, the conversation could show the task as complete while the work was still going. The task now stays open and says it is waiting on a background command, and picks up again when that command ends. See Background & Long-Horizon Execution.

What you say in a private conversation stays in it Fixed

Facts an agent picked up during a private conversation could be saved as knowledge the agent shared with everyone who uses it. Anything learned in a private conversation is now kept to you, and an agent-wide note can no longer be written from a private conversation at all. Nothing you need to do. See Private Conversations.

Deleting a memory takes effect immediately Fixed

A memory you deleted could still be recalled by the agent for up to an hour afterwards. Deletion now reaches the agent straight away, and it is recorded in the memory history. See Memory.

Approval rules on an Integration now apply to that Integration’s actions Fixed

A rule you set for a specific Integration — always allow, must ask, or never — was not being matched against that Integration’s actions, so the rule had no effect. Those rules now apply, including to Integrations reached through a Connection. The console also refuses a rule that names an Integration your agent is not connected to, instead of saving one that could never match. See Autonomy & Approvals.

Stopping a task stops its helpers too Fixed

When an agent had delegated part of the work to helpers running alongside it, pressing Stop ended the main task but could leave the helpers working. Stop now reaches every helper, and a helper that is left behind by a failure is cleaned up.

A failed Integration action no longer reads as a success Fixed

An Integration call that failed could still be shown in the conversation as a tick with a count of fields returned. A failure is now shown as a failure, with its reason.

Testing an Integration tells you whether the credential actually works Fixed

Test reported whether we could reach the service, which is not the same as whether your key, token or account still works — so an expired credential could show green. Test now asks the service itself, using a read-only check that costs you nothing, and reports three answers: verified, rejected (with the reason), or no verdict available. A result we could not confirm is never shown as verified. Test also times out instead of hanging on a slow service. See Connect an Integration.

Searching your Integrations no longer errors Fixed

Searching the Integrations list failed for any organisation that had a connected Integration with discovered actions. Search works again, and the connected-Integration list renders those actions correctly.

Your agent’s sandbox can’t be restored or deleted out from under a running task Fixed

Restoring or deleting a sandbox snapshot while another conversation’s run was using the sandbox could pull the working files away mid-task. Those actions now wait, naming the conversation that is using the sandbox, and the workspace shows the sandbox as busy instead of offering buttons that would break the run. See Sandboxes.

Agents no longer draft Skills on their own after a run Changed

After a longer successful run, an agent could draft a proposed Skill for you to review. That proposal step is now off by default: it ran on every qualifying run whether or not you wanted a Skill from it. Skills you create yourself, Skills added from a link, and every Skill already attached to your agents are unchanged. See Skills.

Plans you can actually read, and a second model checking risky actions New

Your agent now writes a real plan — a goal, an approach, numbered steps, its assumptions and any open questions — instead of a one-line checklist. Each step shows what it will do and whether it will need your approval when it runs. You can approve it, ask for changes, answer its questions, or edit the plan yourself. Approving covers the ordinary steps, so the agent doesn’t stop again for each one, while destructive and sensitive steps still ask at the moment they run.

At Autopilot and Guarded, a separate reviewer model now checks each write or destructive action against your original request before it happens, and brings it to you when it looks beyond what you asked for. It never relaxes the safety floor, and when it is unsure or unavailable it asks you rather than proceeding.

You can also set approval rules per agent — always allow, must ask, or never — by action, and answer a waiting request out loud during a live voice call. See Autonomy & Approvals.

Stopping a run now stops it Fixed

Pressing Stop cancelled the run’s display but could leave the work itself running for up to a minute and a half afterwards, still spending credits and still able to stop for approval on something you had already cancelled. Stop now halts the work itself.

Two runs on one conversation no longer lose each other’s questions Fixed

When more than one task was working on the same conversation — a background task you delegated by voice, a scheduled run, a recurring loop — a question from one could overwrite a question from another, leaving a run waiting on an answer you were never shown. Each waiting request now appears as its own card, labelled with the run it belongs to.

Plans no longer stop for a word in the text Fixed

Plan approval was decided by matching words in the plan’s text, so a piece of pure research could stop and wait because a step mentioned “production”. Whether a plan waits is now decided by what its steps will actually do.

Automated runs use your plan’s full capabilities Fixed

A message your agent received over a channel — Telegram, WhatsApp, Slack or the web widget — or a run started by a flow could be answered with free-plan limits instead of your plan’s: a smaller budget for the run, and premium capabilities unavailable. Those runs now carry the same entitlements as a message you send the agent yourself. See Flows and Messaging Channels.

The live browser view reconnects Fixed

Watching your agent browse could get stuck on “reconnecting…” and never recover, and the New tab button in that panel did nothing when clicked. Both now work. See Computer Use & Browser Automation.

Cloned and designed voices cost less Changed

Speech in a designed voice now bills at 50 credits per 1,000 characters and a cloned voice at 60, down from 150 for both. Preset voices are unchanged at 50. See Pricing & Credits.

Designed voices are ready the moment you create them Changed

Describing how a voice should sound no longer sends that description to a separate voice-building service and waits. Your description now steers the voice directly, so a designed voice appears in your library immediately instead of processing in the background, and it can no longer fail after the fact. Any voice you had already designed keeps working. See Audio generation.

Sound effect generation has been retired Removed

Agents can no longer generate sound effects from a description. The capability depended on a single provider we no longer use, and none of the providers that replaced it offers an equivalent. Speech, multi-speaker audio and slide narration are unaffected. See Audio generation.

Multi-speaker and long-form audio complete again Fixed

Generating a multi-speaker conversation or a long script in a preset or designed voice was failing at the final step — after every segment had been produced — and returned no audio. The segments are now combined correctly whichever voice produced them. See Audio generation.

Slide narration plays in every browser Fixed

Narration added to a presentation in a preset or designed voice was saved with the wrong audio format label, so Safari refused to play it and its length was misreported. Narration now carries the format it was actually produced in. See Audio generation.

Video generation is more reliable Fixed

Extending or editing a video your Agent already generated now completes instead of failing partway through: the continuation step was silently breaking the link to the original clip. Longer, higher-resolution videos are now labelled as AI-generated like every other one, and saving a generated video to your workspace files now writes the file. See Content Generation.

Sound effects cost what they run Fixed

Sound effect generation used to bill one flat amount whatever its length. It now bills for the seconds you ask for, so a short effect costs less and a long one costs more, in line with the published rate. See Pricing & Credits.

Multi-language audio uses the language you wrote Fixed

Generating spoken audio in several languages from one script no longer assumes the script is English. It works from the language you declare, or the voice’s own language, so the translated audio comes out right. See Audio Generation.

July 2026

Simpler agent types Changed

There are now two agent types — Internal and Customer-Facing. The former Collaboration type has been folded into Internal: internal agents now have an Allow external guests toggle to invite people outside your org to specific conversations. Existing Collaboration agents were migrated to Internal with guest access enabled. See Agent Types.

Bring your own computer New

Internal agents on paid plans can now run on your own Ubuntu/Debian machine instead of the managed cloud sandbox. Install a signed runner that dials out over a secure outbound tunnel — no inbound ports — and the agent uses your environment, credentials, and network. This also unlocks residential-IP web fetch, so pages that block datacenter traffic load from your home or office IP. See Bring Your Own Computer.

Autonomy dial New

A per-agent autonomy level now controls how often your agent pauses for approval — from approving every plan and sensitive action to running fully autonomously — with plan-approval modes of always, smart, or never. Approvals are durable, so requests wait for you and the agent resumes where it left off. See Autonomy & Approvals.

Fork a conversation New

Branch any conversation into a new thread from any point to explore alternatives without losing the original. See Fork a Conversation.

Background & long-horizon execution New

Agents can run long, autonomous tasks in the background — asynchronous runs, self-scheduled follow-ups, and resume across interruptions — beyond a single synchronous reply. See Background & Long-Horizon Execution.

Featured MCP & expanded integrations New

New dedicated guides for ServiceNow, Telegram, Twilio / WhatsApp, and the Web Widget, plus a Featured MCP tier of ~29 hosted MCP servers (Sentry, Datadog, Shopify, Stripe, HubSpot, Postgres, Snowflake, BigQuery) with a managed credential model — alongside OAuth integrations and self-hosted Custom MCP.

June 2026

Premium workspace New

The sandbox workspace now includes a full file explorer with file previews, a Git Source Control panel for staging and committing changes, and a multi-tab terminal — a complete IDE-style surface alongside the chat.

Real-time voice New

Talk to your agent. Real-time voice conversations are available in the workspace on Pro plans and above, with selectable agent voices.

April – May 2026

Presentation builder upgrades

Generate polished, themed slide decks, add narration and voiceover, and publish decks to a shareable link.

More featured integrations

Expanded the catalog of one-click MCP integrations and added new agent templates and skills to the library.

Smarter new-chat suggestions

Agent-aware starter prompts now appear when you open a new conversation.

March 2026

Computer Use GA New

Computer use is now generally available on Pro plans and above. Your agent can browse the web, interact with UIs, and extract data from any website.

Custom Skills New

Create your own reusable skills and share them across agents.

Knowledge Sync Performance

Sync times reduced by 60% for large Confluence spaces and Google Drive folders.

Fix: WhatsApp template message handling

Resolved an issue where approved WhatsApp message templates weren’t being sent correctly in some regions.

February 2026

Flow Scheduling New

Schedule your agent to run on a timetable with full cron expression support. Available on all plans.

Google Drive Integration New

Sync Google Docs and Drive folders directly into knowledge collections.

Datadog & Sentry Integrations New

Connect Datadog and Sentry to let your agent monitor for alerts and read error logs.

Agent Test Panel improvement

The test panel now shows real-time tool call details and credit usage inline.

January 2026

Collaboration Agent Type New

A new agent type designed to work alongside your team. (Consolidated into Internal agents with the Allow external guests toggle in July 2026 — see above.)

Notion Integration New

Read and write Notion pages and databases. Also usable as a knowledge source.

Fast mode speed improvement

Fast mode responses are now 35% faster on average.

Q4 2025

Web Widget — embed a chat bubble on any website with a single script tag
WhatsApp Business API integration
Knowledge web crawler
Skill Library — Coding, Research, Customer Support, and DevOps
Multi-organization support

Q3 2025

Auteryn public launch
Core agent runtime with tool support (GitHub, Slack, Google Workspace, Jira, Confluence)
Knowledge support (file upload, Notion, Confluence, GitHub)
Flows with webhook and schedule triggers
Telegram deployment
REST API with streaming support