Why Google needs to keep Linux support in the new Android-based ‘Aluminium’ project

When we talk about ChromeOS being re-baselined to the Android kernel—known internally as Project “Aluminium”—the conversation almost always revolves around AI. But for a core group of ChromeOS enthusiasts, there is a lingering fear right now: what happens to Linux support?

For years, the ability to run Linux apps has been the secret sauce that allows users to turn a standard Chromebook into a genuine development machine. It’s the primary reason many power users out there can rely on a Chromebook as their full-time computer. So, as we look ahead to this underlying shift to an Android foundation, we have to wonder if Linux will actually make the jump to the new OS.

The legacy ChromeOS split

As we covered earlier this year, Google has confirmed that they are sticking to their 10-year support promise. However, because Project Aluminium has higher technical requirements, not every device will get the new software. Older or budget-friendly Chromebooks that aren’t eligible for the Aluminium update—or devices where users simply choose not to migrate—will continue to run “legacy” ChromeOS until they reach their Auto Update Expiration (AUE).

Because of this split, we already know that Linux support isn’t completely vanishing overnight. If your device stays on legacy ChromeOS, you will still have access to the Linux container just like you do today. But that creates an interesting crossroads for Google.

Why leaving developers behind is a mistake

It would be incredibly easy for Google to just cut Linux development on the new Aluminium stack entirely. From a purely business standpoint, you could argue they should leave Linux on the legacy software and focus all their new resources on the general consumer and the integration of AI features.

But I think that would be a massive mistake. Pro users and power users are a vital part of the ChromeOS ecosystem. They are the ones who push the boundaries of what is possible on these machines, discover new workflows, and provide some of the most valuable feedback to the development teams. Forcing them to stay on legacy software just to keep their development environment would essentially punish the platform’s most dedicated fans.

Ever since we first heard about the migration to the Android kernel, there has been a genuine worry that Google might strip away the enthusiast features we’ve grown to love in the name of simplification. Bringing Linux support over to Aluminium wouldn’t just be about keeping a terminal window alive; it would be a clear validation of the entire developer community that has built their daily workflows around this OS.

We don’t have any official confirmation from Google just yet on what the future holds for the Linux container. But by ensuring that the new Android-based project retains the openness and utility of the current platform, Google would send a strong signal that these new Android-powered laptops are still built for everyone. I really hope they see the value in keeping Linux around for the next generation of ChromeOS!

And, look, I know that many of you reading this are in the terminal every day and have a much deeper understanding of the technicalities of Crostini and Linux on Android than I do, so what are your thoughts on all of this? How do you think Google should handle this transition? Are there specific Linux workflows you rely on that absolutely must make the jump to Project Aluminium? Let me know in the comments below!