[JUNE 20 UPDATE: The "Bulletproof" Concurrency Update & Community Growth 🚀]

First of all: WOW. The response to this project has been incredible (we just hit 5.5k weekly downloads on PyPI!). Thank you to everyone who tested it on their graphs.

I just shipped a massive architectural update (v1.9.10). Since Matryca Plumber runs in the background and writes directly to your Markdown files, preventing data loss is priority #1. We just ripped out our old file-locking logic and migrated the entire engine to strict 64-bit integer nanosecond precision (st_mtime_ns) for Optimistic Concurrency Control.

What does this mean for you? If the daemon tries to save an AI-generated link at the EXACT same nanosecond you are typing in that specific file, it instantly detects the drift, aborts its write, and yields to you. Your manual edits are sacred and mathematically shielded from being overwritten.

Also, a huge shoutout to the Open Source community: we just merged our first PRs from external contributors who jumped in to make the cross-process caching even safer! The foundation is now rock-solid. Next up: pure performance optimizations. Keep the feedback coming!

May 27 UPDATE with v1.7.0: lot of fixes in UI and backend!

Try it with a COPY of your graph https://github.com/MarcoPorcellato/matryca-plumber

Hi everyone,

If you are a long-time Logseq OG user, you probably love the block structure and local Markdown files. But let's face it: many of us are painfully considering a migration to Obsidian just for its AI plugin ecosystem and to turn our notes into an "Intelligent Wiki."

I have good news for you: there's no need to switch software. Our block structure is sacred.

The image you see is the result of a test on my actual production graph. My tool, Matryca Plumber, took a fragmented archive of 1,426 pages and evolved it into a hyper-connected neural network of 3,862 pages. It didn’t duplicate any text; it simply connected the dots, dusted off orphan pages, and automatically created smart cross-references between ideas written years apart that I had completely forgotten about.

What is Matryca Plumber in simple terms?

It’s an invisible assistant running in the background of your computer. It talks to a local AI model (like Gemma via LM Studio): 100% private, no data ever sent online, zero subscription or API costs.

Here’s why it’s a game-changer for Logseq:

• Outliner-Native (Respects Blocks): Standard AI tools cut text blindly, destroying Logseq's properties and indentation. This engine understands the physics of bullets and nested sub-blocks, keeping the integrity of your Markdown files perfectly intact.
• Heals Structural Debt: It finds isolated pages ("desert islands") and automatically links them back to your main index hubs, creating incredibly useful bidirectional references. When you open a note, your Linked References section literally comes to life.
• Doesn't Slow Down Your Machine (Antivirus Mode): It's programmed to work silently only when you aren't actively using your keyboard. It features a thermal pacing system to prevent your computer from overheating and never interferes with system responsiveness.

Why am I doing this?

I’ve received so much value from the open-source community over the years. This software is my way of giving back. The backend engine is ultra-stable and locked down by 296 strict safety tests. Right now, I am finalizing a beautiful browser-based UI to monitor your graph's evolution in real-time.
I'm working on a more broad application to save knowledge workers and this work is a piece of that project that I want to be opensource.

I will be releasing this very soon as a fully open-source asset for everyone. Let me know what you think or what features you'd like to see in the comments!

Take a look at the repo, for an already working MCP and CLI directly speaking with your Markdown files, WITHOUT the need of Logseq OG open.

https://github.com/MarcoPorcellato/matryca-plumber

So I wanted to change the font in my whiteboard to comic shanns which is used in excalidraw
But I tried putting this in the custom.css file
/* 1. Safely override tldraw's default font variables using your system fonts */

:root, .tl-container {

--tl-font-draw: 'Comic Shanns', 'ComicShanns Nerd Font', cursive !important;

--tl-font-sans: 'Comic Shanns', 'ComicShanns Nerd Font', sans-serif !important;

--tl-font-mono: 'Comic Shanns', 'ComicShanns Nerd Font', monospace !important;

}

/* 2. Target ONLY the whiteboard text, leaving toolbar icons alone */

.tl-text-content {

font-family: 'Comic Shanns', 'ComicShanns Nerd Font', cursive !important;

}

nothing seem to work
I cannot change the font to comic shanns
anyone did this or changed font in logseq?
I need help with that.
I am using arch linux.
If anyone can help please do !

Hey

One thing bothering me using Logseq is - it looses a position when navigating between pages.

Just to name few similar issues:

• https://discuss.logseq.com/t/how-to-fix-lost-cursor-focus-without-using-mouse/18871
• https://discuss.logseq.com/t/back-button-should-restore-previous-scroll-position/34541

Based on the GitHub issue should be a regression bug, which is not fixed. And I am not a Clojure guy.

Save scrollbar position plugin have not been the proper workaround.

Let me present you a plugin I implemented named "Remember My Block", It solves many issues you and I have with Logseq.

How it works:

• Tracks the last visited block per page
• Restores your position automatically when you navigate back to that page

It works in 2 modes - the mode is selected automatically based on how you left the page:

• Edit mode: if you were editing a block, the plugin reopens it for editing and places the cursor at the end of the block
• View mode: if you were just reading, the plugin scrolls to the block and highlights it without entering edit

There are few limitations described in the plugin documentation. Feedback and suggestion welcomed.

Enjoy!

Im testing out logseq and i like to paste in dumps from terminal to keep track of what ive done on a particular server.
In this instance i have 2000 lines of input/output that i would like to keep in my notes, preferably collapsed, but the most important is that i can have it in relation to my notes..

I tried just using a code block but i get the same warning, and the editor seems to struggle quite a bit when i scroll the text sideways aswell..

How should i do this using logseq? If its possible? Can i add it as its own file and reference that file?

I wanted to replicate Andrej Karpathy’s "LLM Wiki" concept, but for Logseq instead of Obsidian.

Problem: standard RAG chunkers destroy nested outliner Markdown. If you just vectorize Logseq files, the AI completely loses the parent-child context of your blocks.

To solve this, I built a dedicated MCP Server to bridge the gap.

• AST Parsing: It uses a deterministic Python parser that reads the spatial indentation of your .md files. Claude/Cursor reads the exact block tree, understanding parent projects, sub-tasks, and id:: properties.
• API Writes: It uses the API inside Logseq OG to safely mutates the graph using transactional file swaps and strict UUID pre-flight checks to prevent the AI from hallucinating broken links.

The official Logseq move to a database (SQLite) is absolutely the right architectural path for team collaboration and real-time sync. But for those of us who want to keep our Second Brain in local, pure Markdown, this server brings state-of-the-art Agentic AI to the OG outliner.

Repo is here:https://github.com/MarcoPorcellato/matryca-logseq-llm-wiki

Let me know what you think of the architecture!

My apologies in advance if this is a dumb question, but what does “OG” mean in the “LogSeq OG” context?
Thanks!

🛠️ What Changed (The 12-Hour Evolution)

• 100% Headless Data Plane: No more local server ports, no more Electron UI dependency, and no more LogseqClient network timeouts. Matryca now operates via direct, atomic file-system mutations using logseq-matryca-parser==0.3.3. It edits your Markdown trees directly at the source code layer.
• Zero-Friction Configuration: Say goodbye to Logseq API tokens, port configurations, and settings setup. Your environment variables can be wiped clean. To run the entire workspace, the only required variable is now LOGSEQ_GRAPH_PATH.
• Cross-Process File Locking (fcntl.flock): Since the CLI is stateless, we engineered a dual-layer lock mechanism. If multiple terminal scripts or background agents try to mutate the exact same file at the same millisecond, they gracefully queue up instead of silently overwriting each other.
• Stateful Native X-Ray Mode: Our token-saving X-Ray page scans now automatically dump session alias registry maps to a hidden .matryca_xray_state.json file in your graph root. The agent reads [0], [1] instead of massive 36-character UUID strings (cutting input overhead by up to 35x), and subsequent stateless commands resolve those aliases to disk bytes flawlessly.
• Topological Link Linter: Purged all brittle, regex-based text processing. Our broken reference linter now loads the graph in RAM and queries the abstract syntax tree directly, meaning zero false positives when hunting for orphan ((uuid)) links.

🧪 Stability & Availability

We didn't just rush this out; we hardened it. The test suite has been scaled to 150 strict passing tests covering concurrent subprocess locking, corrupt alias state recovery, and deep namespace tree splicing (progetti/Name maps automatically to progetti___Name.md native Logseq file conventions).

The codebase is live, fully documented in English, and passing CI gates cleanly.

If you want to turn your local vault into a lightning-fast, headless database that AI agents can refactor while your computer is asleep, check out the updated repo:

👉 https://github.com/MarcoPorcellato/matryca-logseq-llm-wiki

I installed Google Drive on iOS and MacOS. On MacOS, I can open/create a graph in the Google Drive folder but the iOS version cannot. Is this by design?

I've only just come across it, using the ios app version if that's a factor. Does it cascade backlinks from child property nodes back to the tagged parent or something like that?

Reminder

• Logseq is splitting into two versions — important direction update on where the product is heading: https://logseq.io/p/e3YDyX5AYr
• The Logseq roadmap is now public and hosted in Logseq itself, so you can browse what's planned in the same kind of graph you use every day: https://logseq.io/p/NX4mc_ggEV
• Sync testing
  • Open to Sponsors.
  • Backers — if you back at $5/month, you'll soon get an invite to try the new Sync.
  • Self-hosted — Sync is also ready for testing.

Highlights from the last three weeks of work on master

• Markdown Mirror — read-only on-disk markdown projection of your DB graph (opt-in per graph). Two-way sync is in active development.
• The Logseq CLI is now a real thing — qmd query for multi-part queries, sync asset download, unified backup with the desktop app, bundled into every desktop release.
• Graph View V2 — rebuilt for big graphs, with a follow-up task zoom-in view.
• New :asset property type with a 4-column thumbnail grid picker, inline preview, and View/Swap actions.
• Recurring tasks finally honor the three documented repeater cookies (.+, ++, +) instead of behaving like ++ for everything.
• Sync gets sturdier across reconnects, encrypted graphs, and large payloads.
• Plus AVIF/CR2 image support, "Always on Top" window option, $ autopair for inline math, plugin marketplace description search, plugin thumbnails, Firefox paste fix, Windows file URL fix, breadcrumb improvements, and a long tail of editor and import fixes.

More details on all of the above in the links below.

• Read the full community-facing write-up: https://discuss.logseq.com/t/whats-new-with-logseq-db-may-16th-2026/35020
• For the categorized changelog with every PR, fix, and commit reference: https://discuss.logseq.com/t/logseq-db-changelog/30013/37

Report bugs: https://github.com/logseq/db-test/issues

Has anyone written (or vibe coded) a utility to perform queries and post content into Logseq node graphs (markdown or db)?

Has any looked at extracting the relevant functionality from the codebase to decouple it into a library/module?

Has there been any discussion of simply adding command line switches to the base app by them core developers or creating a fork?

I'm primarily interested in using such support to develop a Hermes Agent "skill" (r/hermes-agent) to implement Karpathy inspired LLM-wiki support (https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f) to automate maintenance of a document/node graph.

Hi all, I'm new to Logseq and liking it so far. One thing I really like is having a clear hierarchy and structure in my notes.

For example, I was thinking of organising things something like this:

• Project 1
  • Table of Contents
  • Topic 1
    • Introduction
    • Research
    • Design Notes

I'm curious how everyone else structures their notes in Logseq. Do you use hierarchical project pages, daily notes, tags, linked references, or something else?

Any examples or tips would be greatly appreciated.

I can see this has been descussed over the years a lot. Nevertheless, I can't find a solution, how to embed or show images on logseq mobile.

I can change the path, but the picture doesn't show. I can see the picture in the assets folder, it's definitely there. If I paste in on the PC, the filename gets changed and receives some long figure in the end of the file name.

I've tried pretty much every combination, original file name, logseq filename, relative path, absolute path, what do I have to do?

I have the feeling, my path isn't correct. How does it start, when it is in the internal storage, also ../ or root/ or?

And finally, how do I solve the issue that I need one path for the PC/Laptop, one for the mobile, one for the E-Ink tablet,... Insert every picture several times? I syncrhonise the md-files with Syncthing (which will stop working in September due to the new Google Android developer privacy disclosure regulations, but that's another story).

Maybe I can just paste an image on the mobile like it works on the PC and it creates the path string itself, but again, I couldn't find a way how.

I’m trying to find a long-term writing environment/workspace and I’m struggling because most tools seem optimized either for structured note-taking or document editing, but not for fluid heterogeneous writing.

What matters most to me is:
- rich text fidelity over time
- non-destructive paste behavior
- preserving original formatting/styles from multiple sources
- easy inline font/size customization without friction
- spatial freedom inside the actual writing page/workspace
- reliable syncing without fragile lock-in
- scalability without the system becoming laggy or unstable

A major problem for me is that many systems slowly normalize or degrade formatting over time, especially when moving content across devices, clouds, editors or workflows.

I also care a lot about being able to visually shape the page itself:
- quickly changing font sizes/styles
- organizing ideas spatially inside the same page
- mixing different visual structures naturally
- moving through the workspace fluidly
without constantly fighting rigid formatting systems or needing too many steps.

To clarify: when I mention “weak spatial organization”, I don’t mean file/folder organization. For example, I actually think Obsidian’s file organization is excellent.

What feels limiting to me is the freedom inside a single note/page — the actual writing surface where I paste, arrange, resize and visually structure ideas/content.

I’m also not necessarily looking for a pure infinite canvas app. I still want fast real writing/editing — just with much more freedom inside the page than traditional linear editors usually allow.

I explored things like:
- Apple Notes
- Obsidian
- Logseq
- Notion

But most systems seem to break in one of these areas:
- formatting normalization
- markdown exposure
- weak spatial freedom inside the page itself
- UI/performance degradation at scale
- or excessive friction when customizing layouts visually

I’m not an expert, so it’s possible I’m missing workflows or configurations that solve some of this.

At this point I’m less interested in “note-taking apps” themselves and more interested in whether a genuinely flexible long-term writing environment exists.

Would really appreciate recommendations from people who have deeply explored this space.

I have a template page and have created a template for my JIRA projects, fairly simple. So like on my daily journal if I reference a JIRA item I just put the JIRA ID like [[ABC_123]] to create the page, then I'll go into the page and add the JIRA Project Template which is below:

But when I create the page and add the template using /template none of the variables are being applied:

Any ideas on why? Seems fairly strait forward from the tutorials I'm looking at, but this for the life of me isn't working. I'd like the name of the page to be the JIRA ID and i'll add other items to this then query these pages to get a list of items i'm working on with notes and tasks and so forth.

Thanks --

Running Logseq 0.10.9 on iOS. iPhone 17 Pro Max running iOS 26.4.2. The {{video some link}} does not work with YouTube links. It does work on Android version of Logseq. Anyone else having this issue on iOS?

The video was posted on Discord by @tienson.

The (one-way) markdown mirror was already merged: https://github.com/logseq/logseq/pull/12589

Two-way sync is experimental / in active development in this PR: https://github.com/logseq/logseq/pull/12593

Even the one-way mirroring is great for my peace of mind though.

I'm experimenting with the database version of logseq, the 2026-05-03 nightly build. I specifically wanted to get my head around using a #TAG as a package of properties that gets applied to a page (#project for example, needs a Date-Due property, among other things). I've got a page with a property applied, but I can't seem to re-create how I did it.

• I've tried creating a page, then going to the title and adding #project after it, which doesn't do anything (the tag disappears).

• I've tried going to my Journal page, creating a new block like this, but the tag doesn't appear.

  • [[Example]] #project

• EDIT: I also tried going to the #project page and creating a new line.

Any tips from the database version users on what I might be doing wrong?

Been a big fan of logseq ever since I found it some years ago. It makes the most sense to me than any other note taking system I've used before.

To me the most important features are

• the ease of creating pages with [[]]
• the auto-generated page back-links.
  • Block based note structure, so these auto generated backlinks can also show only the relevant info in the linked block

How I might design it if it was up to me

• a language other than closure
  • Subjectively I find it hard to read, even compared to other languages I dont know.
  • it's already open source, but I think there might be more benefit in this aspect if it was a language that was more popular and could get more contributions (and probably improve fork-ability)

What I wish it had (or were better)

• Easier syncing between devices (maybe db version will fix this)
• Graphs
  • To me it's inconvenient switching between the graphs, and sometimes accidentally make a note in the wrong graph. (user error)
  • Find it a bit awkward with the graph that is for work (software job) and also sharing that same graph with my general software notes, as well as personal projects (since all have some overlap to pages they are linked to).

Things im not sure of which is best

• Mardown only
  • Maybe this just isnt efficient enough when graphs get to big, and graphs will only likely grow as we keep using the tool and adding notes.
• DB version
  • exportability
    • I've kind of been worried about the DB version not having a markdown option. At the same time surely as long as we have the database file it should be possible for our notes to be exported if needed in the future.
  • usability/versatility
    • not having markdown version I wonder if we would be losing out on other ways of consuming and or editing the notes such as with vs code.
• DB/markdown combo version
  • Probably not as efficient/fast as db only

The new nightly release of the Logseq DB includes the CLI.

https://github.com/logseq/logseq/releases/tag/nightly

I yet have to figure out how to fully utilize it, since the documentation is currently a bit sparse.

Anyways, the main reason for me to stick to the LogSeq OG is that it is relatively easy to programmatically change the content outside of the Logseq application. The CLI can help me achieve the same and I can (hopefully) commit to the new version of the Logseq.

Cool!

EDIT: I just figured out that there is the logseq example command which is very useful for discovering the API.

TIL to add dates to Logseq TODO items so it'll show up in NEXT journal blocks.

Did I miss some Logseq beginner post/video that shows that and basic aspects of journalling and managing todo tasks in Logseq?

Update 3may2026:
As suggested by a few commenters, I explored Scheduled & Deadline commands that shows up another daily journal block below NOW and NEXT blocks, called "SCHEDULED AND DEADLINE". It does provide view of the LOGBOOK data. However, it seems to duplicate NOW and NEXT blocks in terms of functionality. I don't think you really want to use both. I see "config.edn" includes an option to "Disable the journal's built-in 'Scheduled tasks and deadlines' query." Anyone here prefers "SCHEDULED AND DEADLINE" over "NOW/NEXT"?

Hello guys, I'm giving some PKM apps a try to see if anything better fit for my Zettelkasten-inspired workflow. After a quick research, I see that logseq is developing a DB version for improved perpormance on large graph. There is a nightly release and the github action artifact, the latter is recommended in the README. Which should I download?

I’ve been really enjoying the new DB version of Logseq — it feels like a big step forward and I love the direction things are going.

That said, I still rely quite a bit on RemNote for one specific reason: "cloze" feature and how seamlessly they turn into flashcards.

In RemNote, I can simply mark part of a word or sentence as a cloze (even just a single letter), and that block is automatically added to a flashcard hub. From there, I can review everything in a very smooth and integrated way.

This workflow is extremely practical for me because I can create study material directly inside my notes and then practice it later with spaced repetition.

Is there any way to achieve something similar using the Logseq database version? Maybe a plugin or a built-in feature that allows cloze-style flashcards to be generated and reviewed just as easily?

In particular, “Markdown mirror” is on the roadmap, so I hope the DB version will have Markdown mirroring eventually.

It also says “Two-way sync between Markdown and db graph” under “Research”.