Skip to main content
Cleft can write each finished note as a Markdown file, so your spoken thoughts can land in a Logseq graph as pages you can tag, link, and review.
Local Sync is one-way. Cleft writes files into your chosen folder. Edits you make in Logseq do not sync back to Cleft.

​
Choose your Logseq destination

1

Find your Logseq graph

In Finder, open the folder for the Logseq graph you want to use. The best target is the graph’s pages folder, or a folder inside it.
2

Open Local Sync in Cleft

In Cleft on your Mac, open Settings and go to Local Sync.
3

Pick the Logseq pages folder

Choose your graph’s pages folder as the destination. Cleft will write .md files there.
4

Record or update a note

Finish a Cleft note. Open Logseq and the new Markdown file appears as a page after Logseq indexes the folder.

​
What Logseq receives

  • One page per Cleft note. Filenames start with the note date, then a readable title slug.
  • Markdown body. Headings, lists, and summaries stay readable inside Logseq.
  • Inline tags. Cleft appends tags as #tag, which Logseq treats as tag-page references.
  • Source details. Cleft includes metadata such as title, created time, updated time, and source in YAML frontmatter.

​
Current limits

Cleft writes standard Markdown with YAML frontmatter. It does not currently emit Logseq’s native key:: value block-property format or journal-page filenames.
That means Cleft notes work well as project pages or inbox pages in a Logseq graph. If you want every note to become a Logseq journal entry, use the Cleft file as the starting point and move or reshape it inside Logseq.

​
Troubleshooting

Confirm Cleft is writing into the graph’s pages folder, then restart Logseq or refresh the graph. If you chose a folder outside the graph, Logseq will not index it.
That is expected. Logseq can read the Markdown file, but Cleft currently writes YAML frontmatter instead of Logseq-native block properties.
Local Sync is one-way from Cleft to your folder. If Cleft updates the same note later, it can overwrite changes made directly in the exported file.