Helper App for API background use | Logseq | Page 1

mint cobalt Nov 9, 2025, 6:47 AM

#

Currently Logseq has to be running and the API turned on for API queries to work. It would be nice if there was an API helper app that ran in the background, allowing other apps to interact with your graph even when logseq wasn't running.

proud coral Nov 9, 2025, 7:14 AM

#

Logseq cli is it

mint cobalt Nov 9, 2025, 7:22 AM

#

proud coral Logseq cli is it

Doesn't the CLI also require the app to be running?

But even if it doesn't, sandboxing on MacOS means that API would be preferable. For instance, a browser plugin like Logseq copilot can't use the CLI.

proud coral Nov 9, 2025, 7:26 AM

#

Logseq cli does not require the app to be running.

mint cobalt Nov 9, 2025, 7:32 AM

#

Maybe the helper app could just be a web API for the CLI?

proud coral Nov 9, 2025, 7:34 AM

#

the chrome extension is sandboxed as you said. But there is a way for a chrome extension to perform local commands execution by using the native message host which talks to a native app. It could be a small python/go/node app …

mint cobalt Nov 9, 2025, 11:54 AM

#

Here is a simple (vibe-coded) proof of concept:

https://github.com/kerim/logseq-cli-server

GitHub

GitHub - kerim/logseq-cli-server: HTTP server wrapper for Logseq CL...

HTTP server wrapper for Logseq CLI - enables browser extensions to query Logseq graphs via REST API - kerim/logseq-cli-server

mint cobalt Nov 14, 2025, 3:33 AM

#

I've updated this with a new version that can run in the background on MacOS:

https://github.com/kerim/logseq-http-server

GitHub

GitHub - kerim/logseq-http-server

Contribute to kerim/logseq-http-server development by creating an account on GitHub.

#

It would be nice if the CLI could simply launch its own server, the way it launches MCP, logseq http-server. (Thanks to @proud coral for the suggestion.)

#Helper App for API background use