Nuffing.com

Mac users who don’t want Apple Intelligence to take up precious drive space can free up capacity thanks to a new command-line tool.

Apple Intelligence is generally a good set of features for Apple’s ecosystem of devices. However, not everyone particularly wants to use it.

That is especially a problem for Mac users with small drives and constrained spare capacity. For those stuck with a 256GB SSD, recovering 12GB can be extremely useful.

While the answer for this particular segment of Mac users would be to uninstall or remove Apple Intelligence, it’s not that simple.

Under macOS 27, there’s no option to turn off Apple Intelligence at all. You can turn off Siri, but there’s no single point in the menu to disable Apple Intelligence completely.

Even if you manage to disable Apple Intelligence, there’s still data hanging around and no direct option to remove it. There are about 12 gigabytes of models that Apple Intelligence relies on, and that’s storage users could find other uses for, if they were allowed to delete it.

Without a single Apple-sanctioned option to remove AI in the Settings, Mac users will have to look elsewhere for a solution.

RemoveMacAI

A project by Om Lahore called RemoveMacAI aims to clean up your Mac of Apple Intelligence. It’s a free project, released on GitHub under the MIT license.

RemoveMacAI is a script that installs a configuration profile to disable Apple Intelligence features on a Mac. That includes features like Siri AI, Writing Tools, Genmoji, Image Playground, and more.

As well as disabling features, it also removes the Apple Intelligence foundation models, as well as those for image generation, Spatial Photos, Photos Clean Up, and Xcode code completion.

The script’s configuration profile works on restriction keys for Apple Intelligence, as well as for settings that don’t have a restriction key. The models are removed using Apple’s asset service, with System Integrity Protection enabled and System files kept intact.

Once deleted, the profile also redirects attempts to download each removed model to a closed local port. This prevents macOS from redownloading the models again.

However, you can remove the configuration profile to restore previous settings and allow the models to redownload.

How to use RemoveMacAI

AppleInsider recommends that users check out the project and ensure they are aware of what RemoveMacAI does before running it.

While there are a few ways to run RemoveMacAI, the easiest is from a single line, pasted into Terminal. At the time of publication, that line is:

curl -fsSL https://raw.githubusercontent.com/omlahore/RemoveMacAI/main/install.sh | bash

Ran in Terminal, it downloads RemoveMacAI to a temporary folder and automatically runs. It shows how many features are active, how much storage space the models consume, and warns you about what happens if you proceed further.

At the prompt to "Turn Apple Intelligence off? [Y/N]" type Y, then enter.

A Device Management pop-up will appear, asking if you want to install the configuration profile. Click Install, and the script will continue to delete the models.

To revert the process, use this similar line in Terminal:

curl -fsSL https://raw.githubusercontent.com/omlahore/RemoveMacAI/main/install.sh | bash -s revert

“Rendering Doom in a database is obviously a bad idea,” Lukas Vogel writes in a lengthy blog post explaining how exactly he managed to render Doom using an SQL database.

OK, that’s not entirely accurate. The SQLDoom project uses a small Python client to handle input and output, drive the game’s timing, and display each frame to the screen. Behind that, a series of CedarDB tables tracks the game geometry and state, while about 1,300 lines of SQL queries spread across 89 common table expressions implement the game logic and generate 35 bitmap framebuffers per second.

In this, SQLDoom is a major improvement over Vogel’s previous DoomQL project, which last year set out to build “a multiplayer Doom-like shooter entirely in SQL.” Unfortunately, that effort ended up with raycasting-based, grayscale ASCII graphics that were more akin to the simplistic 90-degree-angled maps of Wolfenstein 3D. The newer SQLDoom, on the other hand, generates full-color 640×480 frames that look like they could have come from the original Doom executable.

It’s all just data, man

Converting Doom‘s classic WAD files to a relational database was relatively simple and straightforward, Vogel writes, because of the way the original game broke levels down into vertices, lines, sectors, and so on. Even Doom‘s famous binary-space partition trees can be broken down into SQL using a sort_key for objects that’s pre-computed for each position at load time. With this set in your table, a simple “ORDER BY” statement can determine which parts of walls to display and which to ignore every frame, vastly improving performance.

Here comes dbForge 2026.2, a new release of our ever-evolving ecosystem of AI-powered database lifecycle management solutions—and it’s packed with useful updates you definitely shouldn’t miss! These include a brand-new embedded PostgreSQL Debugger in dbForge Studio, handy visual object editors for PostgreSQL, broader context awareness in dbForge AI Assistant, enhanced SQL development and schema comparison capabilities, and a new, simplified product activation flow. It’s all here to make the daily work of developers, architects, and analysts much easier.

Without further ado, let’s get started!

What’s in the box?

Embedded PostgreSQL Debugger in dbForge Studio

First and foremost, we’re glad to introduce a brand-new PostgreSQL Debugger in dbForge Studio. With its help, you will no longer need to scrutinize your code in order to find potential performance bottlenecks and other possible issues. The Debugger will help you do the following:

• Set breakpoints in your code to pause the execution at specific lines
• Step through code line by line to see how each line is executed
• Monitor the current values of variables, expressions, and query results to analyze how data changes during the execution process
• Handle exceptions by highlighting the exact line where the error occurs

One of the best things about our new PostgreSQL Debugger is that it’s integrated into dbForge Studio, so you won’t have to deal with any extensions or manual setups at all.

New visual object editors for PostgreSQL

The same dbForge Studio for PostgreSQL has received new visual object editors for event triggers, functions, and procedures. These editors eliminate the need to manage these objects with raw code, bringing the convenience of a visual interface into your daily operations.

You can invoke them in multiple ways:

• On the Start Page, go to the Database Design tab > New Database Object
• Go to the Database menu > New Database Object
• Click the New Database Object icon on the application toolbar
• In Database Explorer, double-click the required object to open it in the editor
• In Database Explorer, create a new event trigger/function or open the existing one from the context menu

This is what the editor looks like for event triggers.

This is what the editor looks like for functions.

This is what the editor looks like for procedures.

Also note that dbForge Studio for PostgreSQL now lets you configure the default action performed when you double-click database objects in Database Explorer. Separate default actions can be set for tables and views, and for procedures and functions. You can do it in Tools > Options.

Broader context awareness in dbForge AI Assistant

Another key goal of this release was to make dbForge AI Assistant smarter and more flexible than ever, allowing you to tailor it to your workflows and standards as precisely as possible. To achieve this, your control over the context has been greatly expanded, most notably with the ability to attach files. For instance:

• You can freely select to auto-attach your currently active document to the AI chat
• You can attach ready-made files instead of manually copying SQL code into your prompts
• You can provide the Assistant with sample code to help it learn your coding style and standards—and thus generate code that consistently adheres to them
• You can attach two scripted databases and have the Assistant compare them
• You can attach multiple databases to the same chat
• Generally, you can give the Assistant any files (e.g., application code, database projects/diagrams, or custom instructions) as an additional source of context

Another useful addition to the AI Assistant is the ability to select an AI model to be used. Now you can configure it from the Tools menu > Options > AI Assistant > General. The available models include the following:

• Anthropic: Claude Haiku 4.5, Claude Sonnet 4.6, Claude Sonnet 5
• OpenAI: GPT-5.4, GPT-5.5

Free Express edition of dbForge AI Assistant

This release makes dbForge AI Assistant even more accessible by introducing a long-awaited free Express edition. It provides a limited number of tokens and 14-day storage of chat history, which is still a great way to explore the Assistant’s capabilities and try it out in your daily work.

In case you need more extensive AI assistance, with a considerably larger token allowance and unlimited chat history, you can upgrade to a paid plan at any moment.

SQL development enhancements

From now on, you can apply object and column name qualification to code that is already written. Previously, the qualification settings in Options > Text Editor > Code Completion > Advanced applied only while you typed. Now, the new refactoring command uses the same settings and qualifies names in an entire pre-written SQL document or a selected fragment of code.

We have also implemented wildcard expansion for all supported contexts, whether in the entire SQL document or in a selected fragment of code.

These enhancements have been implemented in dbForge SQL Complete and three dbForge Studios: for SQL Server, MySQL, and Oracle. And if you’re dealing with multiple database systems on different projects, you may want to try dbForge Edge, a suite of four Studios that works across a huge number of databases and cloud services.

Quick data generation from Database Explorer

If you need to generate data for a table (or several tables) quickly, just go to Database Explorer, right-click the required table(s), and select Generate Data from the shortcut menu. You will immediately proceed to configure your generation without any unnecessary steps.

New “Last modified” column in schema comparison documents and reports

Schema comparison documents, as well as all three types of comparison reports, now include a handy Last modified column.

This feature has been implemented across dbForge for SQL Server and dbForge for Oracle.

Support for MySQL 26.7 and MariaDB 13.x

Finally, all dbForge tools for MySQL are now seamlessly compatible with MySQL 26.7 and MariaDB 13.x.

Get your dbForge 2026.2 update today!

The update is already available, so you can open your dbForge product, proceed to Help > Check for Updates, and get your dbForge 2026.2 right away.

If you’re not a user of dbForge yet, we gladly invite you to download any product for a free trial and give it a go in your daily work.

For extra convenience, we have introduced product activation via a simple sign-in, now available alongside the traditional methods: entering an activation key and generating an activation request.

And, like we said previously, if you’re dealing with multiple database systems on different projects, you can try dbForge Edge, an AI-powered multidatabase solution that helps you cover the entire database lifecycle—including database design, development, management, and administration—across SQL Server, MySQL, MariaDB, Oracle, PostgreSQL, and a vast number of related database systems and cloud services.