Chrome 156 for Googlebook delivers 14 desktop upgrades and a look at what’s coming next

Having the initial batch of Googlebooks on my desk this month has been an exercise in balancing massive hardware potential against early software growing pains. As we have talked about extensively around here lately, Googlebook OS is built on an Android 17 foundation that impresses when it comes to speed and mobile hand-offs, but the Chrome browser itself has been less than stellar when compared to existing Chromebook hardware.

We expected Chrome 156 right at two weeks after Chrome 155 delivered universal web app installations and side-panel extension support, but Chrome 156 for Googlebook was held up nearly a week, leaving many of us wondering where it’s been in the meantime.

Thankfully, Chrome 156 is rolling out via the Google Play Store today. Between the official Googlebook Help Community announcement and a detailed technical breakdown from Google’s Mishaal Rahman over on r/Googlebook, we know that this update packs 14 meaningful improvements alongside a transparent look at the features coming next.

Real desktop workflow upgrades for files, Google Docs, and 1Password

The headline improvements in Chrome 156 target the exact daily friction points that make or break a laptop as a primary work machine. At the top of my list is the arrival of proper “Save As” file dialog support, which finally lets you choose your destination folder and rename files before they hit your local storage.

Alongside that dialog, Google squashed an infuriating naming bug where duplicate downloads appended numbers after the file extension – naming a photo something like image.webp(1) instead of image(1).webp and rendering it un-openable in the Files app. Because the new “Save As” prompt is rolling out gradually on the server side, you can force it on your Googlebook right now by pasting chrome://flags#enable-download-save-as-system-file-dialog into your address bar and enabling the flag.

Power users living inside Google Workspace and third-party password managers are also getting huge relief in this build. Until today, trying to copy multi-page tables, images, or massive blocks of rich text in Google Docs on the web would routinely fail with a clipboard error because the selection exceeded the operating system’s standard buffer limit. Chrome 156 automatically offloads those oversized web clipboard payloads so heavy document editing works without a hitch.

Extension stability has taken a major step forward as well. If you configured your Googlebook to use a third-party autofill service in the system settings, clicking into an input field or typing your master password inside the 1Password extension popup would previously crash the entire browser.

That crash is completely resolved in version 156.0.8078.47, along with a bug where uninstalling extensions like Teleparty (which launch an automatic feedback page upon removal) would crash Chrome and wipe out all of your open windows. Google even patched a specific window-management crash triggered by dragging a tab into a new window, clicking its address bar, and dragging it back while the text cursor was still active.

Smarter keyboard shortcuts, web fixes, and omnibox polish

Desktop keyboard behavior is another area where Chrome 156 feels much closer to ChromeOS, Windows, and macOS. Previously, opening a fullscreen website or cloud gaming web app like GeForce NOW that utilizes keyboard lock would trap all of your keystrokes at the OS level, forcing you to press and hold Esc just to switch tasks. Now, Alt + Tab switches windows seamlessly even when fullscreen keyboard lock is active, unless a site explicitly requests system modifier capture.

Navigating the address bar is noticeably cleaner across the board, too. Pressing Alt + Shift + Enter after typing a query or URL now launches that page in a new background tab at the end of your tab strip while keeping you focused on your current window. When you type a long, multi-line prompt into the address bar or AI Mode box, Chrome now hides the autocomplete dropdown so your Up and Down arrow keys actually move the text cursor between lines instead of jumping into search suggestions.

Beyond keyboard navigation, Google cleaned up several nagging web and UI quirks. Clicking the “X” button on third-party “Sign in with…” prompts now properly dismisses those popups on sites like Reddit, Canva, Pinterest, and The New York Times, and a video decoding fix stops Facebook Live streams from getting stuck in endless buffering loops.

You can also right-click links on the Incognito New Tab Page to access the context menu, site favicons no longer get stuck in the URL bar after clearing text with Esc, and the address bar’s AI Mode menu picks up mouse hover tooltips, smoother expansion animations, dark mode polish, and a cleaner “Add to your search” header when attaching open tabs or files.

A transparent roadmap for multiple profiles, tab group sync, and Cast

As welcome as these 14 updates are, the best part of today’s rollout is the candid roadmap shared in the Reddit community thread. Google explicitly acknowledged three of the biggest missing pieces on Googlebook OS and confirmed that the engineering team is actively building fixes for future bi-weekly releases. Most notably, support for multiple Chrome profiles – easily the most requested feature from longtime Chrome users – is officially in development for a future update, alongside tab group syncing across browser windows and devices.

The team is also working on a permanent fix so local Google Cast devices automatically populate inside Chrome’s Cast menu. Thankfully, you don’t have to wait for Chrome 157 to cast from your browser. You can get local Cast devices showing up right now by opening your Googlebook Settings, navigating to Apps and selecting Chrome, opening Permissions, and manually granting access to Nearby devices (or Local Network).

Seeing Google push out this level of polish just two weeks after M155 while openly sharing flags and workarounds with early adopters is exactly the kind of momentum Googlebook OS needs right now. You can wait for the update to hit your machine automatically over the next few days, or jump straight into the Google Play Store on your Googlebook, search for Chrome, and hit Update to test these upgrades out for yourself.