Skip to main content
Locus

Complements what you already use

Locus isn't trying to replace your note app, your cloud storage, or your AI assistant. It's a thin search layer that sits underneath all of them: point it at a folder, and whatever AI you already talk to can find things in it with citations back to the real file. That's the whole product. Below is exactly how that plays with the tools people usually ask about — what's real today versus what isn't built yet, same honesty rule as the rest of this site.

Note apps — Obsidian, Logseq, and similar

Obsidian and Logseq vaults are just folders of plain .md files on disk — Locus doesn't need a plugin or a special integration to read one. locus index ~/path/to/your-vault --prune indexes it exactly like any other folder. Locus doesn't touch the vault's graph view, backlinks, or plugins, and it doesn't write anything back into it — it only reads. Your notes stay exactly where they are, in the app you already use to write them; Locus just makes the same files answerable by the MCP-capable assistants you connect.

Notion is different, and handled differently on purpose: it isn't local files, so locus sync-notion does a one-time OAuth login and then pulls your pages down into a local Markdown cache, which then goes through the same indexing pipeline as everything else.

Cloud storage — Google Drive, Dropbox, OneDrive, iCloud Drive

If you already run one of these as a desktop app, it's syncing your files into an ordinary local folder — Locus indexes that folder the same way it indexes any other. It doesn't replace your backup, sharing, or version history; it just makes what's already sitting on your machine searchable with citations.

What Locus does not do today: call Google Drive's, Dropbox's, or any cloud provider's API directly to pull files you haven't synced locally. A direct cloud-source integration is a planned future step, not built yet — if it isn't on your disk, point the desktop sync app at it first.

Your AI assistant — Claude, ChatGPT, and the rest

Locus doesn't replace the assistant you already talk to, and it deliberately has no chat interface of its own. It's a tool your assistant calls over MCP — you keep using the same client, the same conversation, the same habits; Locus just gives that conversation something new to search.

Ask your assistant to help you fit the rest together

Once Locus is connected, the assistant you're talking to already knows what note apps, storage tools, and workflows generally look like — that's just what a capable AI assistant reasons about, not something Locus built or trained specially. So it's worth literally asking it: "given what you can already search in my files, what else in my setup would actually help?" It can reason over what it finds through Locus and what it already knows about the broader landscape of tools. This is general assistant capability applied to your own files, not a Locus feature with its own UI or guarantee — treat any answer the way you'd treat any other AI suggestion, and verify before you act on it.

See /compatibility for the full list of file formats Locus can index, and /docs/connect for exact setup steps per AI client.