Skip to main content

A Unix-composable CLI for the Logseq local HTTP API

Project description

██╗      ██████╗  ██████╗ ███████╗███████╗ ██████╗       ██████╗██╗     ██╗
██║     ██╔═══██╗██╔════╝ ██╔════╝██╔════╝██╔═══██╗     ██╔════╝██║     ██║
██║     ██║   ██║██║  ███╗███████╗█████╗  ██║   ██║     ██║     ██║     ██║
██║     ██║   ██║██║   ██║╚════██║██╔══╝  ██║▄▄ ██║     ██║     ██║     ██║
███████╗╚██████╔╝╚██████╔╝███████║███████╗╚██████╔╝     ╚██████╗███████╗██║
╚══════╝ ╚═════╝  ╚═════╝ ╚══════╝╚══════╝ ╚══▀▀═╝      -╚═════╝╚══════╝╚═╝
  

Logseq CLI

Python 3.10+ License: MIT Platform Last Commit

Your Logseq graph, from the command line.

Pipe pages. Filter blocks. Query the graph. Work with Logseq the Unix way.

A Unix-composable CLI for the Logseq local HTTP API — built for humans and AI agents alike. NDJSON output, clean stderr, and auto-stdin composition let you wire Logseq into any shell pipeline or agentic workflow without glue code.

PowerShell screenshot showing the logseq CLI help output


Why This CLI

Most Logseq automation requires either the plugin API (which lives inside Logseq) or direct file manipulation (which bypasses the graph index). This CLI takes a third path: the official local HTTP API, exposed as composable shell commands.

Designed for humans and AI agents. Every command emits structured NDJSON that is trivially parseable by jq, shell scripts, or an LLM driving an agentic workflow. Errors are always on stderr so stdout stays clean for piping.

Property What You Get
NDJSON by default Pipe directly into jq, fzf, or the next command — no parsing glue
Auto-stdin Commands read identifiers from upstream NDJSON when no argument is given
--fields filtering Trim output to specific keys — token-efficient for LLM agents
--plain mode Human-readable key: value pairs for interactive use
Errors on stderr stdout is always clean — safe to pipe at every step
Consistent structure Every command follows noun verb — no surprises

Requirements

  • Python 3.10+
  • Logseq Desktop with the HTTP API server enabled
  • Windows, macOS, or Linux

Installation

logseq-cli is published on PyPI. Install it globally with pipx if you want the logseq command available in every shell without manually activating a virtual environment.

Important: the CLI will not work until an API token is configured. Every installation method below must be followed by the required token setup step in Set the API token.

Global install from PyPI with pipx

Windows (PowerShell)

py -m pip install --user pipx
py -m pipx ensurepath
pipx install logseq-cli

macOS / Linux

python3 -m pip install --user pipx
python3 -m pipx ensurepath
pipx install logseq-cli

Then run the required token setup step in Set the API token and verify:

logseq --help

Global install from PyPI with pip

Windows (PowerShell)

py -m pip install --user logseq-cli

The script usually lands in your user Python Scripts directory, such as %APPDATA%\Python\Python310\Scripts. Add that directory to PATH if logseq is not found after install.

macOS

python3 -m pip install --user logseq-cli

If logseq is not found after install, make sure the user base binary directory is on your PATH:

python3 -m site --user-base

On many systems that means adding a path such as ~/Library/Python/3.11/bin to your shell profile.

Linux

python3 -m pip install --user logseq-cli

If logseq is not found after install, add ~/.local/bin to your PATH.

Install from a local checkout

The examples below install from this repository checkout instead of PyPI.

Recommended: pipx (globally available, no manual activation)

Windows (PowerShell)

py -m pip install --user pipx
py -m pipx ensurepath
pipx install .

macOS / Linux

python3 -m pip install --user pipx
python3 -m pipx ensurepath
pipx install .

Then run the required token setup step in Set the API token and verify:

logseq --help

Virtual environment (for development or isolation)

Windows (PowerShell)

py -3.10 -m venv .venv
.\.venv\Scripts\Activate.ps1
pip install -e ".[dev]"

macOS / Linux

python3 -m venv .venv
source .venv/bin/activate
pip install -e ".[dev]"

Then run the required token setup step in Set the API token before using logseq.

User install (no virtual environment)

Windows (PowerShell)

py -m pip install --user .

The script lands in your user Python Scripts directory, such as %APPDATA%\Python\Python310\Scripts — add that to PATH if logseq is not found after install.

macOS / Linux

python3 -m pip install --user .

If logseq is not found after install, add ~/.local/bin to your PATH.

Then run the required token setup step in Set the API token before running logseq.

Install the agent skill

If you want AI agents to install the bundled logseq-cli skill into their local skill directories, use:

logseq skill install

That writes SKILL.md into the supported user-level targets:

  • ~/.agents/skills/logseq-cli/SKILL.md
  • ~/.claude/skills/logseq-cli/SKILL.md

You can also install into the current project instead:

logseq skill install --scope project

Related commands:

  • logseq skill status
  • logseq skill show
  • logseq skill uninstall

Uninstall

Use the uninstall flow that matches how you originally installed logseq-cli.

Uninstall a global pipx install from PyPI

Windows (PowerShell)

pipx uninstall logseq-cli

macOS / Linux

pipx uninstall logseq-cli

Uninstall a global pip install from PyPI

Windows (PowerShell)

py -m pip uninstall logseq-cli

macOS

python3 -m pip uninstall logseq-cli

Linux

python3 -m pip uninstall logseq-cli

If you installed with --user, this removes the package and its logseq entry point from your user Python location.

Uninstall a local checkout installed with pipx

If you ran pipx install . from this repository, remove that environment by package name:

Windows (PowerShell)

pipx uninstall logseq-cli

macOS / Linux

pipx uninstall logseq-cli

Uninstall a virtual environment install

If you created a project-local virtual environment, deactivate it if it is active and then remove the virtual environment directory.

Windows (PowerShell)

deactivate
Remove-Item -Recurse -Force .\.venv

macOS / Linux

deactivate
rm -rf .venv

If the environment is not active, skip deactivate and just remove .venv.

Uninstall a user install from a local checkout

Windows (PowerShell)

py -m pip uninstall logseq-cli

macOS

python3 -m pip uninstall logseq-cli

Linux

python3 -m pip uninstall logseq-cli

Uninstall the agent skill

If you also installed the optional agent skill, remove it separately:

logseq skill uninstall

That removes the installed SKILL.md from the supported skill target directories.


Configuration

1. Enable the Logseq HTTP API

  1. Open Logseq Desktop and load your graph.
  2. Go to Settings → Features.
  3. Enable HTTP APIs server.
  4. Copy the API token shown in that panel.

The server listens at http://127.0.0.1:12315/api by default.

2. Set the API token

This step is required for every installation method. logseq-cli will not work until a token is stored or provided via LOGSEQ_TOKEN.

Recommended: store the token in the CLI's user config so it works across future shells and agent runs without shell-specific setup.

logseq auth set-token

The command prompts securely for the token and stores it in a user-level config file. After that, verify:

logseq auth status
logseq graph info

Run logseq auth set-token again at any time to replace the stored token with a new one.

Environment variable override

If you prefer, the CLI still supports LOGSEQ_TOKEN and will use it instead of the stored token for the current process.


Quick Start

Make sure Logseq is running with the HTTP API enabled, then:

# Verify the connection
logseq graph info

# List all pages
logseq page list

# Get a specific page
logseq page get "My Page"

# Append a block to a page
logseq block append "My Page" "- New thought"

Command Reference

auth

Command Arguments What It Does
auth set-token [token] Store or replace the token in the CLI config; prompts securely if token is omitted
auth status Show the config path and whether a token is stored

page

Command Arguments What It Does
page list --fields, --plain, --page, --page-size List all pages; auto-paginated
page get [name] --fields, --plain Get a page by name; auto-stdin reads .name
page create <name> --fields, --plain Create a new page
page delete [name] Delete a page; auto-stdin reads .name
page rename <src> <dest> Rename a page
page refs <name> --fields, --plain Linked references to this page
page properties <name> --plain Derived from the first block in the page tree
page journal <date> --plain Create/get a journal page (YYYY-MM-DD)
page ns-list <namespace> --fields, --plain Pages under a namespace
page ns-tree <namespace> --plain Namespace as a nested tree

block

Command Arguments What It Does
block get [uuid] --fields, --include-children, --plain Get a block; auto-stdin reads .uuid
block insert <content> --uuid, --sibling, --plain Insert as child by default; auto-stdin reads .uuid
block update <uuid> <content> --plain Replace a block's content
block remove [uuid] Delete a block; auto-stdin reads .uuid
block prepend <page> <content> --plain Insert at the top of a page
block append <page> <content> --plain Insert at the bottom of a page
block move <src_uuid> <target_uuid> --sibling, --plain Move as child by default
block collapse <uuid> --expand, --toggle Collapse, expand, or toggle
block properties <uuid> --plain Get all block properties
block prop-set <uuid> <key> <value> Upsert a block property
block prop-remove <uuid> <key> Remove a block property
block insert-batch <uuid> <json> --sibling, --plain JSON array with content and optional children

graph

Command What It Does
graph info Returns the current graph name and path

query

Command Arguments What It Does
query run <datalog> --plain, --page, --page-size, --input Run a Datalog query; --input is repeatable for parameterized queries

Piping & Composition

Commands that accept a positional name or uuid argument will read it from upstream NDJSON when the argument is omitted:

# List non-journal pages, then fetch each full page object
logseq page list |
  jq -c "select(.isJournal == false)" |
  logseq page get

# Fetch a block and remove it by piping its UUID forward
logseq block get abc-123 | logseq block remove

# Trim output to specific fields for downstream processing
logseq page list --fields name,uuid

# Run a Datalog query and pipe results into jq
logseq query run "[:find ?name :where [?p :block/name ?name]]" | jq .

Auto-stdin commands:

Command Field read
page get .name
page delete .name
block get .uuid
block insert .uuid (when --uuid omitted)
block remove .uuid

Output Format

Mode What You Get
Default (NDJSON) One JSON object per line — pipe-safe, jq-compatible
--plain key: value pairs — human-readable for interactive use
--fields name,uuid Output filtered to the specified keys only

Errors always go to stderr. stdout is reserved for data only.

logseq page list --fields name,uuid
{"name": "My Page", "uuid": "abc-123"}
{"name": "Another Page", "uuid": "def-456"}

API Compatibility Notes

Some Logseq HTTP API methods are absent or non-functional in current builds. This project documents all confirmed-unsupported methods in UNSUPPORTED-LOGSEQ-HTTP-METHODS.md, including reproduction steps and the exact server error returned.

Active fallbacks:

Command Fallback Strategy
block append Reads the page tree and inserts after the last block
page properties Reads the first block in the page tree
page journal Creates a YYYY_MM_DD page, then resolves the journal entry

Development

# Install with dev dependencies
pip install -e ".[dev]"

# Run all tests
pytest --tb=short

# Run a specific test module
pytest tests/test_page.py --tb=short

Project Layout

src/
  logseq_client.py      # HTTP client — thin wrapper around httpx.AsyncClient
  logseq_service.py     # Service layer — async methods over logseq_client
  cli/
    main.py             # Typer app entry point, get_service(), handle_errors()
    output.py           # format_output(data, fields, plain)
    stdin.py            # read_stdin_field(field) — reads NDJSON lines from stdin
    page.py             # page subcommand group
    block.py            # block subcommand group
    graph.py            # graph subcommand group
    query.py            # query subcommand group
tests/
  conftest.py
  test_page.py
  test_block.py
  test_graph.py
  test_query.py
  test_output.py
  test_stdin.py
  test_errors.py
  test_entrypoint.py

License

MIT

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

logseq_cli-0.2.4.tar.gz (29.3 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

logseq_cli-0.2.4-py3-none-any.whl (23.0 kB view details)

Uploaded Python 3

File details

Details for the file logseq_cli-0.2.4.tar.gz.

File metadata

  • Download URL: logseq_cli-0.2.4.tar.gz
  • Upload date:
  • Size: 29.3 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.12.3

File hashes

Hashes for logseq_cli-0.2.4.tar.gz
Algorithm Hash digest
SHA256 777cd240662c686666b87c490dbdcbbfeb467ad1927eb637089756efa1801130
MD5 a33732042b8b32589de57b87d5c3b401
BLAKE2b-256 9205b7121f372b4a4d0c7acd09f6c811a5611f73c1ce441fa419eaa2a18bc6e7

See more details on using hashes here.

File details

Details for the file logseq_cli-0.2.4-py3-none-any.whl.

File metadata

  • Download URL: logseq_cli-0.2.4-py3-none-any.whl
  • Upload date:
  • Size: 23.0 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.12.3

File hashes

Hashes for logseq_cli-0.2.4-py3-none-any.whl
Algorithm Hash digest
SHA256 a93561b527009b510c97f8106ef105c977fdfaedac60f99f69d6b17b849be1c9
MD5 92d17ee8125ce8b19b3f7c5733f52ac7
BLAKE2b-256 c0feac3cfe161e0e2c652e880085e1980b67add76aa8f780a45b9c00b7869e8d

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page