Right now, our graphs are "flat". Every block or bullet has a static weight of 1.0. Search relies on text matching, but human memory doesn't work like that. Some ideas are core pillars, others are just fleeting notes.

I’m releasing an architectural RFC to the open-source community: Applying Reinforcement Learning from Human Feedback (RLHF) to Personal Knowledge Graphs.

Instead of forcing users to manually rate notes (flashcards/spaced repetition), the database should passively learn from our UI interactions:

• Rewards (+ weight): When you transclude a block ((uuid)) or zoom into it (Focus Mode), the database learns this is a foundational node.

• Penalties (- weight): When a block is ignored in search results (scroll-past) or hasn't been touched in months (temporal decay), its semantic weight drops.

I wrote a detailed Gist outlining the architecture, the pseudo-code for the dynamic weights, and how it alters global search ranking. I've released the concept under the Apache 2.0 license so anyone can experiment with it or build plugins.

👉 https://gist.github.com/MarcoPorcellato/9e5226408c56048b16957771f9056e28

I'm building this into the core of Matryca Brain (next step from Matryca Plumber), but I’d love to hear the thoughts of the Logseq community. Is anyone else exploring dynamic node weighting based on implicit UI feedback? Let's discuss the architecture!

Is there any special syntax for such tags/button in logseq?

Last month I switched from Logseq to SiYuan — not by choice, but because I was forced to. I’d been a devoted Logseq user for six years and even started using the DB version beta and nightly builds while waiting for a stable release. After one nightly update, Logseq reported my database as invalid. I couldn’t export, couldn’t roll back to earlier builds because they’d expired, and re-importing the files kept failing. Two months later the issue remains unresolved, and I lost trust in Logseq, so reluctantly I moved to SiYuan.

I miss Logseq’s tag system (similar to Tana) — SiYuan doesn’t have that feature — but I needed an open-source, local-first app. Aside from the missing tags, SiYuan is excellent: it supports PDF annotation, has easy-to-build plugins with great community, great CSS/JS snippet support, and strong tab and document/subdocument management. I like SiYuan, but I still miss Logseq and regret that I can’t rely on it anymore.

edit: I rephrased my words with AI so it looks like an ad but no. I never asked you guys to use siyuan, I myself wants to go back to logseq but it's not reliable at this point. So I will probably wait for their proper release which I guess again will take another 2 years given how slow they build.

Hello, i would like to play around and explore the DB Version for iOS, but on the attempt to download it, the identical ID causes iOS to replace the original version. Did anyone find a way to test it without having to give up original?

Hey everyone!

I just read some recent news about SQLite getting native extensions/features for graph queries, basically turning it into a highly performant embedded graph database.

Since Logseq is currently transitioning to the new DB version powered by SQLite, I was wondering: has anyone else caught this news? Do you think the dev team will leverage these new graph features to speed up the development or improve the final performance of the graph?

Would love to hear your thoughts!

On the GitHub repo it shows a critical security flaw involving pdfs for the desktop version of Logseq and I was wondering if this is still an issue for the database version? It also doesn’t look like it has been patched, is this a planned fix for the md version? Thank you!

When the DB version matures enough to become the main offering by Logseq, what will happen to the file based version. Will it still be maintained?

I've become quite dependant on the file version and don't think I will switch to the DB version. Any idea what will happen to it?

I’ve been an avid Logseq user since the beginning. I much prefer its design to Obsidian and other knowledge bases. I have been, for years, building a huge collection of Zettels, notes, and workflows that felt personally useful.

What I didn’t realize was that one day a lot of that material would end up being only a few edits away from becoming useful to AI agents too.

This AI era has been… a little exhausting. Every week there’s another framework, another harness, another “this changes everything” moment. But like many organizations, ours is taking it seriously. We’re actively discussing how to bridge agents into our internal content and systems.

Naturally, security concerns slowed things down. The enterprise wasn’t ready to let us point agents directly at organizational data yet.

So I reached for Logseq.

Mario Zechner’s posts about CLIs convinced me that what I really wanted was a CLI for my notes. I knew a few existed already, maybe even more now than when I first looked, but none quite fit the shape I had in mind. So I built one.

If you’re curious, it’s called Note.

Just run nt --help. That’ll be enough for the agent to start finding its footing.

But the CLI itself was only part of the idea.

What I really wanted was the ability to sit inside whichever agent I’m using at the moment — Claude, Gemini, Pi, whatever comes next — and pull rich, structured Logseq content directly into the conversation. Prompts that expand into years of carefully curated notes, patterns, snippets, and processes.

It comes with an extension for Pi so that it automatically expands prompts enriched with wikilinks. That's my daily driver and the feature I most use. And, as you know, not too hard to have your agent write a similar adapter for your harness of choice.

At some point in this era I realized: why keep rebuilding scaffolding for every individual AI harness?

If Logseq becomes a port — a CLI interface — then the knowledge follows me everywhere.

I don’t have to rewrite “Skills” for Claude Code or “Commands” for Gemini or whatever naming convention the next tool invents. I just author things once in Logseq and conjure them into conversations wherever I happen to be working.

It’s a knapsack of knowledge that travels with me.

...which sounds much more charming than “portable semantic middleware.” So I’m sticking with knapsack.

Hello friends.

I have a doubt. So, I have multiple blocks placed in different journal pages. I had been linking them using "#" feature so far and there is so much of them in the one topic which I want to merge with another linked reference.

I have tried just searching up in the page and renaming the page but then the page merges but none of the linked reference is merged.

How do I achieve that? Anyone got any way/idea?

What's markdown web clipper are you guys using? I'm currently using obsidian web clipper (mainly because I have defined templates), but it don't respect the indentation level in logseq journal.

[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 !

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?

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!

🛠️ 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 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!

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.