[DONE] Deep Linking or URL Scheme / Allow linking to Logseq pages from outside the app

Any news about that ?

Actually this feature would be very usefull. I could e.g. link from Zotero and from Anki back to the corresponding logseq page. Any news on the state of this feature?

1 Like

Related to this android has the Storage Access Framework which makes it possible for users to grant finegrained access of files or directories in an apps sandboxed private storage to other apps. Details are in This topic


With the release of 0.6.6., this feature is now implemented.

1 Like

If you use the Flatpak version on Linux and you can’t make Logseq handle logseq:// URIs, be sure that in your com.logseq.Logseq.desktop (it should be in ~/.local/share/applications/) the Exec and MimeType lines are like the following:

Exec=/usr/bin/flatpak run --branch=stable --arch=x86_64 --command=run.sh --file-forwarding com.logseq.Logseq @@u %u @@

You may need to run:

sudo update-desktop-database

Now clicking logseq:// URIs from some other app should open Logseq at the right page. From the terminal the command is:

xdg-open “logseq://…”

Tested on Logseq 0.7.0.


Is there to map a shortcut to “Copy page URL”? Also could it be included in the command palette?

There is no “Copy page URL” shortcut currently. But it’s a great suggestion.

For visibility, could you please create a new feature request?

1 Like

Thanks! (and voted!)

The kind of Deep Linking that Hook enables in macOS would also allow external links to blocks in Logseq. Is this available now? If so, I can’t figure out how to do it.

Also, I would add my vote for direct Hook support.

There is a “Copy URL” button in the context menu of Page & Block

Found them. Thanks!

Possibly linked to a feature request [1], which may be looking at this at a big of a higher level, essentially, we need almost like a normative mapping between Logseq artifacts and those of (1) file system and (2) URLs (Web) and in fact this can become the basis for a lot more productivity for power users.

I’d say that the power of Emacs and Vi (in having so many dedicated knowledge artist users) was their integration with the command line. But they were limited, in fact by Web, and that’s a gap that Logseq can fill. I did also document the higher level idea and some literature around it here in this tweet [2] and some other threads here on logseq community [3].

[1] Hidden APIs: How Logseq's relationship with files and URLs matter a lot from the get-go
[2] https://twitter.com/sindoc/status/1592169398609248258
[3] Specification for public graph discovery. Decentralized social network on logseq - #30 by sindoc