All products

Search Logseq notes and edit blocks with AI

Find the block behind a note or reference in a file-based Logseq graph and preview a change before it affects the live graph.

Search Logseq notes and edit blocks with AI when a reference is easier to remember than a filename. The logseq-cli skill asks a running file-based graph for page identity, aliases and backlinks. A plain file search would not necessarily tell you which underlying page a name refers to.

For a studio archive, a journal entry may be linked from several project pages. Identify its block before moving or changing anything. A dry run can show the proposed operation, while read-only mode refuses writes entirely. If the app reports that the block is open in the editor, inspect the current state instead of assuming a retry is safe.

What it does

  • Find a block using a phrase from its content.
  • Follow aliases and references to the actual page.
  • Read journal entries within a specified date range.
  • Preview a proposed change to a known block.
  • Check why an edit was refused before retrying it.

Install and use

  1. Open a file-based Logseq graph, enable its local API and configure the maker’s CLI with an authorised token.
  2. Start with a read-only lookup and identify the exact page or block.
  3. Preview the write, apply it only where intended and check the reported outcome.

FAQ

Source

Made by Patrick Müller (muellerei). Original skill: logseq-cli, published on GitHub under the MIT licence.

View on GitHub