Your Next Laptop Might Have Dedicated AI Keys, and Google Is Behind the Whole Thing

Key Takeaways

• Linux 7.0 now supports three new AI-specific keycodes: Action on Selection, Contextual Insertion, and Contextual Query
• Google wrote both the USB HID specification and the Linux kernel patch for these new keys
• Unlike Microsoft's Copilot key (which is just a keyboard shortcut hack), these are proper first-class HID values
• Expect to see dedicated AI agent keys on upcoming laptops from multiple manufacturers

So here's something that flew under the radar this week. The Linux 7.0 kernel quietly merged support for three completely new keyboard keys, and they're all about AI. We're not talking about another Copilot button clone. These are purpose-built keycodes that could fundamentally change how you interact with AI assistants on your computer.

And the kicker? Google is behind the entire thing. They authored both the USB HID specification proposal AND the kernel patch that wires these new codes into Linux. When one of the biggest tech companies on the planet pushes through hardware-level changes like this, you pay attention.

What Are These Three New AI Keys?

Let's break down what we're actually looking at here. The Linux kernel now recognizes three new keycodes that arrived through the HID fixes pull request for version 7.0:

• KEY_ACTION_ON_SELECTION (0x254) — Triggers an AI action on whatever you currently have selected
• KEY_CONTEXTUAL_INSERT (0x255) — Lets AI insert content based on your current context
• KEY_CONTEXTUAL_QUERY (0x256) — Fires off an AI query related to what you're working on

These aren't random additions. They're now officially part of the USB HID Application Launch usage page, which means hardware manufacturers can start building keyboards and laptops with dedicated physical keys for these functions. This went through the proper USB-IF specification process. It's legit.

Why This Is Actually a Big Deal

Look, I know what you're thinking. We already have the Copilot key on newer Windows laptops. Why do we need more AI buttons?

Here's the thing. That Copilot key? It's basically a lie. A clever hack, sure, but still a hack. Back in 2024, people figured out that the Copilot button doesn't actually send a new scan code at all. It reports as Left Shift + Windows + F23. Yeah, F23. That's a function key from 1980s IBM keyboards that Microsoft's firmware just repurposed. It's the tech equivalent of duct tape.

These new Google-backed keycodes are completely different. The 0x254, 0x255, and 0x256 entries are first-class HID values that operating systems can map directly. No workarounds. No pretending to be something else. Real, legitimate keyboard codes that the entire industry can standardize around.

Google's Fingerprints Are Everywhere

I find it fascinating that Google authored both sides of this equation. They wrote the HID specification proposal that got these codes approved by the USB standards body. Then they wrote the actual kernel patch that implements support in Linux. That's controlling the conversation from hardware spec to software implementation.

This makes total sense when you think about it. Google has been pushing hard on AI integration across Chrome OS, Android, and their cloud services. Having standardized keyboard shortcuts that work across every operating system and every hardware manufacturer? That's exactly the kind of infrastructure play Google loves to make.

What Each Key Actually Does

Based on the descriptions in the kernel patch, here's what these keys are designed for:

Action on Selection is probably the most straightforward. Select some text, hit the key, and your AI assistant does something with it. Summarize it. Translate it. Rewrite it. The specific action would depend on your software and settings, but the key itself just says "hey, do an AI thing with whatever I've highlighted."

Contextual Insertion is interesting. This seems designed for moments when you want AI to generate content that fits naturally into what you're already doing. Writing an email and need a professional closing? Working on code and want an AI-generated function? Hit the key and it inserts something contextually appropriate.

Contextual Query lets you ask questions about your current work without switching contexts. You're reading a dense technical document, hit this key, and ask what a specific term means. The AI knows what you're looking at and can give you a relevant answer.

When Will You Actually See These Keys?

That's the million dollar question, isn't it? The kernel support is there as of Linux 7.0. Phoronix reported this alongside the recent news about Intel Nova Lake and AMD Zen 6 enablement in the same kernel release, so we're talking about hardware that's coming in the next generation of laptops.

Manufacturers now have everything they need to start building keyboards with these dedicated AI keys. The USB spec is approved. Linux supports it. Windows will almost certainly follow (Microsoft isn't going to let Google get ahead on AI hardware integration). And since Google pushed this through, you can bet Chrome OS will have day-one support.

My guess? We'll start seeing laptops with these keys announced at CES 2027. Maybe some early adopter models before the end of this year from manufacturers who want to claim "first."

The Bigger Picture Here

What we're witnessing is AI moving from software feature to hardware assumption. Three years ago, nobody had an AI key on their keyboard. Two years ago, Microsoft slapped a Copilot button on some laptops using a decades-old hack. Now we have proper, standardized keyboard codes for multiple AI interactions.

Google positioning themselves at the center of this standardization effort is smart. They're not selling keyboards. They're making sure that when AI hardware becomes ubiquitous, it works seamlessly with their services and platforms.

Should You Care?

Honestly? Yes. But not because you need to rush out and buy anything right now.

These keys represent where the entire industry is heading. AI interaction is becoming so fundamental to how we use computers that it's getting baked into the hardware layer. That's a significant shift. Five years from now, keyboards without AI keys might feel as dated as keyboards without a Windows key feel today.

For Linux users specifically, this is great news. You'll have first-class support for these keys from day one. No waiting for driver updates or hoping someone writes a workaround. The kernel already knows what to do with them.

Frequently Asked Questions

Will these keys work on Windows?

Almost certainly yes, once Windows adds support. Microsoft won't want to fall behind on AI hardware integration.

Can I remap my existing keyboard to use these functions?

Theoretically yes, once software supports the keycodes. You could map unused keys to send these codes.

Is this a Google-only thing?

No. These are open USB HID standards. Any manufacturer can use them, and any OS can support them.

When will laptops with these keys be available?

Likely late 2026 for early adopters, with widespread availability expected around CES 2027.

The future of your keyboard has three new buttons, and they're all about making AI a one-keypress interaction. Whether that sounds exciting or dystopian probably depends on how you feel about AI in general. But either way, it's coming.

Sources & Credits

Originally reported by Latest from Tom's Hardware