Release Notes for Nov 2 to Nov 8, 2026

See the latest release notes

November 7, 2026

2026.11.07-PM.1

Improved

  • When you lock your vault, you need to know the lock went through. If Backbuild cannot confirm the lock, your vault now tells you so and offers Lock again. If you see that notice, choose Lock again.
  • Sessions for your virtual workers, the AI assistant and your containers work with your code and your data, so they need dependable protection. Protections for these sessions have been strengthened.
  • Your account needs dependable protection. Account security has been improved.

Fixed

  • Some actions ask you to confirm it's you, such as setting your vault's master password. With no second factor that could confirm it, you could have been stuck with no way to add one. Backbuild now helps you add one, such as this device, an authenticator app or a security key. Then it finishes what you started.
  • During sign-up, choosing email codes as your second factor could have stopped sign-up before it finished. Sign-up now offers this device, an authenticator app or a security key, and you can finish sign-up with any of them.
  • Adding a second factor, such as an authenticator app, could have signed you out before you finished setting it up. You now stay signed in while you add or change a second factor.
  • On a phone, some buttons and fields on the sign-in, vault and two-factor screens were small and easy to miss. Some content could also run off the edge of the screen. They are now larger and easier to tap, and that content now fits on the screen.
  • Some members whose role includes the Early Access Management permission, such as a custom role, could have been refused when changing Early access. Anyone whose role includes that permission can now choose which features to try early in Settings, Early access. Owners and administrators have it by default, and you can add it to a custom role. If you are refused, the message names the permission you need.
  • In Finances, Estimates could have said you had no estimates or customers yet when it could not load your data. It now tells you that your data could not be loaded, and says the list is empty only when it is.
  • On a phone, the Estimates list could have drawn its columns on top of each other, with its buttons running into the total. The account list for an estimate line could also open too narrow to read. Each estimate now shows as a card with its buttons on their own row, and the account list opens wide enough to read.
  • A session for a virtual worker, the AI assistant or a container could have lost its access to your data soon after it started, and a virtual worker's session could also have lost its access to your code repository. The work in that session could have stopped partway. These sessions now keep their access for as long as they run. A session that started before this release could still lose its access. Its next session works as expected.
  • When a virtual worker could not reach its code repository, its output could have said the repository link was revoked, even though the link was still in place. That could have sent you to relink a repository that needed nothing. The message now says what actually stopped the worker, and it says the link was revoked only when it was.
  • In Email, a message you reported as spam could have stayed in your Inbox until you refreshed, even though it already showed in Spam. Archiving, moving or deleting a message, or marking it as not spam, could have left it in the list too. The message now leaves the list as soon as the change is saved, and the folder counts update with it. Your other devices with that folder open show the change the next time they load it.
  • Sometimes Email cannot move, report or delete a message. When that happened, Email could have shown no error at all, or moved on to the next message as if the change had worked. The message now stays where it is, and Email tells you the change did not go through. The message you had open stays open.
  • The icon buttons in Email, such as Report spam, Delete and Archive, showed no name when you pointed at them. You had to guess what each one did. Every icon button in Email now shows its name when you hover over it or reach it with the keyboard. On a touch screen, press and hold a button to see its name without using it.
  • Hover labels across Backbuild could have appeared in a different typeface from the rest of the screen. They now use the same typeface as the text around them.
  • On a phone, the buttons above an open email were small and easy to miss. They are now larger and easier to tap.
  • On a virtual worker's Configure tab, the GitHub section could have asked you to bind a vault in step 4. That could happen even when the worker already had one, while its vault was still loading or could not be loaded. The section now shows that the vault is loading. If it cannot be loaded, you see an error with a button to try again. It asks you to bind a vault in step 4 only when the worker has none.
  • In Settings, under Administration, Integrations, the GitHub App panel could have told you to install the App on a worker from a tab that does not offer it. It now points you to the GitHub section of the worker's Configure tab, where Link a new GitHub account lets you pick the repositories the worker may use.
  • Some AI use in features such as AI Testing and Finances could have been left out of your organization's daily AI spend cap. The cap could then have let more AI use through than the amount you set. Your daily AI spend cap now counts that AI use too.

November 5, 2026

2026.11.05-PM.1

Improved

  • Approving a connection to your Secrets vault gave you no last look at exactly what the machine would receive. After you choose Authorize, a Confirm this grant step now shows the access level, vault, expiry, service and machine. Choose Confirm and authorize to grant it, or Back to change your choices.
  • Your Secrets vault holds sensitive information and needs dependable protection. Protections in Backbuild Secrets have been strengthened.
  • AI browser control works on the sites you allow, so it needs dependable protection. Protections in AI browser control have been strengthened in version 0.3.0 of the Backbuild browser extension.
  • Your organization's GitHub App cannot be installed on a GitHub account other than its own. A virtual worker using a repository there had no way forward. The worker's GitHub section now explains this. It suggests forking or mirroring the repository into your App's account, then linking the copy to the project.
  • Your account and your virtual workers need dependable protection. Protections for your account and your virtual workers have been strengthened.

Fixed

  • Approving a connection to your Secrets vault could have been hard on a phone or with a keyboard. Some identity check buttons were small, and fields showed no keyboard focus. Those controls are now easier to tap, and the field you are typing in is clearly highlighted.
  • In Remote Hosts, a host name you typed before the host reported in could have been replaced by the host's own label. The name you type now stays, and Approve host saves the host with that name.
  • When a virtual worker could not reach its GitHub repository, the link in its output could have opened your home page instead of that worker. The link now opens the worker's GitHub section at This worker cannot reach its repository, with the choices that give the worker access.
  • A virtual worker's GitHub section could have shown Linked for a personal GitHub connection that the worker cannot use to reach its repository. It now says when the worker cannot use that personal connection, and when the worker has no GitHub link at all.
  • You might change your GitHub App's repository access on GitHub, or install the App from GitHub itself. Returning could have shown Install failed, although GitHub saved your change. You now see Back from GitHub, with a prompt to return to Backbuild to continue.
  • Some GitHub App messages could have sent you looking for a button that is not there. With no App yet, linking a worker said only to create it first. These messages now point to Create GitHub App in Settings, under Administration, Integrations. After you create the App, they point to Link a new GitHub account on the worker's Configure tab.
  • Choosing Create another for your organization's GitHub App could have replaced the App your virtual workers use. Those workers could then have stopped being able to use git. While a worker is linked through the App, Create another is unavailable and says how many workers use it. To replace the App, unlink GitHub on those workers first.

November 5, 2026

2026.11.05-AM.1

Improved

  • Your account, and the work virtual workers do in your code repositories, need dependable protection. Account security, and the protections around virtual workers' access to your connected code repositories, have been strengthened. To let a virtual worker work in your code repositories, link it with your organization's GitHub App. Open the GitHub section on the worker's Configure tab. Choose Use the existing GitHub installation for this worker, or Link a new GitHub account. If your organization has no GitHub App yet, create it first with Create GitHub App in Settings, under Administration, Integrations.

Fixed

  • When you moved a stage in a workflow, or the stages reloaded in a new order, the stage editor could have switched to another stage. The stage editor now keeps showing the stage you were viewing, wherever it moves in the list.
  • After you paused a virtual worker, its page could have shown it as running with no busy slots. It also offered Resume worker, so it was hard to tell whether it was still working. A paused virtual worker now says it is paused and takes no new work, and shows whether a session is still running, finishing or starting. When its state cannot be confirmed, the page says so and Start stays unavailable.
  • On a phone, some controls at the top of a virtual worker's page, such as Fire worker, could run off the edge of the screen. The controls now wrap onto the next line, so every one of them stays in view and can be tapped.
  • If a deployment could not get your code from its repository, it could have failed without saying why. It now tells you the reason in the run's log in Build & Deploy. For example, signing in to the repository failed, or the repository could not be reached.

November 4, 2026

2026.11.04-AM.1

Improved

  • On a phone, the Studio editors could feel cramped. Headers crowded together, some buttons and tabs were hard to tap, and the Training tools panel could cover the editor. The Studio editors now fit a phone or tablet screen. Headers wrap neatly, every control is easy to tap, and the Training tools panel stays closed until you open it.
  • In the Studio Video editor, the timeline could be hard to scroll on smaller screens. Track names and the time ruler could scroll out of view, and the format buttons could cover the picture. The tracks now scroll in every direction with their names and the time ruler always in view. The picture stays whole, its format buttons are easy to use, and the editor keeps your place when the window changes size.
  • When a Remote Desktop session showed an error, its buttons were small on touch screens. Pressing Tab could also move the keyboard to the page behind the message. Remote Desktop error messages now have buttons that are easy to tap, and the keyboard stays on the message until you choose what to do.
  • Your account and your organization's data need dependable protection. Account security and the protections around your organization's data have been strengthened.

Fixed

  • If a Studio editor or page could not load your work, it could have opened empty. Saving from there could have replaced your script, actions or other content with an empty or older copy. Studio, in Early access, now tells you when something couldn't load and offers Try again, and your saved work stays as it was.
  • The Studio auto-captions dialogs could not be closed with the Escape key, and pressing Tab could move the keyboard behind them. They now close when you press Escape, and the keyboard stays inside the dialog while it is open.
  • If someone else deleted the stage you had open in a workflow, the stage editor could have kept showing that stage's details. The editor now clears a deleted stage, so what you see always matches the workflow's list of stages.
  • During a brief service problem, requests made with a valid API key could have been told the key was invalid. The Backbuild CLI could also have said its access had expired or been revoked. They are now told the service is temporarily unavailable, so you can simply try again. Your key and its access are not affected.

November 3, 2026

2026.11.03-AM.1

Improved

  • In the Studio editors, the menus in the menu bar and the items inside them were small and hard to tap. A long menu could also be cut off at the bottom of the screen, leaving its last items out of reach. Every menu and menu item is now easy to tap or click, and a long menu scrolls within your screen so every item stays reachable.

Fixed

  • A Studio project's production, actions and timeline pages could have opened blank after a refresh or from a shared link or bookmark. Studio, in Early access, now shows those pages however you open them.
  • Those Studio pages could have shown plain, unformatted text with buttons too small to tap. On a phone or tablet, an actions table could also make the page wider than the screen, so it scrolled sideways. Those pages now look like the rest of Backbuild, with buttons and links that are easy to tap. Each page stays within your screen on any device.

November 2, 2026

2026.11.02-PM.1

Reliability and performance improvements.

November 2, 2026

2026.11.02-AM.1

Fixed

  • Over time, some actions could start to slow down or fail. Those actions now keep working reliably.