The Great iCloud Divorce: A Tale of Two AIs and One Very Angry Mac

Or: How I Learned to Stop Worrying and Love sudo killall fileproviderd

TL;DR

Breaking up with iCloud is like trying to leave a cult. Except the cult has kernel-level access to your Mac and really, really doesn’t want you to go. Also, I needed two different AIs to help me escape, and only one of them made it out alive.

The Setup: Why I’m Leaving (And Why It Shouldn’t Be This Hard)

I didn’t wake up one morning and decide to nuke my 250GB iCloud ONE & iCloud+ subscription on a whim. This was ideological.

I’ve been on a slow-burn tech divestment journey since the industry went stone cold fascist—right around the time Black folks asked to stop being shot by police, and Biden suggested maybe, possibly, tech billionaires could pay some taxes. You know, radical stuff.

So when Scott Galloway kicked off #resistandunsubscribe and #resistICE, I was already primed. Cancel Amazon Prime? Done. Ditch the premium subscriptions funding oligarchs? Absolutely. Reclaim my 250GB iCloud ONE & iCloud+ subscription and move to local storage?

(Especially after watching Tim Cook personally deliver some gilded crystal bauble to the White House like a medieval courtier seeking favor.)

Should be simple, right?

Narrator voice: Reader, it was not.

I’m a Product Manager who’s shepherded enterprise orgs through multiple CMS migrations. I understand data architecture. I’ve seen things. But here’s what got me: Google Drive—clunky, awkward Google Drive that once duplicated files like digital tribbles—finally figured out sync. They can gracefully disconnect without making your data vanish (Google One AI Pro is also being divested of).

So I thought: “Apple. The ‘it just works’ people. Surely they’ve nailed something as fundamental as turning off a feature.”

Narrator voice: Reader, they had not.

Act I: Gemini Tries Its Best (Bless Its Heart)

When my Desktop and Documents folders vanished into the void after following Apple’s official “turn off sync and keep a copy” workflow, I turned to Gemini first.

Gemini was… enthusiastic. Earnest. Like a golden retriever trying to solve a Rubik’s cube.

Gemini: “Have you tried checking System Preferences?” Me: That’s literally what caused this.
Gemini: “Maybe restart Finder?” Me: Oh, sweet summer child.
Gemini: “You could re-enable iCloud sync!” Me: THAT’S THE OPPOSITE OF WHAT I’M TRYING TO DO.

We spent 45 minutes going in circles before Gemini cheerfully suggested I “contact Apple Support” for “this unusual situation.”

The unusual situation being: following Apple’s own documented process.

Act II: Claude Enters, Sees War Crimes, Rolls Up Sleeves

By the time I brought Claude into this nightmare, I had:

Claude Code took one look and said: “This is a messy but recoverable situation.”

Lie. It was not recoverable through normal means. But I appreciated the confidence.

The Technical Torture Parade

  1. The xattr Strip-Tease
  1. The Daemon Assassination Attempt Result: Operation not permitted The daemon respawns faster than we can kill it. Horror movie logic.
  2. The Great Folder Replacement Strategy “We’ll just rename the poisoned folders!” Result: Permission deniedYou cannot rename a folder. On your own computer. That you own.
  3. The Nuclear Option That Also Failed Result: Operation timed out (×61 times, once for each folder) The FileProvider daemon was actively intercepting every file operation. With root privileges. In real-time.
  4. The Actually Working Solution: Use the clean backup that had never touched iCloud’s corrupted influence. Finally.

The Technical Post-Mortem

Apple’s iCloud sync injects extended attributes that mark folders as FileProvider property. When you turn off sync:

The AI Assistant Scorecard

Winner: Claude Code, by technical knockout

To be fair to Gemini, this was like asking a dermatologist to perform cardiac surgery. But Claude showed up with a scalpel and a plan.

Narrator voice: Reader, this was written by Claude Code.

My Love Letter to Apple

Dear Apple,

I came to you from an Amiga 1200. I chose a Performa 6400 (or, rather, bought it secondhand from a friend) during your darkest timeline—when you had 47 different models that were all basically the same computer with different RAM. When Gil Amelio was driving the company into the ground. When “beleaguered” was permanently welded to your name in tech journalism.

I stayed through:

I’ve earned my right to be disappointed.

Context for younger readers: The Amiga 1200 was a powerhouse home computer in the early 90s—true multitasking, custom chips for graphics and sound, capabilities that made Macs of the era look quaint. Leaving that for a mid-90s Performa bought secondhand wasn’t just brand loyalty—it was faith in a vision despite all evidence to the contrary.

And Apple rewarded that faith by making it nearly impossible to get my own files back from iCloud in 2025.

The irony is exquisite.

You’ve built a sync system so invasive that:

Google Drive figured this out. GOOGLE. The company that once thought Google+ would be a thing. They can gracefully sync and unsync files without making them invisible to the operating system.

You’re supposed to be the “it just works” company. But iCloud only works until you try to stop it from working. Then it becomes a technical exorcism requiring multiple AIs, sudo privileges, and systems-level knowledge of extended attributes.

What Should Happen

  1. “Turn off sync” should actually turn off sync, not mark folders as detached-but-still-owned-by-FileProvider-daemon
  2. “Keep a Copy” should keep an actual copy, not create ghost folders that exist in Terminal but not Finder
  3. My admin account should have admin rights, even over folders that iCloud previously touched
  4. The FileProvider daemon should not have more power than sudo. This is not a democracy. I am root. The daemon should respect that.

What Will Actually Happen

You’ll ship another iPhone color, announce “all-new” iCloud features, and this bug—sorry, “behavior“—will persist for another decade while your engineering team integrates AI into the Notes app.

Epilogue: Freedom Tastes Like Terminal Commands

My data is recovered. My folders are local. My iCloud subscription is downgraded to the free tier.

The scars remain. I still get nervous when I see folder icons. I compulsively check xattr -l on random files. I’ve developed a Pavlovian response to “Permission Denied.”

But I’m free.

And if you’re reading this because you’re trying to escape iCloud too? Make a clean backup first. Not a move. Not a sync. A real, cp -a copy to a folder that has never known iCloud’s touch.

Then get Claude Code. Not Gemini. Claude.

And may the odds be ever in your favor.

Sincerely,

A Former 250GB iCloud+ Subscriber Who Now Understands Why Tech Twitter Has Trust Issues Currently #resistandunsubscribe-ing Her Way to Digital Sovereignty

P.S. — The full technical breakdown involves sudo killall fileproviderd racing conditions, SIP-protected extended attributes, and a FileProvider daemon with main character syndrome. The command history alone is 200 lines of trying to convince my Mac Studio that I, in fact, own my own files. It’s beautiful in a “watching a controlled demolition” kind of way.