Your knowledge base stays plain Markdown in your own vault.

What this actually is

Co Platform is a hosted knowledge base with a chat layer over it. You put documents and notes in, it files them into linked pages, and then you — or people you share the link with — can ask it questions and get answers with citations. It lives on a server, which is what makes it answerable from a phone, or by someone who isn't you.

Twins KB Sync is the sync client for that. The order matters: you create a knowledge base on the site first, then point the plugin at it. From then on it mirrors that knowledge base into your vault and keeps both sides current — pull brings cloud changes down, push sends your local edits up.

So this is not a standalone Obsidian plugin, and I would rather you knew that now than after installing. It is a sync client, and it does nothing without an account on the server it syncs against.

What keeps working in your vault

• Plain files, plain folders. Pages arrive as Markdown files on disk. sources/ is organized into topic folders that mirror the web knowledge base's own grouping — and dragging a file between those folders locally regroups it on the web too, without renaming the underlying page or breaking a single link into it.
• Wikilinks, graph, backlinks. They are ordinary notes, so Obsidian's own machinery works on them. No proprietary block, no custom view, nothing to un-pick later.
• It doesn't have to take over the vault. Set Settings → Sync folder before the first sync and everything — pages, the plugin's .kb/ state, its .kbignore — lives under that one folder. A note anywhere outside it is never read, never touched, never counted.
• Your edit is never quietly eaten. The cloud wins on pull, but your conflicting version is copied to .kb/bak/ first, and the Activity panel gives you a Restore button for it. On push, a page changed on both sides is reported as a conflict and your file and the sync journal are left exactly as they were. Push never deletes cloud pages.
• Nothing gets published by accident. A Markdown file whose frontmatter has no visibility: key is skipped by push by default, because the server would otherwise default it to guest — publicly visible. You add visibility: owner or visibility: guest deliberately, or flip an advanced setting if you really want it pushed as-is.
• Ambient, with real off-switches. Pull runs on an interval (default 5 minutes), and push fires quietly about 45 seconds after you stop typing. Set Auto-sync to 0 to stop the pull; turn off Auto-push local edits to stop the push. The two switches are independent, and a routine ambient push never interrupts you — it reports into the status bar and the Activity panel instead of a toast.
• Your token is in the OS keychain. It lives in Obsidian's secretStorage, never in the vault — so obsidian-git or Obsidian Sync never carry it off somewhere. Only the non-secret settings (server, slug, interval) sit in data.json.
• No telemetry. The plugin talks to exactly one host: the server URL you set in Settings. No analytics, no crash reporting, no CDN fetches, no third parties.

And if you want out: the vault copy is already the whole thing in plain Markdown, and Export / Delete on the site downloads every page as a zip with the folder structure intact.

Installing it today

It is not in the Obsidian community plugin store yet — that submission is in progress. Until it lands, BRAT is the way in.

Prefer not to add BRAT? Download main.js and manifest.json from the latest release in the same repo and drop them into your vault:

Requires Obsidian 1.11.4 or newer, for the OS-keychain secretStorage API. Works on desktop and mobile.

Where this honestly is