How I Spent Hours Toggling Flags for Native Gemini on Brunch & the Ultimate Fix

on

How I Spent Hours Toggling Flags for Native Gemini on Brunch (And the Ultimate Facepalm Fix)

If you are running ChromeOS via the Brunch framework and trying to force-enable the new native Gemini desktop companion (the Glic UI panel), let me save you a massive headache. Don't touch your configuration files, don't write scripts, and don't wipe your state until you check one tiny, crucial detail: your system milestone version.

Here is the story of how I went down a command-line rabbit hole, only to realize the answer was staring me in the face the entire time.

The Goal: Native Gemini Live & Desktop Integration

I wanted to get the native desktop Gemini integration running directly on my layout tray to see how it handles real-time conversational features like Gemini Live, alongside its suite of text, image, video, and music generation tools.

The catch with this specific feature is that it is baked directly into the core Chromium system UI layer. Because it is part of the native environment—rather than running as an isolated Linux sandbox container application or a Flatpak package—you can't just download an installer. You have to force the operating system to turn it on using system-level features flags.

The Terminal Rabbit Hole

Naturally, I jumped into the developer terminal to force-inject the necessary arguments. Here is exactly what I ran to try and make it appear:

1. Attempting an Automated Flag Script

At first, we tried passing the feature parameters through an automated flag script, but ChromeOS quickly shut that down with a command-not-found error. Time to do it manually.

2. Remounting the Root Filesystem & Appending Flags

To modify system configurations, I had to remount the root filesystem as writable so the OS would let me edit core files. I ran:

sudo mount -o remount,rw /

Once the system was writable, I targeted the developer configuration file and manually appended the required Gemini companion flags to the bottom of /etc/chrome_dev.conf:

--enable-features=Gatekeeper,Glic,GlicEntrypointVariations

3. Resetting the UI Framework

To force the browser engine to read the new configurations, I restarted the graphical user interface layer directly from the shell:

sudo restart ui

The screen flickered, the desktop reloaded, but... still no Gemini icon on the taskbar.

4. Wiping the Global Application Scratchpad

Thinking the layout was cached, we decided to clear out the global application state scratchpad to force Chrome to rebuild its interface parameters on a completely fresh boot:

sudo rm "/home/chronos/Local State" && sudo restart ui

Even after rebuilding the state file, the interface remained completely unchanged. The button simply refused to exist.

The "Aha!" Moment (Why It Failed)

Exhausted, I pulled the fresh system logs to see why the browser was completely ignoring my configuration lines. That is when the ultimate facepalm happened. As it turns out, Gemini completely overlooked a vital piece of system data I had provided right at the very beginning of our troubleshooting session: my actual ChromeOS build version.

Right there at the top of the log, the system string read:

"onboarding_completed_version":"146.0.7680.169"
  • The Problem: My Brunch installation was firmly pinned to ChromeOS Milestone 146.
  • The Reality: The desktop AI companion framework (#glic) wasn't actually compiled into the upstream Chromium source code until Milestone 147, and the interface assets weren't unified layout-wide until Milestone 148.

No matter how many terminal injections, file permissions modifications, or configuration wipes I threw at it, the visual layout code for the Gemini interface literally did not exist inside my operating system's local binaries yet.

The Real Fix for Brunch Users

If you are trying to get this working on your own setup, stop editing your configuration files and follow these steps instead:

  1. Navigate to Settings -> About ChromeOS and verify your current Milestone version.
  2. If your build is on Milestone 146 or lower, the code is missing. You must update your root system images.
  3. Open your terminal and run the Brunch update engine framework to check for an upgraded release:
sudo brunch-update

Alternatively, you can manually flash a Milestone 148 or higher recovery image matching your device's architecture directly over your current installation partition.

The upside? Because my manual edits to /etc/chrome_dev.conf are already saved to the disk, the exact second my root image updates to a build that actually contains the desktop companion code, the Gemini icon will instantly populate on my taskbar without me having to re-type a single terminal command.

Comments

Post a Comment