Skip to content
Shared Tasks for Obsidian · MVP 0.3

Shared tasks and sections inside your private notes.

Share one task, or a whole section of a note — not the vault. A visible pane leads you from Share to Invite to Join, so you don't have to learn the commands. It lives in both notes and syncs both ways, end-to-end encrypted. No account needed.

The project server sync.openlfcp.org (quotas and a privacy note apply) or your own server.

alice / Launch plan.mdprivate
## Launch
Notes only Alice can read.

- [x] Prepare API contract 📅 2026-10-20 ✅ 2026-10-06- [ ] Check the venue contract
- [ ] Draft the announcement
bob / My week.mdprivate
### Monday
- [ ] Gym at 7
- [ ] Call the bank
- [x] Prepare API contract 📅 2026-10-20 ✅ 2026-10-06
Bob's own notes stay here.
Highlighted line: shared and end-to-end encrypted. Everything else never leaves its device.
The name

What does OpenLFCP mean?

It's short for Open Local-First Collaboration Protocol: an open, written-down way for apps to share small pieces of your data without moving the rest. Shared Tasks for Obsidian is the first app built on it.

Open
The protocol, both SDKs and the server are public and Apache-2.0. Anyone can read the spec, run the tests or build their own app on it.
Local-first
Your data lives on your device and works offline. The network is only for meeting the people you share with.
Collaboration Protocol
The rules two apps follow to share one object — a task or a section — with end-to-end encryption, invitations and revocation.
How it works

Share a task or a section, not your vault.

  1. 01

    Share it

    Put your cursor on a heading and click "Share section…" in the Shared Tasks pane. A preview shows exactly what will be shared; a small hidden marker links it. The rest of your note stays private.

  2. 02

    Invite someone

    Choose Read or Read + write and copy a one-time link. They paste it into "Join with a link…", pick the note and the place, check the preview, and the section appears. No account needed.

  3. 03

    Work as usual

    Tick a task, rename it, add items inside a section, even offline. The change reaches the other note. Conflicts show beside the content as a choice, never written into your text.

Everything about sections is in the pane and the card, and both work from the keyboard. Single tasks are still shared with commands, which keep their names.

New in MVP 0.3 · Shared Tasks 0.5

Collaboration without learning the commands.

A visible Shared Tasks pane and a card on each shared section take you from one step to the next. Your notes stay plain Markdown and the sync protocol has not changed.

Share and invite

Share, then invite, in one place.

On a heading, the pane offers "Share section…" and shows what will be published before you confirm. When the section is ready it offers the invitation: Read or Read + write, one-time link. Shared Tasks never sends the link for you; you choose how it travels.

The Shared Tasks pane beside a note: a preview of what a share will publish, then the invitation with a choice of Read or Read plus write.
Join and insert

Paste a link, then choose where it goes.

"Join with a link…" shows each step as it happens, then asks which note should hold the section and previews the result. A join that was cut short can be checked again; it is never started twice.

The join flow in the pane: steps of the join, then a choice of note and a readable preview of the section to insert.
Problems with a direct way to the fix

A problem hub with a way out.

The pane lists what needs attention, such as a conflict or a line that went missing, and opens the matching dialog or "Repair shared sections in this note". Text not yet sent is told apart from what the server accepted.

The Shared Tasks pane lists a problem with the shared section and offers Repair shared sections… right under it.
Nothing half-done is lost

Unfinished steps stay in view.

A share resumes by itself after a restart; an unfinished insert or join is listed in the pane, where you continue it or check the result. Short tips explain an action when it is offered; "Hide tip" hides one, and no tour opens on install.

The card of a shared section: what is shared, who has access, and buttons to invite, check the resource status or open the pane.
Two Obsidian windows side by side, Alex on the left and Sam on the right, both showing the same shared section with four tasks.
Two vaults (Alex on the left, Sam on the right), one shared section, in sync.

Shared Tasks 0.5 is desktop-first. Shared sections are read-only on mobile, and the new pane has not been tried on a real phone or tablet. Recurrence (🔁) stays local by design. Known limits in the 0.5.0 notes.

Since MVP 0.2

Share a whole section of a note.

A section is a heading and everything under it — tasks, subtasks, paragraphs and lists, in order — down to the next heading of the same or a higher level. Each one is its own collaboration, with its own key and its own invitation. Whatever is added inside it later is shared too.

Status you can read

A double tick (✓✓) after a shared heading means "shared". A separate icon shows sync progress: saved here, sending, offline, or "Needs your attention". It is not a read receipt — it does not mean someone else has seen your change.

Access, verified

The details card shows who has access, as last verified with the server. "Remove access…" removes someone's future access and rotates the key. It cannot erase copies they already received, and the confirmation says so.

Conflicts kept, not guessed

A task moved two ways, or a field changed on both sides, waits as a choice in "Review conflicts…". Nothing is lost while you decide, and your note is never overwritten under you.

Copy or detach

"Copy readable text" gives you the plain text without any sharing markers. "Copy shared section" makes another copy of the same section — it grants nobody access. "Detach" keeps the text in your note and stops sharing it.

Bring in 0.3 tasks

"Share section…" can move your existing 0.3 shared tasks into a section. That is an explicit copy with new identities, not an automatic migration — "Restore note before section import" undoes it in the note.

Repair a boundary

If a section's markers get damaged by hand, "Repair shared sections in this note" puts the boundary back, points to lines it cannot match, and lets you choose your version or the shared one.

Plain text, always

Markdown stays Markdown.

A shared task is an ordinary task line with one hidden comment that links it. A shared section adds a hidden marker after its heading, one at its end, and one line beside each item. Live Preview hides them; Source mode — or "Show or hide sharing metadata" — shows them.

  • Tasks keep the Tasks-plugin syntax: dates, priorities, tags.
  • Tables, callouts, fences and blockquotes travel as raw blocks — not every Markdown feature is modelled.
  • Detach a section or a task any time: the text stays, only the markers go.
Launch plan.md · rawMarkdown
## Launch plan
<!-- lfcp-section: lfcp1:3fk…#section:01J… -->
- [x] Prepare API contract 📅 2026-10-20
  <!-- lfcp-ref: lfcp1:3fk…#task:01J… -->
- [ ] Check the venue contract
  <!-- lfcp-ref: lfcp1:3fk…#task:01J… -->
<!-- /lfcp-section -->
Privacy, said plainly

Everything you didn't share stays on your device.

Stays local

The rest of your note, your other notes, your folders and file names. None of it ever leaves the device. Your device's sync data is encrypted at rest.

Travels encrypted

The shared task's or section's changes. They are encrypted and signed on your device, and only the people you invited can read them.

The server sees

Ciphertext it cannot read, plus metadata: when something changed, how big it was, and which IP sent it.

Using the project server, sync.openlfcp.org? Read its privacy note and terms. Prefer full control? Run your own server.

What runs where

Platforms, Markdown and limits.

Shared Tasks 0.5 requires Obsidian 1.13.4 or later.

Platforms
PlatformShared tasksShared sectionsNotes
macOS (desktop)FullFullThe platform the performance budgets are measured on.
Windows, Linux (desktop)FullFullFunctional; not performance-qualified.
Mobile (iOS, Android)FullRead-onlySections arrive and are shown; edits there stay on the device. Sharing, inviting and removing access are desktop-only.
Markdown inside a shared section
ContentSharedHow
Tasks, subtasks, paragraphs, list itemsYesModelled with their order and nesting.
Obsidian Tasks fields (dates, priorities, tags)YesKept in the Tasks-plugin syntax.
Tables, callouts, code fences, blockquotesYesTravel as raw blocks, not structured content.
Some Tasks tokens (🔁 🛫 ➕ ❌ 🔼)LocalStay on your device; the preview shows which.
Headings inside a sectionNoA section has no nested headings; sharing offers to split it.
Size

About 200 tasks with their notes is the qualified size. A much larger section (2,000 tasks) works, but each edit blocks the editor for seconds.

Long history

After many thousands of edits a section becomes slower. The details show how large its history is and, past about 200,000 characters, suggest starting a new section for new material; nothing happens automatically.

Project server quotas

sync.openlfcp.org currently allows one identity up to 200 collaborations, 50 new a day per network, 256 MiB per identity and 128 MiB per collaboration. A server you run yourself sets its own.

Not yet

Rejoining a section you were removed from, comments inside a section, and moving a collaboration to another server.

Get started

Install and upgrade.

Release

Install 0.5.0 from Community plugins

In Obsidian, open Settings → Community plugins → Browse, search for "Shared Tasks", then install and enable it. Obsidian keeps it up to date. Then click the Shared Tasks icon in the ribbon.

Open in Community plugins →
Beta

Test a pre-release with BRAT

Install BRAT, run "Add a beta plugin for testing" with openlfcp/obsidian, and choose Latest version — a pinned version never updates. Pre-releases come only this way and are not offered in Community plugins.

Read the 0.5.0 notes →
Upgrade

Coming from 0.4.x

Your identity, shared sections and queued edits are kept, and no tour or dialog opens: the sync data format is unchanged. To go back, install 0.4.2 over it. From 0.3.x the first start of 0.4 or later upgrades the sync data, with no way back to 0.3.x — keep a copy of your vault.

Upgrade and rollback →
Built in the open

Obsidian is the first app, not the last.

LFCP is an open protocol for sharing objects instead of whole documents. Any app can speak it. Shared Tasks implements the MVP 0.2 subset of LFCP-WIRE-01 (unchanged in MVP 0.3), not the whole protocol.

npm install @openlfcp/client
The release

What's in MVP 0.3.

MVP 0.3 is about how it feels to collaborate: the plugin changes, and the protocol, the server and the Markdown format do not. The components and the versions they ship at.

MVP 0.3 components
ComponentVersionWhat it provides
obsidianShared Tasks 0.5.0The Shared Tasks pane and section card, guided share, invite and join, a problem hub, and resuming unfinished work after a restart.
sdk-ts@openlfcp/* 0.2.2The TypeScript SDK the plugin builds on.
specmvp-0.2-baseline.12The protocol subset and the test vectors, unchanged.
server0.3.2The reference sync server, unchanged. It never decodes sections.

Earlier: MVP 0.2 release notes, which introduced shared sections.

Status · MVP 0.3

Early software, tested in the open.

Encryption, sync, revocation, offline edits and restarts are covered by automated tests across the TypeScript and Rust SDKs, which pass the same conformance vectors. Performance is measured on macOS; Windows and Linux are functional but not performance-qualified. The specifications are still drafts, so don't use it yet for data you need to protect.