Logseq Style Fold

Your lists stay folded the way you left them — written the way Logseq writes it.

An Obsidian plugin that remembers how each list item was collapsed, by writing a Logseq block property into the note instead of keeping the state somewhere outside it.

English · 简体中文

Why

Logseq stores a folded block as a collapsed:: true property right under it. Obsidian does not understand that line: a vault that came from Logseq shows it as plain text, and Obsidian's own folds are forgotten as soon as the note is closed.

This plugin reads and writes that marker. The Logseq style is the default, so notes stay compatible with Logseq. If you prefer something else, set your own marker — an HTML comment <!-- collapsed:: true -->, an Obsidian comment %% collapsed:: true %%, or any line of text you like.

What it does

Fold something in a list, close the note, come back tomorrow — it is still folded.

- Weekly meeting
    collapsed:: true
    - Data sources
    - Definitions check
- To do
    - Not folded yet

The marker sits one indent level in, right under the item it belongs to — the same place Logseq puts it. Whatever style you choose, the plugin hides it everywhere you look:

• Live Preview and Source mode — the line is removed from the view, newline and all. It is not dimmed or squeezed; it is gone, and the cursor treats the spot as one atomic step, so you cannot land inside it while typing.
• Reading view — the marker is stripped from the rendered note (including Dataview's inline-field rendering of collapsed:: true). A %% … %% comment is never rendered by Obsidian in the first place.

Nothing else about your note changes.

Markers

collapsed:: lines are always recognised — bare, inside %% … %% or inside <!-- … --> — whichever style you write, so switching styles never loses existing folds. collapsed:: false (which Logseq can leave behind) is treated as unfolded and is reused when you fold that item again.

Recommended if your notes go elsewhere: the HTML comment

If your notes are also published or read outside Obsidian — a blog, a GitHub repo, a static site, another editor — pick the HTML comment style:

• Clean everywhere. Every Markdown renderer drops HTML comments, so the published page shows no trace of your folds. A bare collapsed:: true or an Obsidian %% … %% comment would show up there as text.

• Easy to remove for good. The markers are a fixed, unambiguous pattern, so one regex search-and-replace across the vault (with multiline mode on) deletes them all and leaves everything else untouched:

  ^[ \t]*<!--[ \t]*collapsed::[ \t]*(?:true|false)[ \t]*-->[ \t]*\r?\n
  

  Replace with nothing. Only whole marker lines match; the same text inside a sentence is left alone. For a single note, the Remove all fold markers from this note command does the same.

How it folds

The folding itself is not drawn by this plugin — it calls the same CodeMirror fold that ⌥S uses. You get Obsidian's own arrow, the … at the end of the line, the same click to unfold.

Marker and fold are kept in sync in both directions:

• A marker in the file folds that item when the note opens, and again whenever another plugin or a sync rewrites the file and the fold gets lost. This direction only ever folds; it never unfolds something for you.
• Fold something yourself — ⌥S, the arrow, whatever you already use — and the marker is written for you. Unfold it and the marker is removed. Typing and rewrites of the file don't count as folding.
• Another plugin that folds on its own can wrap that in app.plugins.plugins["logseq-style-fold"].quietly(() => …), and those folds are not recorded as yours.

Why the state lives in the file

A JSON file in the plugin folder, keyed by line numbers or text hashes, falls apart on a note that keeps being rewritten: line numbers shift the moment anything is inserted above, and hashes break when the wording changes. A line written into the note travels with its own content through git, sync, export and any rewrite that keeps the block itself.

Commands

Bind any of them to a hotkey in Settings → Hotkeys.

Settings

Installing

Copy main.js, manifest.json and styles.css into <vault>/.obsidian/plugins/logseq-style-fold/, reload Obsidian, and enable Logseq Style Fold in Settings → Community plugins. Or add it through BRAT from MatsuriMW/logseq-style-fold.

Notes and limits

• Outside Obsidian, collapsed:: true shows up as text — which is exactly what Logseq expects. Pick the HTML comment style if you want it invisible everywhere else.
• Markers survive any tool that keeps the block they belong to. A rewrite that deletes or re-words the block itself loses its fold state.
• Code blocks, callouts, ordered lists and checklists are handled. Lists inside tables are not folded.
• Markers are matched by the item's own text fingerprint within its nesting level, so two identical items at the same depth in one note share a fold state.
• The plugin only ever writes its own marker lines; nothing else in a note is modified.