What "Can Claude Read My Folder?" Taught Me About Product Boundaries

When I started building NorthLab Folders, I kept running into the same question from users: can Claude read my folder?

Not "how do I organize my chats?" Not "does the extension sync across my devices?" The question was always some variant of: can I point Claude at a local folder on my computer and have it work through the files?

The answer, it turns out, is: it depends which Claude you mean. And the fact that there are three different correct answers — all true simultaneously — is one of the most clarifying product lessons I've had.

Three Claudes, Three Answers

Here is the actual breakdown:

claude.ai (the web app): No. The web interface cannot touch your local filesystem at all. Whatever you see at claude.ai runs in a browser tab. It has no mechanism to read a directory on your machine. The only way local files get in is if you manually upload them.

Claude Code (the CLI): Yes. Claude Code is a command-line tool you install and run from a terminal. It operates inside your working directory. It reads files, writes files, runs commands. Local filesystem access is the entire point. It even has its own config directory at ~/.claude.

Claude Desktop with MCP connectors: Also yes, but differently. Claude Desktop is a native app that can load Model Context Protocol servers — small local processes that expose tools. One such tool category is filesystem access. So with the right MCP connector configured, Claude Desktop can read files you point it at.

Same brand. Same underlying model. Three completely different relationships to your local machine.

I wrote a full guide on this distinction because so many people were confused — and the confusion was understandable. "Claude" is used to mean the model, the web app, the CLI, and the desktop app, often interchangeably. When someone says "Claude can read your folder," they might be right and wrong at the same time depending on context.

The Adjacent Feature Request

The confusion had a product consequence for me.

Users trying NorthLab Folders — an extension that adds a real folder sidebar inside claude.ai and chatgpt.com — would ask whether it could sync with a local folder on their machine. Could they just point it at a directory and have the extension organize chats based on what projects were in there?

It's a reasonable idea. If you're already working inside a project folder locally, why not mirror that structure in your chat sidebar? The request came up enough times that I had to make a deliberate call about it.

I said no. Not because it was technically impossible, but because it was a different problem with a different trust model.

The Trust Model Difference

NorthLab Folders is, at its core, a chat organizer. It adds folders and subfolders to the sidebar inside claude.ai and chatgpt.com. The folder structure and chat IDs live in the browser's local extension storage. Conversation content is read in-page only to render the sidebar and generate exports — nothing is ever sent to any server. There's no backend storing your data. The only outbound call is to verify a Pro license.

The architecture is deliberately narrow: the extension knows your folder names and which chat IDs belong in each folder. It does not know what you said in those chats, and it never needs to.

Reading local files would require a completely different architecture. A browser extension that accesses your filesystem needs elevated permissions — permissions that trigger browser security dialogs, that change what users need to understand about what they're installing. You are now not explaining "it organizes your chats" but "it reads your files." Those are different explanations that require different trust.

And they should require different trust. An extension that touches your filesystem has a larger attack surface, a more complex permission model, and a different category of risk if something goes wrong. A chat organizer that never leaves the browser tab is simpler to reason about — for users and for me.

Saying No to an Adjacent Feature

The discipline here is not just technical. It's positioning.

Every extension or tool that tries to do too many things ends up being bad at explaining itself. "What does it do?" is the first question a new user asks. If the answer takes three sentences to establish prerequisites, you've already lost some of them.

NorthLab Folders has a clear answer: it adds folders to Claude and ChatGPT in your browser. That's it. Claude's native organizing primitive — Projects — is useful but limited: capped at 5 on the free plan, no nesting, and no way to pin individual chats. The extension fills that specific gap. Folders, subfolders, pins, date stamps, export. All local, no account required.

The local filesystem feature would have been adjacent to that. Related enough to seem like a natural extension, but different enough in trust model that combining them would have muddied what the product is.

The cleaner product boundary also makes the trust story simpler to tell. Users can verify what the extension does: check the permissions, look at what storage it uses, see that there's no login. The narrower the scope, the shorter the verification path. For a browser extension touching a chat interface, that matters.

What the Confusion Actually Taught Me

The recurring "can Claude read my folder?" question was not a feature request in disguise. It was a signal that people were trying to locate this product in a mental map that already included Claude Code and MCP-connected desktop apps.

My job was not to build the filesystem feature. My job was to be clear enough about what NorthLab Folders is — a chat organizer, browser-only, local-first — that the question resolves itself: not because we added the feature, but because users understand the tool well enough to know it's a different tool they're thinking of.

The clearest products are the ones where what you don't do is as deliberate as what you do. Saying no to local file sync was not a limitation I'm working around. It was a product decision I'd make again.

---

If you're working in claude.ai and find yourself wishing you could group your chats into folders, NorthLab Folders does exactly that — nothing more, nothing less.