Open-source project
SkyBlue997/enableMacosAI avatar
SkyBlue997/enableMacosAI

enableMacosAI ships a prebuilt kext and asks you to weaken one protection, not all of them

One-click tool to enable full Apple Intelligence (on-device + Private Cloud Compute) on mainland China region Macs, for macOS 27 / Apple Silicon.

2,365 stars134 forksShellApache-2.0

At a glance

What is it?
A minimal kernel extension that rewrites one device property at the source so a China-region Mac reports a US region code to the eligibility daemon. The engineering is unusually careful about its own limits, and the honest reading is that this is a machine-local region spoof that removes a regional eligibility gate rather than anything that changes Apple infrastructure.
Who is it for?
Understand what this is before running it. It does not unlock a feature Apple has disabled for capability reasons; it changes the device region code so the system believes it is in a supported region, which means the eligibility check now reflects a fiction rather than a real entitlement.
Can I use it commercially?
Yes. Apache-2.0 is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 3 days ago.
What is it written in?
Mainly Shell, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • SkyBlue997/enableMacosAI2,365 ★ · +246
Star history
Repository2026-09-222026-11-15
SkyBlue997/enableMacosAI2.1k2.4k

246 Stars in the last 54 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

The mechanism is one property, rewritten at the source

The technical description is short and specific, which is a good sign.

The gate is that a system call returning a region code of the China value causes the intelligence feature to be switched off. That value comes live from a region property on the device's platform expert node, and the project states explicitly that it is not a cached property file: the eligibility daemon on this system version recomputes it in real time, and the older approaches of editing a property file or locking it against writes no longer work.

So the extension matches that one device node and, during its start routine, sets the region property to the US value and the country-of-origin property to the United States.

Because the change happens at the source rather than per process, every process in the system reads the US value and the eligibility path, the model download and the interface all follow without per-process injection. That is a genuinely better place to intervene than the approaches it replaced, and it explains why the older workarounds stopped working.

It solves the eligibility layer and says so twice

The most valuable sentence in this README is a boundary, and the project puts it in the opening paragraph rather than in a footnote.

It states that it solves the eligibility layer, not Apple's server side and not the network layer of the private cloud compute feature.

That distinction matters because the two failure modes look identical from the outside. If the on-device model works and the cloud-backed features do not, the natural assumption is that the local part succeeded and the network is blocked. The project says the opposite: run its read-only classifier first and do not treat one particular status value as proof that the cloud side works.

The repository then repeats the discipline in its troubleshooting section, opening the cloud-failure guidance with the statement that a working on-device model does not prove the cloud feature works, and warning against repeatedly tapping on the action because each failure can trigger server-side rate limiting.

For a repository in this category that is not a small thing. Most projects of this kind promise everything works. This one ships a diagnostic tool whose main purpose is to tell you which half of the feature is actually broken.

Region is one input of about ten, and the page is careful not to overclaim

There is a warning block that prevents a very common misdiagnosis, and its care is the tell.

If the region property and the extension are both correct but the eligibility answer for one specific domain is still the negative value, the page says the likely culprits are the account region or the language, and tells you to inspect the individual inputs.

It then immediately walks the claim back. It says the domain answer is authoritative, and that an individual input showing the negative value does not by itself explain the whole domain. That is a careful sentence. Most troubleshooting guides would stop at the point where they had named a probable cause and tell you to go change it.

The instructions to inspect those inputs are concrete: a property-list read of the eligibility database at a path under the private variable directory, then either restarting the daemon by name through the service manager or rebooting.

So the diagnostic chain is: extension for the device region, account region and language for the rest, and the domain answer for the verdict.

The protected preference it recommends is the narrow one

The prerequisites are where a project of this kind normally stops being honest, and this one does not.

The recommendation is to run one specific command in recovery mode that disables only the extension signature check, and the page explicitly justifies the choice: the full disable works too, but turns off more protection than this project needs, and the script can now recognise both states.

That is the correct recommendation and the reasoning is worth internalising. System integrity protection is a bundle of separate controls, and the extension's signature check is one of them. Disabling the whole bundle to load one unsigned extension is a much larger concession than disabling one flag, and a project that has measured the difference and tells you which to use has done the work.

The other prerequisites are equally concrete. One specific boot argument must not be present, and the installer only detects and removes that explicit argument rather than assuming the absence of any boot arguments means things are fine. First load needs approval in a specific settings pane followed by a reboot. The account's media and purchases region must be a supported one, and the system language must match the Siri language with the safest choice given.

The language requirement is why a separate localization layer exists

The localization story is the part of this repository that shows the most iteration, and the explanation is a genuine constraint rather than a preference.

Eligibility reads the user's global language list and the Siri language, and the new Siri's language allowlist currently contains only English. So switching the system language to Chinese drops the new Siri. The page states this was verified instruction by instruction in the eligibility daemon, and that interface language and eligibility read the same value, so there is no room for pretending to the detector while displaying Chinese.

The project's answer inverts the usual approach. Keep the global language English and write Chinese into each application's own preference domain, which is equivalent to adding languages per application in settings, and which the eligibility daemon does not read. Apps that Apple hard-excludes, such as system settings, are launched by a resident proxy carrying a language launch argument, with dock icon and deep link behaviour preserved. All changes are logged and revertible in one step.

The script interface reflects that care: a dry run that changes nothing, separate scopes for built-in applications and for third-party ones because the third-party scope is broad, a status command, and a revert that restores each value. The page also warns explicitly not to run it with elevated privileges, since it modifies the current user's preferences.

The troubleshooting documents its own dead ends

The troubleshooting section is long, and its value is in what it refuses to present as a solution.

One subsection covers a second geofence input that this project explicitly does not handle, because it is determined by the system from location services, nearby networks and address, and this project's extension only fixes the device region value. It tells you which input to inspect and, if that is the blocker, points to community approaches with a bold disclaimer that none of them are verified by this project and you accept the risk yourself.

Those approaches are described with their costs attached. One uses a third-party tool to relocate the position signal and restart the location daemon, with a note that changing the position without restarting that daemon has no effect. Another edits a cached country code, locks it against writes and reboots, with the stated side effect that the locked cache can never update again and at least one person found it reverting after a day. A third reinstalls the system and immediately runs the script, on the reasoning that the machine should not have network traces left behind.

It also records what does not work: editing the eligibility values directly, because the daemon recomputes them. That is a list of dead ends with citations, which saves more time than any of the workarounds.

The repository ships source, a prebuilt binary, and a signing warning

The root listing tells you what you are actually installing.

There is a source directory holding the extension implementation, a separate file declaring the kernel entry point and providing the symbol linking requires, and an extension bundle property list carrying the personality that matches the device node. There is a build document with the full compile and link commands, and a prebuilt extension bundle for the arm64e architecture with an ad-hoc signature, already compiled.

The load path is a launch daemon that loads the extension early in boot and refreshes the intelligence daemon, calling a shell script, with the daemon property list at the root. Alongside those sits the installer script, the read-only classifier for the cloud feature, an offline fixture test for that classifier, and the localization directory.

The signing situation is stated in the troubleshooting section rather than the install section. A signature failure means you should confirm the actual output of a status command rather than guessing from whether protection is partially or fully on, and the page notes that this system version already has a successful case with the narrow exemption. It also notes that a system version that is too new or too old may fail verification, in which case you rebuild from source using the build document.

Shipping a prebuilt binary alongside the source, with the rebuild instructions, is the honest version of this. The alternative would be making everyone compile a kernel extension before they could try it.

The installer takes its jobs as subcommands rather than separate scripts:

bash
sudo ./install.sh

The others are a health check covering the protections, the signature state, the region, the extension and eligibility; a diagnostic that dumps all key state as one block of plain text, which the page asks you to paste when opening an issue because it carries no private data; a read-only classification of the cloud feature over a recent thirty minute window; and an uninstall that restores the original region.

Editorial conclusion

Understand what this is before running it. It does not unlock a feature Apple has disabled for capability reasons; it changes the device region code so the system believes it is in a supported region, which means the eligibility check now reflects a fiction rather than a real entitlement. If you bought a machine in a region where the service is not offered, that is a licensing question your regional terms decide, not something a kernel extension settles. If you are travelling or your account is genuinely in a supported region and only the hardware region differs, the mechanism is at least a precise one. Either way, note that it requires a weakened signature check and a kernel extension loading early, and that the project itself distinguishes which part of the feature actually works.

Frequently asked questions

How does enableMacosAI make a Mac eligible for Apple Intelligence?

It loads a minimal kernel extension that matches the device's platform expert node and, during its start routine, sets the region property to the US value and the country of origin to the United States. The value is read live from that node rather than from a cached file, so changing it at the source makes every system process read the US value.

Does enableMacosAI make the cloud features work too?

It states that it solves the eligibility layer, not Apple's server side or the cloud feature's network layer. The repository ships a read-only classifier and says a working on-device model does not prove the cloud side works, so run the classifier before assuming a cause.

What does enableMacosAI require before it will install?

Running a recovery-mode command that disables only the extension signature check rather than the full protection, which the page says is the narrower option. It also needs no specific boot argument present, first-load approval in a settings pane followed by a reboot, an account region in a supported one, and the system language matching the Siri language.

Can I keep a Chinese interface with enableMacosAI?

Yes, through a separate localization layer that keeps the global language English and writes Chinese into each application's own preference domain, which the eligibility daemon does not read. Apps Apple excludes are launched by a resident proxy carrying a language argument, every change is logged, and there is a dry-run mode and a one-step revert.

What does enableMacosAI say it cannot fix?

A second geofence input determined by the system from location services, nearby networks and address, which the extension does not handle. The page points to community approaches for it under a bold disclaimer that none are verified by the project, and describes their costs, including a cache lock that stops updating and one approach found reverting after a day.

Official sources

  1. Issues
  2. README
  3. SkyBlue997/enableMacosAI on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/skyblue997-enablemacosai.svg)](https://hysenlabs.com/projects/skyblue997-enablemacosai)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/skyblue997-enablemacosai.svg)](https://hysenlabs.com/projects/skyblue997-enablemacosai)

Was this useful?