Skip to main content
Cleft integrates with Logseq via Local Sync on Mac, iPhone, and iPad. Local Sync itself is free; Cleft Plus lets you point exports at your Logseq graph (or any folder you choose). On Free, exports land in Cleft’s Documents/Cleft Notes folder.

​
What you get

Point Local Sync at your Logseq graph’s pages/ folder and your Cleft notes appear as Logseq pages alongside the rest of the graph. Each note becomes one page with:
  • Readable filenames like 2026-05-06-meeting-with-jonny-12431.md (Logseq uses the filename as the page name)
  • YAML frontmatter with title, tags, timestamps, and the full transcript
  • Inline hashtags at the end of the body, clickable as Logseq tag-page references
  • Audio companion. The original .m4a recording sits next to the page if the audio toggle is on
Here’s what a synced note looks like: 
---
cleft_id: 12431
title: "Meeting with Jonny"
tags: ["work", "ideas"]
created: 2026-05-06T10:30:00Z
updated: 2026-05-06T11:15:00Z
source: cleft
transcript: "full transcript on one line, newlines collapsed to spaces"
---
AI-generated summary body goes here.

#work #ideas
In Logseq, this renders as:
  • A page named 2026-05-06-meeting-with-jonny-12431 in your graph
  • The AI summary as the body
  • #work and #ideas clickable as tag-page references
  • The YAML block visible as text at the top of the page
This is one-way sync: Cleft → Logseq. Edits you make in Logseq are overwritten on the next Cleft sync (same contract as Notion auto-send).

​
Setup

1

Pick your graph's pages folder

Open Settings → Local Sync and click Choose Custom Folder… (Plus).
  1. Select <your-graph>/pages/ (or any subfolder inside the graph)
  2. On Mac, Cleft creates a dedicated subfolder inside it. On iPhone and iPad, Cleft writes to the exact folder you select in Files.
  3. Use the selected folder and you’re done
Full setup guide: Local Sync
2

That's it

Open Logseq and your Cleft notes appear as pages alongside the rest of the graph. New recordings show up the moment they finish processing.

​
Logseq-specific tips

  • Inline tags work natively. Logseq treats #tag at the end of the body as a tag-page reference, so the inline hashtags Cleft appends light up clickability without any extra setup. Multi-word tags (#multi-word) and slashed tags (#work/meetings) both work.
  • No id:: collision. Cleft emits cleft_id: (YAML, single colon), not id:: (Logseq’s double-colon block-property syntax), so there’s no collision with Logseq’s auto-generated block IDs.
  • Recovery by ID. Every note carries a cleft_id field in frontmatter. If you ever rename pages manually, grep "^cleft_id: 12431" *.md finds the original note even in a mixed graph.

​
Limitations

  • No key:: value block properties. Cleft emits standard YAML frontmatter (----delimited), which Logseq parses but doesn’t surface in its native property panel (which expects key:: value syntax). The content is fully readable; it just doesn’t light up Logseq’s property UI. A Logseq-shaped format profile is on the roadmap for the Studio engine in 2.x.
  • No journal-page auto-population. Cleft’s filename format is 2026-05-06-meeting-with-jonny-12431.md, not Logseq’s journal format (2026_05_06.md). Notes appear as regular pages, not in the journal day view.
  • No block references. Cleft 1.x has no data model for blocks. A Cleft note becomes a single Logseq page, not pre-split into blocks. Inter-note references and block-level linking are coming with the Studio engine in 2.0.