Release Notes
See what has changed in Backbuild and how it helps your work.
Releases from the 7 days up to Nov 2, 2026, newest first.
November 1, 2026
2026.11.01-PM.1
Improved
- Keeping your account and your organization's work protected matters every day. Improved account security.
Fixed
- Videos could fail to render when you selected your organization's own voice or transcription account in Studio. Studio, in Early access, now lets those videos render with the accounts you selected.
November 1, 2026
2026.11.01-AM.1
New
- Teams that publish videos on YouTube had no way to connect their channel to Backbuild, so their videos and their channel lived in separate places. Marketing, now in Early access, has a Channels page where a guided setup takes you through connecting your organization's YouTube channel and tells you when the connection is confirmed. Open Settings, choose Early access and turn on Marketing, then open Marketing and choose Channels.
- Getting a finished video published meant downloading it, uploading it again somewhere else and chasing sign-off by message. You can now prepare posts from your Studio videos, send them for approval, and publish an approved post to your connected YouTube channel right away or at a time you choose, using Backbuild's MCP tools.
Fixed
- Buying one of the paid Science plans could have failed at checkout. The Science Individual, Science Team and Science Business plans can now be bought at checkout, billed monthly or annually.
- Checkout for a plan sold with a minimum number of seats could have let you start an order that the plan does not allow. Checkout now starts at the plan's minimum number of seats, so the order you place is one the plan supports.
- After you changed and synced the price of a plan you sell, buyers could have kept seeing the old price for a while. Price changes you sync are now reflected in the prices buyers see.
- AI browser control could have stopped responding after the Backbuild Browser Extension reconnected. AI browser control now keeps working when the extension reconnects.
October 31, 2026
2026.10.31-PM.1
New
- Teams that move tickets through a set process, from intake through the work to release, had no place to lay out those stages, so it was hard to see where each ticket stood. Workflows and stages, in the Tickets menu, lets you place each workflow's states into stages, start from a ready-made set of seven, and see them as a list or a graph. Publishing waits until every state has a stage and names any that are missing, and a published change applies to new tickets while existing tickets keep the stages they started with.
Improved
- Your Stripe Connect profiles were folded into another settings page, so they were hard to find. Stripe Connect profiles now have their own page in Settings, with a link to it from Integrations.
- The API keys you create need dependable protection. Protections around the API keys you create have been strengthened.
October 31, 2026
2026.10.31-AM.3
Fixed
- A plan that includes monthly credits could have failed to add those credits to your account. Your plan's included credits now arrive every month once your payment goes through, on monthly, annual and prepaid plans alike.
- When an AI request was refused because your remaining credits could not be used for AI, the refusal did not say why. The refusal now explains that your available credits cannot be used for AI, so you know what to add or change.
October 30, 2026
2026.10.30-PM.1
Improved
- The desktop app connects to your Backbuild account and needs dependable protection. Security protections in the desktop app have been strengthened.
Fixed
- Buying a credit pack could take your payment without adding the credits to your balance, and a card payment that went through on a second attempt could leave the purchase stuck. Credit packs you pay for are now added to your balance, including when your payment succeeds on a later attempt.
- When a virtual worker could not start on budget containers, the start failed with an unexplained error, so you could not tell what to change. You now see a clear message saying why the virtual worker could not start, so you know what to do next.
October 28, 2026
2026.10.28-PM.1
Improved
- The AI provider keys you connect to Backbuild need dependable protection. Protections for the AI provider keys you connect have been strengthened.
Fixed
- When you turned a purchase order into a bill and supplied an empty date, the empty value could be quietly replaced instead of being flagged. An empty date is now refused with a clear message, so you can enter the date you meant.
- Permanently deleting a project from the trash could fail with a permission error, even for someone allowed to delete it. Permanent deletion of a trashed project now completes for the people allowed to do it.
October 28, 2026
2026.10.28-PM.2
Fixed
- When a virtual worker finished a pipeline stage inside the app, it posted its work but the ticket could stay stuck on that stage instead of moving on. Completed stages now move the ticket on to the next stage of its pipeline.
October 28, 2026
2026.10.28-AM.1
Improved
- Your email needs dependable protection. Backbuild Mail's protections for your messages have been strengthened.
October 28, 2026
2026.10.28-AM.2
Improved
- In the side navigation, only the small icon lit up for the page you were on, and the items sat tightly together. Now the whole item, icon and label, is highlighted, and the items have more room between them.
- On a phone or tablet, the buttons and switches in menus such as your profile, organization and quick actions were small and easy to miss. They are now large enough to tap comfortably, and the profile switches are easier to click with a mouse too.
- Your account needs dependable protection. Account security has been strengthened.
Fixed
- On a phone or a narrow window, Mail could be hard to use: Compose and your folders were out of reach, and two header bars could stack on top of each other. Mail now shows one header bar at every screen size, Compose and your folders are always within reach, and the mailbox switcher is easy to tap.
- On a phone, the project picker sometimes didn't open, or was hard to use from the keyboard. It now opens when you tap it, its buttons are easy to tap, and it works as you'd expect from the keyboard.
October 28, 2026
2026.10.28-AM.3
Improved
- When you connected an AI assistant to Backbuild, its tools sometimes called an app by a shortened name that didn't match what you see in Backbuild. The assistant's tools now use each app's full name, such as Backbuild Sheets and Backbuild Docs.
- Your account needs dependable protection. Account security has been strengthened.
October 27, 2026
2026.10.27-PM.2
New
- Mail had no Reply all, did not show who else a message went to, and you could not add Cc or Bcc recipients. You can now reply to everyone on a message, see its recipients, and add Cc and Bcc when you write.
Improved
- Your Stripe accounts were spread across several screens, with no single place to see which one your organization uses by default. Integrations now lists every Stripe account in one place, with its default badge, webhook state and the package environments it serves. You can make any account the default, and an organization with one account has it as its default. Keys still to be linked are listed with what to do. Open Settings, choose Integrations under your organization, and find Stripe accounts above the other providers.
- Your account and your organization's data need dependable protection. Account security and the protections around your organization's data have been strengthened.
- Every API key you created could do everything your role allows, even when a tool needed far less. When you create a key you can now choose Full access, MCP access or Custom scopes. A key with custom scopes can do only what its tool needs. In Settings, open API Keys, choose Create Key, and pick Access.
- The sidebar took a lot of room on the screen. Navigation is now a compact rail of icons with short labels. Open the menu to expand it, and Backbuild remembers your choice.
- Backbuild Mail's inbox and reading view were harder to scan than the email apps people use every day. The inbox, reading view, header, folder list and toolbar have a cleaner layout. New mailboxes open each message in full, and you can still choose a reading pane in Mail's settings.
- Custom themes could not color the navigation rail, Mail or borders. Theme Builder now offers colors for them, with matching defaults in the built-in themes.
- The pricing page first showed prices for a five-year prepaid term, making monthly plans harder to compare. It now opens on monthly billing, and you can still compare every billing term.
Fixed
- Every new account showed a red Out of credits warning before it had ever used or bought credits. The warning now appears only when an organization that has had credits runs out.
- A workflow stage handed to a virtual worker could count as done, and move the ticket on, when the worker left only a blank summary. A stage now completes only when the worker leaves real output. Otherwise it is marked as making no progress and the ticket stays where it is.
- The Assistant could answer with a different model than the one you picked, without telling you. It now tells you when the model you picked is not available to your organization.
- Testing a single sign-on connection could report Connection OK even when a required check had failed. The test now reports an error and says which check failed.
- A bank or store transaction that arrived without an amount could be booked as zero, so reconciliation looked balanced when it was not. Such a transaction is no longer booked, and the sync reports the problem instead.
- Some screens showed an empty or partial result when loading had failed, such as your profile in Settings or the visibility choices for skills. An update to linked Secrets entries could also report success before it had finished. These now report the failure so you can try again, and nothing is shown or saved as if it had worked.
- In Files, at laptop widths, the details column covered the Add File and Add Document buttons. The toolbar buttons now wrap so every button stays visible.
- In SaaS Builder revenue reports, a plan billed only yearly showed its whole yearly price as monthly recurring revenue. It now counts one twelfth of the yearly price each month.
October 27, 2026, 12:52 UTC
2026.10.27-AM.1
New
- A virtual worker had one name for everything. The name your team uses to tell workers apart was also the name people outside your organization saw. Each worker now has an internal name, unique in your organization and shown in your worker list, tickets and dashboard. Its identity name is what people outside your organization see in its replies and inbox. A new inbox sends as the identity name unless you give it another sender name. Set both names when you hire a worker, or later in Configure under Identity.
Improved
- Linking a Stripe account refused a restricted key, so you had to link a key with full access to the account. A Stripe key link now accepts restricted keys, live or test.
- Unlocking Secrets or opening a vault with many entries could take several seconds. Vaults now open and save noticeably faster.
- Your integrations, custom tools and financial records need dependable protection. Protections for them have been strengthened. Setting up an integration or a custom tool from your AI tools now asks for its sign-in details in their own fields.
Fixed
- If two of your virtual workers had the same name, it was hard to tell them apart in lists and tickets. Each worker in your organization now has its own internal name. If two shared a name, one has been renamed, and your organization was told which.
- The welcome tour created your first virtual worker but ended without activating it, so Chat showed no worker. The tour now ends on your new worker's page, where Activate worker explains what it does, and that page fits a phone screen.
- Some HTML email in Backbuild Mail did not display as its sender designed it, and buttons such as a sign-in button could be invisible. HTML email now displays as designed, including its buttons.
- Your tickets list could not create a ticket, and its empty view said everything was closed. The sidebar's quick action sent a support ticket to Backbuild instead. New ticket, in the toolbar and the empty view, now creates a ticket in one of your organization's projects. The quick action now reads Contact support, and a link to a ticket opens that ticket.
- A project opened from a link showed a long identifier instead of its name in the breadcrumb, and the Docs area was labelled Bbdocs. The breadcrumb now shows the project's name, and the Docs area is labelled Docs.
- Setting up Secrets for the first time could take very long or give up. First-time setup now completes reliably.
- When a virtual worker ran a workflow stage in a container, its output went to the person who raised the ticket as a public reply. Stage output now arrives as an internal draft for your team, as it does when the stage runs in the app.
- Set up webhook failed for live Stripe accounts, and it could replace a webhook your organization had made itself. It now works for live accounts, and a webhook you made yourself is kept.
- A subscription your customer had left unpaid or incomplete in your Stripe account could show in Backbuild as past due or active. It now shows as unpaid or incomplete, and a search for unpaid subscriptions finds it.
- Managing a custom tool's variables and sign-in details from your AI tools was refused for everyone. It now works for people allowed to manage tools.
- Once an invoice, bill or other document number grew past its set number of digits, its leading digits could be cut off. Document numbers now keep every digit.
October 27, 2026, 08:07 UTC
2026.10.26-AM.7
New
- Expenses could not carry a class, so a profit and loss for one property, job or division left them out. You can now tag an expense with a class, and the expense then shows in that class's profit and loss. In Finances, open Expenses and choose a class when you add an expense.
Improved
- Your virtual workers and the repositories they work on need dependable protection. Protections for your virtual workers and the repositories they work on have been strengthened.
Fixed
- A container that never finished starting could still use your credits. A container that never becomes ready now uses none of your credits.
- When a virtual worker had no GitHub connection linked, its repository checkout failed without saying why. The checkout now says that no GitHub connection is linked to the worker, so you know what to connect.
- Your organization's AI model policy could be saved with a model your organization cannot use, and the work then ran on a different model. Saving the policy now refuses a model your organization cannot use and names it, so nothing changes until you choose one that is available.
October 26, 2026, 23:09 UTC
2026.10.26-AM.6
New
- You could not try a new feature before its general release, even when your team wanted it early. Settings now has an Early access page. Organization owners and administrators can choose, feature by feature, to try features before their general release, after accepting a short notice. Open Settings and choose Early access.
Improved
- When a virtual worker had queued work it was not starting, nothing told you why. Work waiting for working hours or budget could stay stuck, and a stage short of credits never said why it had not started. The worker's Overview now says why queued work is waiting, such as no working hours or a reached budget, and what to change. Waiting work now starts on its own once it can, and a stage waiting for credits says so on its ticket.
- During a virtual worker's working hours, a container with nothing to do kept running and using your credits. Unless you have chosen to keep one ready, a container with no work now stops after your organization's idle time. Your worker starts a new one when work arrives.
- Connecting your SMS and voice provider asked for a phone number it never used. You also had to test the connection yourself to know it worked. The form now asks only for the account details your provider needs, with an API key offered first where supported. It shows whether the connection works as soon as you save it. Open Settings, choose Integrations under your organization, and connect your provider.
- In Remote Hosts and SSH keys, and when a change needed your Secrets vault unlocked, Backbuild showed a message instead of asking you to confirm. Unlocking the vault could also show a Verify button that did nothing. These now open the confirmation or the vault unlock right where you are, and your change finishes once you complete it.
- When a request from your AI tools or the API needed a person to confirm it, the refusal did not say where to do that. The refusal now includes the Backbuild address, where a person can finish the action.
- Your virtual workers and the accounts they connect to need dependable protection. Protections for your virtual workers and the accounts they connect to have been strengthened.
Fixed
- In a workflow that uses your own status categories, creating or moving tickets could fail. States added through the API also lost their category, so a final state did not count as final. Tickets now work in workflows with your own categories, and states added through the API keep the category you give them.
- A virtual worker could still do, and charge for, stage work on a ticket that had already moved on or been deleted. That work is now canceled, so nothing is charged and the ticket stays where you left it.
- A workflow stage handed to a virtual worker could sit without ever running, or finish without leaving the worker's note on the ticket. Those stages now run, and the worker's note appears on the ticket when the stage is done.
- A virtual worker could run on a different AI model than the one you chose, without telling you. The worker now uses the model you chose, or stops the task and tells you why, so you can choose another.
- A virtual worker task that stopped before it reached the AI model could stay marked as running, with credits set aside that blocked other work. It no longer stays marked as running, and the credits set aside for it are free again much sooner.
- When a virtual worker's request failed before the AI model did any work, the full amount set aside could still come out of your credits. The credits set aside for those requests now go back to your balance.
- Starting a virtual worker's container without enough credits showed a server error instead of the reason. It now tells you plainly that there are not enough credits, so you know why it did not start.
- A virtual worker created through the API or MCP had no working hours, so it never picked up any work. New workers now start with weekday working hours that you can change, so they pick up work during those hours. A time zone name Backbuild does not recognize is now refused instead of saved.
- Saving your organization's container run locations with every location allowed was refused, and so was saving sizes for each run location. Both now save as you set them.
- A linked copy of a Secrets entry showed as Linked entry instead of its name. Edits and renames to the original never reached its copies. Linked copies now show the original's name, and changes to the original reach its copies.
- Testing the key for one of the AI providers your organization can connect could not confirm whether the key worked. The test now confirms the key works and shows the spending allowance set on it and the amount already used, without using any of it.
- After you connected GitHub with access to selected repositories, a virtual worker's GitHub card could list none of them. Connections you make now list the repositories you chose.
- Prove setup told you to install a command-line package that could not be installed. Setup now tells you that the Backbuild command-line tool is already installed in every Backbuild container.