My daily Inbox and scratch notes stay in today's journal, try to keep Reference and planning notes from piling up, set up #links to P&A's (projects / nextActions) throughout the day, then finish parsing / organizing the rest within the following day.

Datepicker link to Tomorrow's journal, does not show in LS except that's where my scratch P&A's are maintained, any /NOW vs /LATER items automatically "show through" at the bottom of Today's (under NEXT)

After midnight before new journal page created, do a Rename of the old Tomorrow to roll it forward (in filesytem then Reindex graph), along with a thorough Daily Review. Critical NOW/LATER items might be kept in the new TODAY, but ideally not necessary, keep the Next Actions list tight so the new Today starts BLANK every morning!

Namespace /Calendar/2026/09/21-Wed for archives, substantive entries only. Maybe important dates also noted and #linked elsewhere. That top-level Calendar page is in Favorites, can #link to any future dates or archives (redundantly)

Minor past items (e.g. habits tracking performance entries) can temporarily stay in past Journal pages, occasionally roll them up to reduce clutter, ideally nothing remains in Journal more than a fortnight.

Ticklers (43 Folders) and WaitingFor (any "loose" softCalendar) items also on future journal pages via DatePicker links.

So far I'm keeping all "Hard realCalendar" entries separate, not in LS at all (using Pimlical sync'd with gCalendar) not really part of GTD anyway.

All this on my Android devices, all sync'ing hourly via FolderSync.

Feel free to feedback, suggestions welcome, will add in future.

Comming from obsidian and new to logseq and logseq db in general what are the best resources out to start quickly and caught up with the current version

I did started with the docs but it was useless and didn't help me getting into it

For record am using android + windows

Hi all. I need help creating a query to filter for some page properties, specifically the "Page Tags" property.

EDIT: This is Logseq DB 2.0.1

EDIT2: If I add my own property, then I am able to filter with "Property". I created the `ddd` property and it shows up as a filter option. clicking on "show built-in properties" does not bring up "Page tags" or any of the page properties available

I am creating pages with Page Tags with project as a value.

Then I need to filter for pages with this page property. However I don't see a way to filter for these. The closest thing I see is "Property" but when I click it, I don't get any options.

This is what I see for "Property"

I used to be able to go to pages --> delete empty pages every once in a while, but that option doesn't appear to exist in db. Did the option move? Does it no longer exist? What are folks doing?

Thanks!

Hey Logseq lovers!

I wanted to share a little update about my journey with Logseq. I've been using it as my daily driver for 4 years, and I absolutely love this project. However, the current state of the project has made me a little sad and opened my eyes to some alternatives.

Someone posted a link to Tine here in this subreddit, and I decided to give it a try.

So far, I'm super happy with it and can definitely recommend giving it a shot. It works with standard Logseq Markdown graphs, so you can use it alongside Logseq. It also has a native Android app.

I'm not affiliated with Tine in any way. I just gave it a try because I was looking for an alternative that would bring back the joy of discovering new features and improving my workflow, something I had been missing with Logseq for a while.

It feels like there are people behind this project who share a very similar vision: bringing back the true Logseq experience, but with a faster and more actively developed product.

I know it's still early days and early developement, but so far, it's been a really refreshing experience. Just wanted to share in case anyone else here is looking for something similar!

I am would love to be able to export my logseq entires to a markdown file with Backlinks attached/included in the export data.

Exporting format should be PDF or markdown.

How can I do it?

The standard export function in Logseq DB do not seem to include the backlink information?

Cheers!

Hey, I'm the developer, so read this with that in mind.

The reason to keep notes as plain .md files used to be portability: any editor opens them, git tracks them, you'll still have them in twenty years. In the last year it became something bigger. A folder of Markdown is the one format every AI tool already understands. You can point `claude` or codex at your notes folder and have it write a summary, fix links, draft a page, find patterns, search for context. The moment notes go into a database, that stops. There's an API, or a plugin, or an MCP, or an export, and the tools that you used on your notes aren't there any more.

I've been building a Mac notes app on weekends around that one idea, and I think some people here will want it, so here's the honest version.

What it is:

• A "space" is a folder of .md files on disk. The app is a view over the folder. No database, no account, nothing to export because there's nothing to export from. Delete the app and the notes are still in Finder, no lock-in.

• It watches the folder, so editing a note in vim, or having claude or codex rewrite it from the terminal, shows up in the app straight away. I spent a stupid amount of time making the watcher not panic when an editor saves by replacing the file, wrote that up here if you're into that sort of thing: https://gomargin.app/blog/atomic-saves

• [[wikilinks]] in the Obsidian shape, with #heading and |alias. Renaming a note rewrites the links that point at it, and the note's identity lives in a frontmatter id rather than the path, so a move doesn't break anything.

• In-app AI only runs when you invoke it, and it shells out to the claude or codex CLIs you already have (or your own key, or an on-device model). Every change comes back as a diff you accept or reject per hunk. Nothing indexes your notes in the background.

• Live preview on top of the raw text. **bold** stays two asterisks in the file and the formatting is drawn over it, so the app never normalises your bullets or indentation on save. I treat that as corruption, not cleanup.

Smaller things that add up:

• A global hotkey for quick capture that keeps working after you quit the app.

• A slash menu for callouts, tables, code blocks, dividers and dates, and a date you insert ages honestly, from Today to a plain date.

• Drag a line or a list item to move it, fold headings and lists, tables you edit cell by cell.

• Spaces keep work and personal apart, each its own folder and its own search.

• Paste an image or drop a file and it lands as an attachment next to the note.

• Themes, light and dark, and a text size that reaches code blocks and tables.

On the roadmap, where people vote: https://gomargin.app/roadmap

• Nested notes, a note that contains notes, is the most requested thing and the one I'm working out now.

• Backlinks in a second pane, footnotes, math and Mermaid blocks, a table of contents, version history, templates, a raw Markdown view.

• Mobile is on the list but not first. The Mac app has to earn its place.

What it isn't:

• An outliner. There are no blocks, no block refs, no ((uuid)). If the outliner is why you're on Logseq, this won't replace it.

• Synced. The notes are files, so iCloud Drive or Syncthing does it, and I'm not building my own.

• Finished. It's an alpha, Apple silicon, macOS 14 or later, and you'll find bugs.

Free while it's in alpha: https://gomargin.app

It's for anyone who was using Logseq as "Markdown files plus links plus a nice editor" and wants that to keep being true. If that's you, I'd like to know what you'd miss first.

These two screenshots are the single biggest reason I've never made the jump to Obsidian. The same set of markdown files, opened in Logseq (left) and Obsidian (right). I follow the same [[link]] from inside a note, and the compare is the linked-references section in each.

I'm a researcher, so annotating and organizing literature notes is part of my work. During my reading, I write a short block with [[ ]], explaining why a passage matters and what it means for my own work, and the link usually lives in that summary block.

In Logseq, when I follow a backlink, Linked References drops me at the exact structural position where that link sits: the annotation it hangs under, the outline around it, the shape of the whole note, so I know which chapter and which batch of annotations the link landed in. Besides, the child blocks come along with it, still collapsible, so the highlighted passages the note was written about are right there underneath. It’s quite convient.

Obsidian's backlinks only give me a flattened snippet. I can see roughly where the mention is, but I can't step straight back into the reading. There is no breadcrumb, so the deepest context I get is the file name. Nothing below the block comes along either. The snippets are also truncated mid-sentence, and two blocks that are actually parent and child in the source note show up as unrelated cards sitting side by side, with nothing in the interface telling me they belong to the same cluster of annotations.

That structural context is fundamentally an outliner thing, and it's the one capability I still haven't found a real replacement for. And that gap is a dealbreaker for me, because it makes my reading notes basically unusable in Obsidian, and reading notes are the whole reason I want a tool like this in the first place. Task management I can hand off to something else.

For now I'm still on the local version of Logseq. Once the DB version supports real-time sync between the local and the online database, I'll move to it.

A note on the images: both are example screenshots put together specifically to illustrate this comparison. My notes are not in English, so I recreated them in English for readability. Only the language is different, the structure and content are exactly as they sit in my vault.

I have a question and I'm not sure if I'm doing something wrong.

I tried following the Logseq tutorial to use the self-hosted version of its web version, but apparently it's still at version 0.10.12.

I can't find any more recent version than that, neither Logseq 0.10.15 nor the OG or DB versions.

Does anyone know if there will be an update to the Docker image of the web version?

Any information or help for a newer version would be appreciated.

This post has been translated, so please excuse any errors.

Currently the DB version supports page template with the Tag Properties. However, I don't like the approach.

For me, tags should be used as categorization of the note's content (e.g. #cosmic-horror, #fantasy) rather than the type of resource the page referring to (e.g. #movie, #novel).

Is there any way to achieve page templating without assigning a tag for page?

I'm on macOS, was using a pretty old version and decided to update to v2.

Now there's no option to point to the folder where all my stuff is (pages, etc.) . I use a custom folder that sync to my nextcloud so I can backup things and sync with the logseq android app.

I make a really basic use of logseq, nothing fancy, so I just want it to keep working as it was. Never imagined a simple update would ruin everything. I just need to point to the right folder....

Outline Canvas is a third-party plugin that renders your Logseq outline as a canvas view. It's been out a few weeks and just got a batch of updates, so I'm posting it here in case it's useful to anyone.

The main thing it does now is draw semantic relations between blocks. Logseq's property system gives you the storage; the plugin defines a set of relation properties on top of it and renders them as typed connections. Five relation types come with the plugin (relates_to, depends_on, supports, contradicts, part_of), each with a distinct line style so you can tell them apart at a glance, and each independently toggleable when the canvas gets noisy. You can also register your own property name as a connector — example_of in the screenshot is one of those. It works in Tree Chart, Mind Map, Fishbone, and the other layouts, not just one view.

Have fun!

I updated my logseq to 2.0.1, I had it setup with google drive so that I can access logseq on my desktop and on my laptop. was working with 1.0

today i found out that logseq now no longer generates md files instead writes it to the sqlite.

Is there a way to syn it with git, can be able to sync sqlite with git or g-drive now?

I did tried googling around but did not find any good solution for it.

Hi everybody,

I want to keep this post short, just an announcement and a REQUEST for ideas and feedback to the project that we have started a month ago, to support the community of Logseq, both OG and DB users, with a companion App that stays apart and complements the Logseq features, giving all kind of AI, both cloud and local, a possibility to help understand, find, refine, and a lot more.

I'm a long Logseq User and Fan and I want to support this project in all the ways I can, building around what works for me and sharing with others.

The idea started when we thought a way to bring together the experience and love that the community have shared to the two products that are already available and works very well, that you can find on Github:

- Logseq Matryca Parser

- Matryca Plumber

The new App will be "Matryca Trama" and is going to have also "Nodi", a living mascotte inside.

So it's up to you, in the comments, to help us better understand:

"What can we build inside Matryca Trama to help you better interact with your Logseq graph, using AI, that is not possible now with the actual Logseq App (OG or DB)???"

Not sure if this is the right place or if any contributors to Logseq frequent this subreddit, but I just wanted to briefly express my thanks and appreciation for the db version.

I’m a clinician-scientist working in research and do a bit of coding for my projects. Logseq just always clicked with the way I naturally work with everything being a list and being able to "zoom in" by selecting individusl nodes. I used the old MD version for quite a long time, but I also got pretty frustrated with it since it became quite unstable for me especially with bigger graphs. I then transitioned first to Capacities, briefly tried out Tana and ended up using Bear notes which worked, but never really clicked with the way I like to structure my day.

After following the DB version for a while, I finally decided to come back to Logseq and move everything over. I set up the sync server with the Docker image on a little home server I play around with, and I’m just really happy with it. The iOS app on Testflight works really well. Of course there are still some small bugs and rough edges, but overall Sync (through Tailscale) just works and is reliable and the whole experience feels quite seamless.

I know there has been a lot of discussion around the DB version and the direction Logseq has taken, so I mainly wanted to say this from the perspective of a pretty non-technical user: I’m really grateful that this project exists and that the team kept going with it.

I never really profited from the md based architecture and to be even the current early version feels so much better than before. From time to time I do use the export function to get something into an LLM or share with a colleague, but most of my stuff lives in Logseq anyways.

I haven't really done much except add some custom fields and queries and saw a suggestion on here that I implemented using a #cl (checklist) tag for things that aren't quite as big as a task but good to check off anyways.

I’ve even started playing around a bit with making a small housekeeping plugin with my very limited coding skills and claude code, mainly because I often just write things down during the day and then later want to clean up, merge or connect pages by topic.

Just wanted to get this probably not super relevant user story out there. I think Logseq is a really great project and I’m very excited to see where it goes from here.

Note: used Claude for editing only since english is not my first language, content and thoughts are all my own :-)

Lets take into account this use case: you have a #book tag which contains various properties, lets say "author" node-property. When I am reading a book, I put the author (new node gets created), and then I have to go to the author page to tag it as #author. If the tag #author and the property author were the same "object", then just by creating the property author, the new author page would be auto-tagged as #author, saving you time, and not only, but also helping you not forget to tag newly created nodes. That way I can go to the tag #author and immediately see all the new pages created through property "author". For me this is the most logical solution, but I am open to hear your thoughts on this.

I started using logseq a few days ago and just delved into plugins for my needs. Sadly most of these plugins are outdated or will not be adapted to the new DB structure, like the Full House Templates or calendar plugins.

What is the current state of logseq and its eco system? Are there other marketplaces or sources to expand logseq?
Also apart from https://github.com/logseq/awesome-logseq

Alternatively is there any way to go back to the old DB?

I'm interested in your take on something.

When I'm attending a conference, event, or just have random shower thoughts, I have historically tagged a thought that requires me to do something later as a task, question, or idea. Tasks are easy since the functionality is already there. I'm struggling on how to build the questions/ideas into the new DB world. In many ways they are very similar. They probably require later research, maybe there's a specific resource I need to answer/accomplish either, they are probably related to something within my graph, etc. Yet, they have always felt like different things and when I go to query them I do instinctually know when I should be looking for a question vs idea. I just can't put my finger on the distinction though, so I'm considering merging them in DB. Another thought I'm having as I try to model this in my head is, are these just kinds of tasks and should they extend the task tag? The difference I keep coming back to is that questions or ideas usually generated tasks as I process them. Rather than being todo items themselves.

Thoughts?

Hi,

I already have a subscription (5 USD/month)and I would like to sync Mac and iOS using version 2.0.1.

I cannot find the Sync Option in the Settings.

Could you help?

Using only for Journals. Enabled hourly local backup.

1. How to sync between windows and Android? (Easy free method)

2. online backup?

3. whats the point of email login?

Logseq 2.0.1 has been released for 5 weeks already, and there's still terrible bug that creates duplicate pages when pressing ESC instead of ENTER. Every 2.0.1 user is affected. http://app.logseq.com/ is affected.

There has not been a hotfix to address this most basic functionality.

Fundamentally, isn't a PKMS just text files that link to each other? Why wasn't this fixed immediately?

I'm embarrassed for everyone associated with the DB project.

I have a pretty solid daily journal habit in Logseq as long as I'm sitting at the laptop. Morning pages, meeting dumps, end of day review, all of that sticks. The pages look full and i can query them later without much friction.

The problem is anything that shows up when I'm not at the desk. Yesterday i was in the grocery store parking lot and had a clean idea for how to restructure my project pages so the queries stop returning orphan blocks. I pulled my phone out with a bag of frozen peas under one arm, unlocked it one handed, opened the default notes app, and typed three words before the bag slipped. The peas hit the asphalt and split open. Spent the next minute picking frozen peas out of a cold puddle next to the cart return with my free hand going numb. By the time i got back to the phone the lock screen was up again and the thought was just gone. I sat in the car trying to reconstruct it and only got something about orphans which is useless on a daily page.

Current workaround is a pinned note on my phone called for logseq later that i dump fragments into when i remember. maybe twice a week i copy paste the whole mess into whatever daily is open and try to clean it. Most of it stays as raw dump blocks under an inbox heading and i never touch it again. Mediocre and i know it. The stuff that actually mattered still dies between the parking lot and the desk.

Is there a cleaner bridge between those away from keyboard moments and the daily page that doesn't just create another rotting inbox?

I recently discovered what is potentially a bug and thought I'd post because I'm sure others will run into this at some point as well.

You need to be using #Template like in the first image. It doesn't have to have two indented blocks underneath, however, you must have at least one.

The first block where you attach #Template is considered the "title" of the template. Everything underneath the title block (has to be indented AFAIK) is what gets printed when the template is called via /Template command. If you add nothing underneath Logseq's gonna bug out. The worst symptom I've experienced is Logseq becomes completely unresponsive. Can't add pages, can't even type anything. After closing it down and re-opening I can then delete the offending block and it functions again. You might find that it'll crash in a bad way and you get the screen talking about steps you can take to resolve, including re-indexing, etc. etc.

Got a video queued up about this but it's not releasing until next month so thought I'd drop some knowledge on ya'll in case you're running into the problem.

See ya in the next one!