What's new in Quaso

You can now link your phone in Settings and message Quaso from Messages on your iPhone or Mac. It understands voice notes and photos, and you can answer its questions with a number or a Tapback.

The beta has limited seats. If linking says it is full, try again later or use WhatsApp in the meantime.

Quaso now has a public changelog at quaso.ai/changelog, listing what was added, improved and fixed in each release. Open it from your account menu. Every entry has its own link, so you can point a teammate straight at the change you mean.

Slack automations can now send replies as the Quaso bot in an existing message thread, with attachments delivered to the same thread.

You can now pick GPT-6 Astra for your chats.

You can now pick Claude Fable 5.1 for your chats.

Long threads now render only their most recent history at first and load older messages automatically as you scroll toward the top. This also applies to shared chats and automation run transcripts.

A new Copy button next to Share copies the full conversation, including your messages, the agent's replies and short summaries of its tool calls, as readable text you can paste into notes or docs.

InFlow is now available as a preset under MCP servers, so the agent can check balances, authorize payments and manage spending policies for agentic commerce. You need an InFlow account with a funded wallet.

The Add a skill section now has an Upload file / Paste text toggle, so you can paste markdown and an optional name directly. A name: in the frontmatter takes precedence, and a skill with no name at all is rejected.

Apps marked Needs reconnect now have a Reconnect button that re-authorizes them in place, keeping a shared connection shared. A broken connection no longer looks identical to a working one.

You can now add a Tailscale OAuth client under Settings > Tailscale so the agent's sandbox can reach private services on your tailnet, such as an internal Grafana, a NAS or a home-lab API, in both chats and automations. Each sandbox joins as a temporary node tagged tag:quaso-sandbox, so your tailnet policy decides what it can reach, and the agent can list the hosts it is allowed to see instead of asking you for their names. The client needs permission to create auth keys for that tag, which is checked when you save it.

You can now connect a ChatGPT plan in settings and run turns on its quota instead of spending credits. Once connected, Codex variants of the supported GPT models appear in the model picker, and a turn falls back to the regular model if your plan's quota runs out. Device code authorization must be turned on in your ChatGPT account settings before connecting.

You can now add environment variables under Settings > Sandbox secrets, such as an API token for an internal service, and the agent can use them in its sandbox. Values are encrypted, redacted from command output and never shown back after saving; the agent only sees their names. On shared workspaces, only owners and admins can change them.

When a task needs your own account on a site Quaso has no integration for, the agent now asks for the login through a secure form in the thread instead of in chat. The login is stored encrypted and filled inside the browser, so the agent never sees the password, and you can replace or remove it under Settings > Site logins. Scheduled runs can use saved logins but cannot ask for new ones.

When you talk to Quaso in Slack, the agent now uses your Slack timezone for the current time, so time conversions and "what time is it" answers are no longer off. If no reliable timezone is available, it asks you instead of guessing.

Clay is now available as a one-click MCP server: connect it with your Clay account from the MCP servers list, with no manual setup.

You can now pick MiniMax M3 in the model picker. It has a 1M-token context window and supports image input.

Messages that include a malformed Slack table or layout block no longer show "This message couldn't render." Quaso repairs the layout, or falls back to plain text.

When a model provider has a brief outage or overload, Quaso now retries automatically in chat and in Slack instead of failing the reply.

Voice dictation in the composer now streams: words appear in the message box while you are still speaking instead of after you stop.

When you remove someone from a workspace, their workspace API keys stop working immediately and their automations in that workspace are turned off.

In a chat that runs a scheduled automation, your messages are now answered as a normal conversation, so you can ask about or edit the automation. Previously Quaso could respond by re-running the automation's steps.

Workspace owners and admins can now set a model for automation runs in Settings, next to the default chat model, for example to run unattended automations on a cheaper model. A model chosen for a specific automation still takes priority.

The Artifacts page now lets you filter by file type and by the teammate who created each file, and shows clean file names instead of raw storage names.

Automation runs that failed right at the start now appear as errored runs on the automation page instead of leaving no trace.

The artifact viewer now has a Download button, so you can save a file from a shared artifact link, including on a phone browser.

Automations now list the apps, MCP servers and browser access they rely on. You can see them on the chat header, on the automation page with buttons to connect anything missing, and as a warning badge in your automations list. Opening a shared chat also shows what you need to connect before running your own copy.

You can now pick Grok 4.5 and Claude Opus 5 in the model picker. Both support image input.

Use Move to workspace in a chat's menu to move it, together with its automations, to another workspace you belong to. Quaso warns you first about apps not connected there and billing moving to the new workspace, and the original is archived so you can restore it. Webhook automations get new URLs, and automations triggered by app events stay off until you reconnect those apps.

A new Support page links to the docs and lets you send a structured support request. You can also permanently delete your account and your solo workspaces from Settings, after cancelling any active paid plan and transferring ownership of shared workspaces.

A WhatsApp message now starts a fresh conversation when the last chat has been idle for more than 24 hours, and Quaso tells you it did. To continue an older conversation, reply to one of its messages.

When you ask Quaso in chat to send an email, Slack or WhatsApp message, it now shows a preview of the exact message first and waits for you to Send or request changes. Automations and messages from connected channels still send directly, since nobody is there to approve them.

When you ask Quaso for an image from Slack, the generated image is now uploaded directly into the Slack thread instead of arriving only as a link.

Each automation's page now has a Stored values section where you can view and delete the values it saved between runs. The global storage view in Settings now lists only files that don't belong to an automation.

Delegating a Linear issue to Quaso without adding a comment now starts work on the issue. Previously Quaso could just acknowledge the delegation and stop.

When you message Quaso from Slack, WhatsApp or Linear, it now always sends its answer back there instead of sometimes leaving it only in the Quaso thread. Quaso also retries automatically when a model returns an empty response.

You can now pick Kimi K3 in the model picker. It supports image input.

Folders you create in a team workspace are now private to you, and you can use Share with workspace to make one visible to teammates. Moving a chat into a shared folder shares that chat too. Folders that already existed stay shared.

Workspace owners and admins can now choose a default model in Settings. New chats, chats without a model of their own, and messages arriving from connected channels use it, while a model you pick yourself always wins. Other members see the setting read-only.

You can now connect several Slack workspaces to a single Quaso workspace from Settings, and Quaso replies in whichever one you message it from. Slack requires the Pro plan, and only workspace owners and admins can connect a workspace.

Every Quaso reply in Slack now carries a View in Quaso button, and opening it shares that conversation with your Quaso workspace so teammates can follow it too. The eyes reaction on your message also switches to a checkmark once Quaso has replied.

Automations that watch a website now show up as a Website trigger in your automations list. Checks where nothing changed stay out of your run history, so you only see runs when the page changed or could not be read.

Switching workspaces from the sidebar or avatar menu now keeps you on the page you were on, such as Settings, instead of sending you to the workspace home. If you were viewing a specific chat or automation, you land on that section's list.

If you belong to several workspaces, you can now pick in Settings which one handles the emails you send to Quaso. Existing email conversations keep going as before.

Chats started from Linear now show the whole run, including each step Quaso took, instead of only the final reply.

A single Quaso turn can now run for up to 30 minutes and up to 100 steps, in chats, automations and channels, so longer jobs finish without being cut off. If a chat still reaches the limit, you can continue it on the web from where it stopped.

You can now give a thumbs up or thumbs down on Quaso's replies in a chat, and add a comment when something went wrong.

Connecting the Atlassian MCP preset now completes sign-in instead of failing before it starts. If connecting any MCP server fails, the connect card in the chat now shows the actual error, and cancelling the sign-in no longer shows an error page.

When you ask Quaso for something in Slack or WhatsApp that needs an app you haven't connected, it now sends you a link that opens Settings and starts connecting that app. Once it's connected, send your message again.

New accounts now answer a short onboarding form, then get a Getting started checklist in the sidebar that walks through your first chat, connecting an app, Slack, WhatsApp and your first automation. Template suggestions on the home page and in Templates are now picked for the role you chose.

You can now install the Quaso GitHub App on your repositories from Settings. Quaso reviews each pull request when it's opened or updated, and answers when you mention @quaso-app in a pull request or issue comment.

You can now connect Mintlify, Fern, Brex, Ramp, Mercury and Qonto from the MCP server presets. Most connect in one click, Fern opens a prefilled form for your docs site, and Qonto is available for EU accounts only.

In a personal or single-member workspace, the apps you connect are now always personal. In a team workspace, you choose Just me or My team when you connect an app. If you have both a personal and a shared connection to the same app, Quaso uses your personal one.

You can now filter your chats in the sidebar by source, such as web, Slack, WhatsApp or email. All sources are shown by default, and All in the filter menu brings everything back.

Quaso can now start up to four sub-agents that work on parts of a task at the same time and report back, which speeds up broad research and multi-step jobs. Sub-agents share the task's budget, and stopping the main run stops them too.

Quaso can now message you on WhatsApp from any chat or automation, and send files it can't attach as a temporary download link. If you haven't messaged Quaso in the last 24 hours, you get a short notice with a link to the chat, and the full message arrives once you reply. You can also swipe to reply to an older message to continue that chat.

You can now branch from a message to start a new chat that keeps everything up to that point, so you can try another direction without losing the original. The new chat opens right away and is marked (Branched) in the sidebar.

You can now get a desktop notification in your browser when Quaso finishes working on a chat, so you can switch tabs while it runs. Your browser asks for permission on your first chat, and you can change the setting any time in Settings > Notifications.

Workspace settings now include a danger zone where you can permanently delete a workspace you no longer need.

You can now CC Quaso on an email conversation with other people. By default it replies only to you, and it replies to everyone already on the thread when the answer is meant for the group. It never adds new recipients.

Opening a chat now takes fewer round trips, and a loading placeholder appears the moment you click, so the previous page no longer sits frozen while the next one loads. Long chats also re-render less while a reply streams in.

You can now pick GPT-5.6 Sol, Terra or Luna from the GPT-5.6 group in the model picker. GPT-5.6 Terra is now the default model for new chats.

When you mention Quaso in Linear, it now works out who you are from your email address. If your Linear email is different from your Quaso email, you can link your Linear account in Settings so Quaso still acts as you.

When a task needs a tool that one of the ready-made MCP servers provides, Quaso now shows a connect card in the chat so you can set it up without leaving the conversation. If the app is already connected, Quaso uses that connection instead.

To talk to Quaso in Slack, each person now connects their own Slack account in Settings. If Quaso doesn't recognize you yet, it replies in Slack with a Connect Slack button instead of running as someone else.

In team workspaces, new chats are now visible only to you. Use the Share dialog to give your team access. Shared chats appear under Shared with me for teammates, who can read them and continue in their own copy. Automations stay visible to the whole team.

You can now link your phone number in Settings and message Quaso on WhatsApp, including voice notes, which it transcribes and shows back to you before it starts. A number can be connected to only one workspace at a time, and Quaso asks you to confirm before moving it to another one.

Having the same chat open in two tabs no longer starts two replies at once, and resuming a reply after a reload no longer shows it twice. A broken screenshot can no longer leave a chat unable to continue, and chats already affected by one now recover.

The sidebar now has a Search entry that opens the command palette (⌘K). From it you can jump to any settings section and find apps or MCP servers to connect without leaving the page.

Quaso can now create an image from a text description, with an optional aspect ratio, and share it in the chat.

Runs started from Slack, email, Linear or the API now stream live in their Quaso chat on the web, and you can stop them there. In Slack, Quaso reacts with 👀 when it picks up a message and ❌ if it fails, and shows what it is doing at each step.

Quaso can now find people who match criteria you describe, such as role, company or location, and return a verified list you can use for prospecting or research.

When Quaso needs you to choose something during a Slack run, it now posts the options as buttons, or a dropdown for longer lists. Your choice continues the run in the same thread.

You can now ask Quaso in chat to view or change your workspace's custom instructions instead of editing them in settings.

Quaso can now publish HTML and Markdown documents as standalone pages. They are private to your workspace by default, and you can make them public with a link. A new Artifacts page and a panel in each chat list the files and pages Quaso created, so you can open, change visibility or delete them. Public pages expire after 30 days by default.

When you sign up, Quaso now opens a first conversation that asks about your role and suggests templates that fit, like founder, sales, marketing or customer service, then helps you connect the apps they need.

While Quaso is working, you can now use Send now on a queued message to deliver it right away. Quaso picks it up at its next step instead of waiting for the current task to finish.

Apps you connect in a team workspace are now shared with its members by default and marked as shared, so teammates do not need to connect them again. Only owners and admins can disconnect a shared app, and on plans without sharing, connections stay personal.

Once Quaso is working in a Slack thread, it now picks up follow-up messages in that thread without a new @Quaso mention. Quaso also reads the earlier messages in the thread as context when you mention it partway through a conversation.

Automations now describe their trigger in plain language, such as "When a pull request opens", in the list and on the automation page. You can also ask Quaso to change which app event starts an automation, and it keeps the same automation and run history.

You can now add Quaso to Linear from settings, then mention it or delegate an issue to it to start a run that posts progress and its reply on the issue. Each run uses the Quaso account of the Linear user who asked, so that person needs a Quaso account in the workspace.

MCP settings and the Connect dialog now include quick-add presets for services like Linear, Notion, GitHub, Stripe, Atlassian and Intercom. Presets that support sign-in take you straight to the service's consent screen, and the rest prefill the server form for your key.

The skills dialog now lets you search the public skills.sh catalog and import a skill into Quaso in one click.

Runs of commands and tool calls are now grouped into collapsible working sessions, so the reply stays readable while cards you need to act on, such as questions and connection prompts, stay visible. Steps in progress now show readable labels instead of internal tool names.

Workspace settings now have a Members section where admins can invite people by email, change roles and remove members. Invitees accept through a link and are asked to sign in if needed.

Quaso now sees images and files you attach when you mention it in Slack or email it, and it can attach files to its Slack and email replies instead of pasting their contents. Existing Slack installs need to re-approve the app to allow file uploads.

Shared chat links no longer show an empty page once the chat continues after you share it. You can also fetch a shared chat as JSON by adding ?format=json to its link.

A new Templates page lists preconfigured agents, showing the apps each one uses, and featured templates now appear on the home screen. You can browse the templates page without signing in.

You can now pick Fable 5 for any chat. It runs with high reasoning effort and suits complex, multi-step automations.

You can now send a task to inbox@quaso.ai from the email address on your Quaso account, and Quaso runs it and replies in the same email thread. Replies continue the same conversation, which also shows up in your sidebar.

When you connect GitHub, Quaso can now use git and the gh CLI directly in its workspace to clone repositories, push commits and manage pull requests as your account. If you connected GitHub earlier, reconnect it to enable this.

Browser sessions now appear as cards in the conversation, next to the step that started them, instead of in a side panel. Each card shows the live browser while it runs and a replay afterwards, and you can expand it to a larger view.

When you press Stop, including while a long command is running, the partial reply and its steps are now saved and still there after a reload.

When you ask Quaso to email an address other than your own, that person first gets a confirmation link, and Quaso can only email them after they click it. Automations can only send to addresses that are already confirmed, so set recipients up from a chat first.

You can now archive an automation to stop it and hide it from your list without deleting it. Archived automations appear under Show archived and can be restored. Pausing still works as before for automations you want to keep in view.

If an automation run fails because of a temporary error, Quaso now retries it automatically instead of marking the run as failed.

You can now pick Claude Sonnet 5 in the model picker, and it is the default for new chats. Chats and automations that used Claude Sonnet 4.6 now run on Claude Sonnet 5.

Your workspace now earns a daily streak credit bonus the first time you chat with Quaso each day (UTC), and the credit balance updates right away. If you use more than one workspace, each one can claim its own bonus.

Quaso can now list your automations, look up an automation's configuration and review its recent runs from chat, so you can ask why a run failed or what it did. It can also change an automation's tool access and default inputs, and prefers editing an existing automation over creating a duplicate.

Workspace admins can now change the workspace name in Settings.

You can now group chats into named folders shown above Recent in the sidebar. Create, rename and delete folders, and move chats with the row menu or by drag and drop. Folders are shared with everyone in the workspace.

The sidebar now orders chats by their last activity, so renaming one no longer bumps it to the top. A collapsed sidebar also no longer flashes open when you reload the page.

When you mention Quaso in Slack, it now reliably replies in the Slack thread, and the conversation appears in the web app. Slack messages from Quaso are also better formatted.

Scrolling up while Quaso was still writing could pull the view back to the bottom. The chat now stays where you scrolled.

When a reply fails for a known reason, such as a conversation too long for the model, a model that cannot read images, or a rate limit, you now see what happened and what to do instead of a generic error. Each error still includes a reference you can share with support.

You can now create a new workspace directly from the workspace picker. Creating additional workspaces requires a paid plan.

Custom MCP servers that require an OAuth sign-in can now be connected in Settings, and Settings shows the tools each connected server provides. Your custom MCP tools are also available when automations run.

You can now ask Quaso to start an automation when an event happens in a connected app, for example "when a new email arrives in Gmail" or "when a HubSpot contact is created". Describe the trigger in plain English and Quaso sets it up on your connected account.

Images, videos, PDFs and other files you upload or Quaso sends now preview directly in the chat. Click a file to open it in a side panel that shows the full content, including PDFs, spreadsheets, Word documents and code, with a download button. Uploads also show progress for each file.

Pasting a long block of text (5,000 characters or 50 lines or more) into the composer now attaches it as a Markdown file instead of filling the message box.

When Quaso works through a multi-step plan, the plan now stays in a single collapsible panel above the composer instead of repeating in the chat. The collapsed view shows the current step and how many are done; expand it to see the full checklist.

Switching a chat that contains screenshots to a model that cannot read images made every following reply fail. Quaso now skips the images for those models and shows a notice, and the model picker groups models into Vision and Text only.

Quaso can now search the web and read pages directly, without opening a browser, which makes research tasks faster. Results show up as source cards with site icons and links you can open.

You can now add Custom instructions in Settings. Quaso follows them in every chat and every automation in the workspace.

Press Alt+Up or Alt+Down (Option on Mac) to move to the previous or next chat, or Alt+1 to Alt+9 to jump to one of your most recent chats. Both work while you are typing in the composer, and holding Alt shows the number hints in the sidebar.

The Cmd-K search now returns your automations and their run transcripts alongside your chats. Chat results still appear as fast as before, with automation results filling in below them.

Use the Share button at the top right of a chat to share it with your workspace or with anyone who has the link. Viewers see a read-only copy of the chat up to the moment you shared it. A public link exposes the full transcript, including tool outputs, code and screenshots.

Chats in the sidebar now show a Working badge while Quaso is running, a Needs You badge when it is waiting on your answer, and a bold title with a Finished badge when there is activity you have not seen yet. Status updates live, including for runs started from Slack, the API or a schedule.

The automations list now flags runs that failed, so you can see which automations need attention without opening each one. Each automation also gets a plain-language description of what it does.

New automations have no daily budget limit unless you ask for one, and the automation page shows No limit when none is set. You can still set a cap on the automation page or ask Quaso to add one; clearing the field removes it.

Slack and email notifications from Quaso now include a details link that opens the conversation, or the specific automation run, that produced them. Slack notifications also render standard Markdown formatting.

Reopening a chat could show assistant steps out of order. The history now always loads in the order it happened.

You can now ask Quaso to change an automation's name, instructions, model, schedule or daily budget, and it updates the automation in place instead of building a replacement.

Chats with three or more of your messages now show a rail on the right edge, with one mark per message. Hover it to see your messages and click one to scroll straight to it.

Quaso can now propose creating, editing or deleting a workspace skill, and nothing changes until you click Approve on the proposal card. You can also use the new Create skill button in the composer to draft a skill from the current chat.

Press Cmd+K (Ctrl+K on Windows and Linux) to search chats by title and message content, reopen recent chats, or start a new chat or open settings.

Under Settings > MCP servers, add any Streamable HTTP MCP server by URL, with an optional bearer token or custom header, and use Test connection to see its tools. Quaso can then use those tools in chat, and every member of your workspace can use the server. Tokens are encrypted and never shown to the model.

Quaso now knows your current plan, credit balance and spend for the current billing period, so it can answer billing questions directly in chat. Top-up and billing links now open the in-app Pricing page.

Your balance, chat costs and automation budgets are now shown in credits (1 cent = 2 credits). Plan prices and checkout totals stay in US dollars.

You can now rename any chat from the sidebar.

Automations can now start from Stripe webhook events. When you set one up, provide the endpoint's signing secret from your Stripe dashboard (it starts with whsec_, not an API key) so Quaso can verify each delivery.

Hold the mic button (or hold Space in an empty message box) to talk, then let go to add the transcript to your message. Tap the mic instead to record hands-free. Voice input is available on Pro and Custom plans.

You can now upload a SKILL.md file of reusable instructions to your workspace from the Skills dialog. Type / in the message box to pick a skill, and Quaso loads its instructions for that request.

You can now paste an image from your clipboard into the message box, and it is attached just like an uploaded file.

On small screens, a menu button now opens the full sidebar with your workspaces, chats and automations, and the browser panel opens full screen. Logged-out pages also get a menu with Learn and Pricing.

Clicking Stop now halts the response immediately instead of leaving the chat busy for several seconds. The run also stops on the server right away, so it no longer keeps working after you stop it.

Quaso and your deployed functions can now save values and files that persist between runs. This lets automations remember what they already processed, and Quaso can send you files as download links in the chat. You can review or delete stored items under Settings > Storage. Limits are 256 KB per value and 4 MB per file.

The Automations page (renamed from My Automations in the sidebar) now opens with a 14-day chart of runs and errors, plus when the last run happened. Hover a day to see how its runs split between agents and functions.

Uninstalling the Slack app or revoking its access now fully disconnects it, so reconnecting starts clean instead of looking connected while every action fails. Quaso also no longer starts a second run when Slack resends the same message.

The Triggers column now lists each function's schedules and webhooks, and paused triggers are dimmed. For webhook agents, the agent page gives you a ready-to-copy curl command, so you can fire them from an external scheduler.

Scheduled triggers now run on time, and webhook-triggered functions no longer drop events after a brief network error. If an automation had missed its schedule, it now runs as expected with no changes on your side.

Functions running on a schedule or webhook can now post to a Slack channel, not just send email. Once Slack is connected to the workspace, any member's automations can post to its channels.

Timestamps across chats, automations, run history and settings, along with cron schedules, now display in your local timezone instead of mixing time zones.

The model picker now offers GPT-5.5 (the new default), GLM 5.1 and DeepSeek V4 Pro. GPT-5.4, GPT-5.3 Codex and Haiku 4.5 are retired, and chats that used them switch to a current model automatically.

Settings now has a Billing section that lists your subscription charges and top-ups, with a receipt link for each payment. The usage view also shows your current plan and remaining balances more clearly.

Quaso is an agent that gets work done in your apps. Describe a task in chat and it connects the tools it needs, drives a real browser where there is no API, and can keep running as an automation on a schedule or trigger.

It comes with a guide at quaso.ai/learn, plans and credit top-ups at quaso.ai/pricing, and a Slack app so you can hand it work from a channel.

You can now send Quaso a direct message in Slack instead of mentioning it in a channel.