Privacy on KnightLi Blog

Chrome Silently Downloads 4GB Gemini Nano: How to Check, Disable, and Delete It

Sat, 09 May 2026 21:37:18 +0800

Google Chrome has been reported to download a roughly 4GB local AI model file in the background without explicit user permission, sparking debate about privacy, storage usage, and environmental impact.

The files are related to Gemini Nano and are mainly used for Chrome’s local AI features. The dispute is not simply that the browser supports local AI, but whether the download process is transparent enough, whether users should be informed in advance, and whether system resources are being used reasonably.

What happened

The model file being discussed is named weights.bin and is located in Chrome’s OptGuideOnDeviceModel directory. It is believed to be a localized version of Gemini Nano, used to perform some AI inference directly on the device.

Chrome decides in the background whether to download it based on hardware capability, especially RAM and VRAM. Users generally do not need to start the download themselves, and they may not see a clear prompt before it happens.

The more frustrating part is that manually deleting the model file usually does not stop it from coming back. As long as the related feature remains enabled, Chrome may download the model again after a restart or a later update.

The platforms mentioned in the discussion include Windows 11, macOS, and Ubuntu desktop systems. Based on Chrome’s desktop install base, the number of potentially affected devices could reach hundreds of millions.

Google’s explanation

Google says these files support local AI features such as “Help me write” and scam detection. Running the model locally can reduce some data uploads and improve privacy protection.

Google also says that if device storage is low, Chrome will automatically remove the related model to free up space. In other words, the model does not necessarily occupy disk space permanently.

At the same time, Google says users have been able to disable the related feature in Chrome settings since February 2024. Once disabled, the model will no longer continue downloading or updating.

How to check and disable it

If you do not want Chrome to keep the Gemini Nano model locally, start by checking a few places.

First, open Chrome settings and look for options related to “on-device AI”, local AI, writing assistance, or optimization suggestions, then disable the features you do not need.

Second, enter this in the address bar:

`1`	`chrome://flags`

Then search for and disable:

`1`	`Enables optimization guide on device`

Finally, check Chrome’s user data directory for the OptGuideOnDeviceModel folder and delete the model files inside it. Keep in mind that deleting the file alone is usually not enough. It is better to disable the related flag or setting first, otherwise Chrome may download it again later.

Possible paths on different systems

OptGuideOnDeviceModel is usually under Chrome’s user data directory. The exact location can vary depending on the operating system and installation method, but these are good places to check first:

Windows: %LOCALAPPDATA%\Google\Chrome\User Data\
macOS: ~/Library/Application Support/Google/Chrome/
Linux: ~/.config/google-chrome/
Chromium: ~/.config/chromium/

After opening the relevant directory, search for OptGuideOnDeviceModel or weights.bin. If you use Chrome Beta, Dev, or Canary, the directory name may include the corresponding release channel.

How to tell whether weights.bin has been downloaded

The simplest method is to search Chrome’s user data directory for:

`1`	`weights.bin`

If it has been downloaded, it will usually appear inside OptGuideOnDeviceModel, and the file size may be close to several GB. You can also check the modified time to see whether Chrome recently created or updated it in the background.

If you cannot find weights.bin, that does not necessarily mean the device will never download it. Chrome may decide whether to fetch the model based on hardware conditions, region, version, feature flags, and experiment configuration.

Which Chrome AI features may be affected

After disabling the related local AI or optimization features, some on-device capabilities that depend on Gemini Nano may be affected, such as “Help me write”, local scam detection, and future browser AI features that do not go through the cloud.

For users who do not use these features, everyday browsing is usually not affected much. For users who frequently use Chrome’s built-in writing assistance, page understanding, or experimental safety detection features, the experience may fall back to cloud processing, become unavailable, or use another browser-provided alternative.

Where the controversy lies

The central question is whether a browser should download several GB of model files for AI features before the user has clearly agreed.

Supporters argue that local AI can reduce cloud processing, improve privacy, and make responses faster. Critics argue that users should at least see a clear prompt before the download, especially when the file is close to 4GB and may affect storage space and network traffic.

Privacy experts also point out that this kind of insufficiently disclosed background download may raise compliance questions under the EU ePrivacy Directive and GDPR. Whether it constitutes a violation depends on Google’s notice mechanism, default settings, data processing path, and user controls.

Summary

Chrome’s adoption of Gemini Nano shows that browsers are moving more AI capabilities onto the local device. But it also creates a new product boundary problem: local models still consume disk space and bandwidth, and they can affect the user’s sense of control over their own device.

For ordinary users, the most direct step is to check Chrome’s local AI and optimization settings. If you do not need these features, disable the related options and then delete the model files in the OptGuideOnDeviceModel directory.

Canonical Ubuntu AI Roadmap: Local Inference First, No Forced Integration

Fri, 08 May 2026 22:23:46 +0800

Canonical’s recent Ubuntu AI roadmap is notable less for “putting AI everywhere” and more for trying a restrained path: AI features are layered, disabled by default, enabled only by explicit user choice, and designed to prefer local inference.

That stands apart from some of the controversy around system-level AI in Windows and macOS. Ubuntu is not trying to build an unavoidable global AI layer, nor is it promising one universal AI kill switch. Instead, the plan is to expose AI as separate tools, letting users decide whether to install them, enable them, choose a model, and allow data to leave the machine.

First, the timeline: not Ubuntu 26.04 LTS

The roadmap points mainly to Ubuntu 26.10 “Questing Quokka”, expected on October 9, 2026. Canonical plans to introduce some AI tooling as experimental previews, not as default features in Ubuntu 26.04 LTS.

That matters. LTS releases are meant for stability, enterprise deployment, and long-term maintenance. It would be unusual to place exploratory desktop AI features into an LTS default experience. A more reasonable path is to test them first in a regular release such as 26.10, gather feedback from developers and early users, and then decide what belongs in later long-term releases.

Local inference first, cloud only by choice

One core principle is local inference first. By default, inference should happen on the user’s machine. Requests should leave the machine only when the user explicitly configures a cloud provider, a self-hosted server, or an enterprise model service.

The reason is practical: system-level AI can easily touch command output, logs, file paths, errors, and system configuration. Sending that information to the cloud automatically, even to explain an error, creates obvious privacy and compliance risks.

So Ubuntu’s AI direction is not a cloud AI gateway. It is closer to a pluggable inference layer. Users may choose a local model, an internal company service, or a Canonical-managed service when needed. The important part is avoiding lock-in to one model vendor.

AI CLI: start with terminal assistance

One of the first practical features may be the AI Command Line Helper, often referred to as ai-cli.

It is not meant to replace the shell or automatically run risky commands. Its job is to help users understand commands, logs, systemd units, error output, and system state. For example, it could explain why a service failed to start, or clarify what a command-line flag means.

This fits Ubuntu’s audience well. Many Ubuntu desktop and server users already live in the terminal. Instead of starting with a flashy chat window, it makes sense to put AI into error analysis, command explanation, and operations assistance.

The safety boundary must be clear. Logs may contain tokens, internal hosts, usernames, file paths, key fragments, or business information. Even with local inference by default, tools should encourage redaction. If a user chooses a cloud backend, the UI must make clear what will be sent.

Settings Agent: natural-language system settings

Another direction is a Settings Agent that lets users query or change system settings in natural language.

This sounds simple but is easy to get wrong. A mature Settings Agent should not scrape the screen, guess buttons, and simulate clicks. It should use controlled internal APIs: what it can read, what it can change, when confirmation is required, and how failures are rolled back.

That makes it more likely to be a post-26.10 direction than a complete immediate feature. If done well, it could lower the barrier for normal users to configure desktop Linux. If done too aggressively, it becomes a new security risk.

Why not a universal AI kill switch?

Many users worry that once vendors add AI to an operating system, AI appears everywhere and becomes hard to disable. So the natural question is whether Ubuntu should provide a global AI kill switch.

Canonical’s position is that if AI features are opt-in, layered, and independently installable and configurable, a global kill switch is not the first priority. In other words, the design should avoid the pattern of “enabled by default, deeply embedded, then users have to disable it.”

Whether that is enough depends on implementation. If AI tools are not enabled by default, do not connect to remote services by default, do not collect data automatically, and each feature has clear controls, users should not need to hunt through hidden settings to turn AI off.

What it means for developers and enterprises

For developers, AI CLI tools can reduce the time spent reading documentation, parsing logs, and diagnosing system problems. They do not replace engineering judgment; they automate a lot of “help me understand this output” work.

For enterprises, local inference and pluggable backends matter more. Many companies cannot send source code, logs, customer data, or infrastructure details to public model services. If Ubuntu can connect system-level AI with local models, private inference services, and enterprise permissions, it may offer useful assistance in compliant environments.

This is also an opening for Linux desktops and workstations. Windows and macOS can more easily fold AI into vendor ecosystems. Ubuntu’s advantage is openness, auditability, replaceability, and self-hosting. If Canonical preserves those principles, AI could strengthen the professional Linux experience.

Do not overread it

It is too early to say that Ubuntu will preinstall a specific small model, that Ubuntu 26.04 will include an AI audit mode, or that there will be a fixed ubuntu-ai command. The clearer public information is about direction, not final product shape.

The safer reading is this: Canonical is preparing a system-level AI tooling framework for Ubuntu, starting with command-line help, settings assistance, local inference, and backend choice. The default posture is user choice, not vendor choice.

Summary

The important part of Ubuntu’s AI roadmap is not that Ubuntu is “joining the AI wave”. It is the attempt to define a more restrained model for AI in open source operating systems: intelligence can become infrastructure, but privacy, control, and user choice must come first.

If the experimental features in 26.10 live up to those principles, Ubuntu may take a different path from consumer operating systems: AI not as an unavoidable system ad slot, but as a selectable, replaceable, and auditable productivity layer.

References:

Claude Identity Verification: Why It Exists, What You Need, and How Data Is Handled

Thu, 16 Apr 2026 09:20:00 +0800

Anthropic is gradually rolling out identity verification on Claude. According to the official help article, this is not simply an added barrier. It is part of platform integrity, safety, compliance, and abuse-prevention work.

In short, Claude identity verification is meant to solve three problems:

Confirm who is using powerful AI tools.
Help enforce usage policies and reduce abuse.
Meet necessary legal and compliance obligations.

If you see an identity verification prompt while accessing certain Claude features, it usually means the platform is running a routine safety and compliance check. Anthropic also states that verification data is used only to confirm your identity, not for other purposes.

01 When Verification May Be Required

The official document does not list every trigger condition. It only says identity verification is being rolled out for some use cases and may appear when you access certain features.

That means a verification prompt does not necessarily mean your account has a problem. More common cases include:

You are using a feature that requires a higher trust level.
The platform is running an integrity check.
Your account or usage scenario has triggered a safety and compliance process.

From a user perspective, the most important thing is knowing what you need before the verification flow starts.

02 Who Handles Verification

Claude identity verification is handled by Anthropic together with the third-party verification provider Persona Identities.

Anthropic says it chose Persona because of:

Technical strength
Privacy controls
Security safeguards

In practice, Anthropic sets the rules for how verification data is used and retained, while Persona processes the verification flow according to Anthropic’s instructions.

03 What You Need

Before starting verification, prepare three things:

Item	Notes
A valid government-issued photo ID	It must be a physical document and available nearby
A phone or computer with a camera	You may need to take a live selfie or use a webcam
A few minutes	Verification usually takes less than 5 minutes

If your ID is not nearby or your device has no camera, the verification process may be interrupted.

04 Accepted ID Types

Anthropic accepts original, physical, government-issued photo IDs from most countries. Common examples include:

Passport
Driver’s license
State, provincial, or regional ID
National ID card

The document must meet these basic requirements:

Issued by a government
Includes your photo
Clear and readable
Undamaged
Not a copy or screenshot

05 What Is Not Accepted

These materials generally cannot be used for Claude identity verification:

Copies
Screenshots
Scans
Photos of photos of an ID
Digital or mobile IDs, such as mobile driver’s licenses
Non-government IDs, such as student IDs, employee badges, library cards, or bank cards
Temporary paper IDs

This is an easy place to make a mistake. The requirement is not just “readable”; it must be an original, physical, government-issued ID.

06 How Data Is Protected

This is the most important part of the document.

Anthropic’s explanation can be summarized as follows:

Anthropic is the data controller for verification data and sets rules for use and retention.
Persona is the processor and performs verification on Anthropic’s behalf.
ID documents and selfies are collected and stored by Persona, not directly in Anthropic’s systems.
Anthropic can access verification records through Persona when needed, such as when reviewing appeals.
Persona is contractually limited in how it can use the data, mainly to provide and support verification and improve fraud prevention.
Data sent to Persona is encrypted in transit and at rest.

In other words, the ID and selfie you submit are not treated as ordinary account profile data for general use. They are restricted to identity verification and compliance workflows.

07 What Anthropic Says It Does Not Do

The official article explicitly lists several things Anthropic does not do:

It does not use identity verification data to train models.
It does not collect more information than needed to verify identity.
It does not use identity data for marketing, advertising, or unrelated purposes.
It does not share verification data with unrelated third parties unless legally required to respond to valid legal process.

This matters because the sensitive part of identity verification is not only taking a photo of an ID, but what happens to the data afterward. Anthropic’s position in this document is that verification data is used only for identity confirmation, legal obligations, and safety compliance.

08 What If Verification Fails

Verification can fail for ordinary reasons, including:

Blurry photos
Poor lighting
Unclear ID information
Expired documents
Technical issues

Anthropic recommends this order:

Try again. The verification flow usually allows multiple attempts.
Retake the photo in better lighting.
Check that the ID is clear, complete, and not expired.
If you have another government-issued photo ID, try that.
If you run out of attempts and still cannot verify, contact support through the official form.

In practice, the most common fix is better lighting and a properly focused camera.

09 Why an Account May Still Be Disabled After Verification

Passing identity verification does not guarantee that an account will never be restricted. Anthropic says accounts may still be disabled for other safety-process reasons, such as:

Repeated violations of usage policies
Creating an account from an unsupported location
Violating the Terms of Service
Use by someone under 18

If you believe your account was disabled by mistake, you can submit the official appeal form with your account information so the safety team can investigate.

10 How Users Should Prepare

If you plan to keep using Claude, especially higher-trust features, prepare these things ahead of time:

Have a valid, unexpired, physical government-issued photo ID ready.
Make sure your camera works, ideally on both phone and computer.
Verify in a well-lit environment.
Do not upload screenshots, scans, or photos of ID photos.
If verification fails, check image clarity and lighting before contacting support.

For most users, Claude identity verification is not a complicated process, but it is strict about document authenticity. If the document type is correct and the photo is clear, it usually takes only a few minutes.

Privacy on KnightLi Blog

Chrome Silently Downloads 4GB Gemini Nano: How to Check, Disable, and Delete It

What happened

Google’s explanation

How to check and disable it

Possible paths on different systems

How to tell whether weights.bin has been downloaded

Which Chrome AI features may be affected

Where the controversy lies

Summary

Canonical Ubuntu AI Roadmap: Local Inference First, No Forced Integration

First, the timeline: not Ubuntu 26.04 LTS

Local inference first, cloud only by choice

AI CLI: start with terminal assistance

Settings Agent: natural-language system settings

Why not a universal AI kill switch?

What it means for developers and enterprises

Do not overread it

Summary

Claude Identity Verification: Why It Exists, What You Need, and How Data Is Handled

01 When Verification May Be Required

02 Who Handles Verification

03 What You Need

04 Accepted ID Types

05 What Is Not Accepted

06 How Data Is Protected

07 What Anthropic Says It Does Not Do

08 What If Verification Fails

09 Why an Account May Still Be Disabled After Verification

10 How Users Should Prepare

Related Links