> ## Content Index
> Fetch the complete content index at: https://itsfoss.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# No AI Slops! GNOME Now Forbids Vibe Coded Extensions
- URL: https://itsfoss.com/news/no-ai-extension-gnome/
- Published: 2025-12-15T06:50:21.000Z
- Updated: 2025-12-15T06:50:21.000Z
- Description: New policy targets low-quality AI-generated code while still allowing AI as a learning tool.
- Author: Sourav Rudra
- Tags: News

[Shell Extensions](https://extensions.gnome.org/?ref=itsfoss.com) are one of the best things about using GNOME. They let you customize your desktop exactly how you want it. I personally use quite a few to keep my workflow streamlined.

*If you are new to this, then we have a detailed guide on* [*using GNOME extensions*](https://itsfoss.com/gnome-shell-extensions/) *that covers the basics.*

However, **maintaining the extension ecosystem isn't easy**. The GNOME extensions team reviews every submission for issues and malicious code, a time-consuming process that's gotten harder lately thanks to [AI slop](https://en.wikipedia.org/wiki/AI%5Fslop?ref=itsfoss.com).

## AI Slop is Not Welcome

GNOME has updated its [extension review guidelines](https://gjs.guide/extensions/review-guidelines/review-guidelines.html?ref=itsfoss.com#extensions-must-not-be-ai-generated) to reject AI-generated code. The new rule states that submissions with clear signs of AI generation will not be approved.

[This change](https://blogs.gnome.org/jrahmatzadeh/2025/12/06/ai-and-gnome-shell-extensions/?ref=itsfoss.com) comes after the team noticed a surge in extensions with unnecessary code patterns. [Javad Rahmatzadeh](https://wiki.gnome.org/jrahmatzadeh.html?ref=itsfoss.com), who reviews extensions for GNOME, mentioned **spending over 6 hours some days** reviewing more than 15,000 lines of code.

During all that, he found out that **unnecessary try-catch blocks were appearing in many new extensions**. When he asked the developers about it, they confirmed it was the result of AI usage.

The updated review guidelines now list what will trigger rejection: large amounts of unnecessary code, inconsistent code style, imaginary API usage, comments serving as LLM prompts, and any other indication that the code is AI-generated.

And, to be clear, **using AI as a learning tool or for code completions is still allowed**. The policy targets developers who generate entire extensions without understanding the code.

This isn't something new. Many projects [are taking steps](https://itsfoss.com/news/fedora-ai-guidelines/) to prevent AI slop from overwhelming existing systems. GNOME's approach is actually really good.

Many new developers are increasingly relying on AI-powered tools to learn, and a [blanket ban](https://en.wiktionary.org/wiki/blanket%5Fban?ref=itsfoss.com) wouldn't really be constructive, if you ask me.

Via: [Phoronix](https://www.phoronix.com/news/GNOME-Extensions-Block-AI?ref=itsfoss.com)

**Suggested Read 📖**: *Btw,* [*Tiling Shell*](https://itsfoss.com/news/tiling-shell-gnome-extension/) *is my favorite GNOME shell extension.*

[Tiling Shell: A GNOME Extension to Add Superpowers to UbuntuA nifty GNOME extension to maximize productivity.![](https://itsfoss.com/content/images/icon/android-chrome-512x512-114.png)It's FOSSSourav Rudra![](https://itsfoss.com/content/images/thumbnail/tiling-shell-first-look-1.png)](https://itsfoss.com/news/tiling-shell-gnome-extension/)