For people who let AI work on their real computer.
Right now it can read everything and nothing checks what it ships. Lucy is the gate: it decides what your AI is allowed to read, and what it's allowed to put online.
Every file is fingerprinted with SHA-256. Encryption with keys you hold is on the roadmap.
Example: one file, three copies
lucy versions film HANDOFF_cut_v3.md3 copies · 2 match · 1 not read
DropboxFilm/HANDOFF_cut_v3.md · 3f9a61c2readable
Studio RAIDFilm/HANDOFF_cut_v3.md · 3f9a61c2offline · last seen 2h ago
iCloud DriveFilm/HANDOFF_cut_v3.md · content not on this Maccloud only · not read
Nothing deleted. Nothing downloaded. Dates never pick the winner.
The idea
One gate. Two directions.
AI lets one person build what used to take a team. But your AI tools get your whole drive, start every session from zero, and will happily ship a leaked key or a half-finished page. Lucy sits between your AI and your files. Going in, it hands over only the folders you approve and knows which copy of a file is the real one. Going out, it checks what you're about to publish. It runs on your Mac, makes no network calls, and it's open source.
In · what your AI may read
Only the folders you approve. Everything else does not exist to it.
Which copy of a file is the real one, across Dropbox, iCloud Drive and your drives
A cloud-only file is never read as an empty one
Short excerpts, secrets masked, every request logged
Search by what files say, and each project's saved decisions and handoffs
Out · what your AI may ship
Leaked keys and committed .env files
Libraries with known holes
Drafts, TODOs and private paths on a page about to go public
Use cases
What it looks like on a real day.
"Is this safe to deploy?"
Lucy checks the repo before it goes out: a key in a committed .env, a library with a known hole, a page that still has your working notes on it. You fix those, then ship.
"Where did we leave this project?"
A fresh session starts from the saved decisions and the last handoff instead of asking you to explain it all again.
How it connects
Every cloud and every drive, in one index.
Lucy sits between your files and your AI. It knows what is in each place, keeps the copies honest and lets through only what you approve.
CLOUD
Dropboxconnected
iCloud Driveconnected
Google Drivenext
YOUR HARDWARE
Mac Studioconnected
Attached RAIDconnected
Laptopnext
Blue is your files. Red is what Lucy stops at the gate: hidden instructions, leaked keys and attempts to reach outside an approved folder.
Why it is safer
One checkpoint instead of full access.
Without Lucy, an AI assistant is wired straight into Dropbox, iCloud and your drives, with access to everything.WITHOUT LUCYAI assistantDropbox· everythingiCloud· everythingYour drives· everythingWith Lucy, the assistant goes through Lucy, which checks every request and passes on only approved folders from Dropbox, iCloud and your drives.WITH LUCYAI assistantLucychecks everyrequestDropboxapproved foldersiCloudapproved foldersYour drivesapproved folders
Each tool is wired into each place, with full access. Nobody knows which copy is current, and nothing is logged.
One checkpoint. Short, masked excerpts from approved folders only. Every request, allowed or denied, is written down.
Security
Denied by default.
An assistant sees a folder only after you approve it. Everything else does not exist to it.
0
network calls in Lucy's own code
22
automated safety tests, in the repo
allowapproved folders, one project each
allowshort excerpts with secrets masked
denypaths that escape a folder, symlinks included
denyshell, SQL, URL fetch, general file read
denyinstructions found inside a document
denywrites, until you switch them on
Roadmap
One Mac today. Every device next.
Now · built
Secure and remembered
On one Mac: security checks, the approved-folder gate, and a searchable index of Dropbox, iCloud Drive, your drives and your code.
Next
Every device
Your laptop and desktop share one picture of each project. Lucy fetches the files a task needs and offloads them after. Google Drive, and a board for every project.
Later
Hosted
Lucy run for you, so it works when your own machines are off. Encrypted backups with keys you hold.
Three lines to connect.
git clone https://github.com/ckaico/lucy && cd lucyuv syncclaude mcp add --scope user lucy -- "$PWD/bin/lucy" mcp
Needs macOS, Python 3.11 or newer and uv. Nothing is readable until you approve a folder.
Early access
For what comes next: Lucy on every device, then hosted.
Your email is stored with Cloudflare for Lucy early-access updates. To leave the list, email hi@ckai.co.