dsh-logseq

[!NOTE]

📦 This plugin lives in the dsh-plugins monorepo — file issues & pull requests there.

npm: @hy-sde-org/dsh-logseq-graph · @hy-sde-org/dsh-tool-logseq

dsh-logseq — headless LLM-wiki (Logseq CLI graph service + tools) for DeepSeek Harness

Two standalone packages, installable as one plugin family for the DeepSeek Harness CLI:

package · role · installed by users? @hy-sde-org/dsh-logseq-graph · the service: host-plane ctx.wikiGraph backed by the installed logseq CLI · yes @hy-sde-org/dsh-tool-logseq · the model-facing logseq_* tools (list/show/search/query/upsert/remove/graph/server) + logseq:tools prompt section · yes

This is the DeepSeek Harness packages/logseq family — the logseq-graph host service and the logseq CLI tools — ported to the hy-sde npm scope as a standalone plugin family with zero upstream harness changes: every @deepseek-ai dependency resolves from the npm registry at the 0.2.0-rc.2 baseline, so it installs on official DeepSeek Harness releases (dsh-v0.2.0-rc.2 and later) exactly as it runs in the fork. The service row ships as a normal package (no cordis.patch.yml inside — see Mounting), and the tool row ships as an agent-plane plugin.

Why

Agent wiki work is terminal-first: it reads and writes the graph from tool calls, not from a GUI. The upstream harness reaches this graph through the web GUI's wiki drawer and a browser drawer package — neither ships here, and neither is needed. This standalone publishes the headless surface only: the ctx.wikiGraph service backed by the installed logseq CLI, plus the model-facing logseq_* tools with deterministic JSON output. No desktop app hop, no scraped screenshots — page/block trees, tags, properties, and Datalog queries come back as plain-JSON wire types the model can act on directly.

Prerequisites

• Node.js 22.19 or newer with npm and pnpm on PATH;
• DeepSeek Harness 0.2.0-rc.2 or newer including the standard dsh CLI —

the packages' @deepseek-ai/* peer range is ^0.2.0-rc.2 (@deepseek-ai/cordis pins ~4.0.4);

• the Logseq CLI — the ctx.wikiGraph

service is backed by the installed logseq CLI, so the graph must be reachable from the terminal.

Install the Harness CLI and pnpm before continuing:

npm install --global @deepseek-ai/dsh@0.2.0-rc.2 pnpm
dsh --version

Summary

The logseq/ family gives agents a headless LLM-wiki backed by the Logseq CLI:

• logseq-graph/ — host graph

service (ctx.wikiGraph): page/block trees, tags, properties, Datalog queries, upserts/removals, and the logseq_server lifecycle, projected to plain-JSON wire types.

• tool-logseq/ — model-facing

logseq_* tools: list/show/search/query/upsert/remove/graph/server with deterministic JSON output, plus a logseq:tools prompt card.

In the upstream harness, the web GUI's wiki drawer reads/writes the graph through this service via the host API proxy's wiki domain, and the browser drawer (dsh-client-ui-wiki) is a separate package — neither ships here. This standalone publishes the service + tool surface only.

Table of Contents

• Install
• Mounting
• License

Install

Direct from npm (published)

dsh plugin --profile web add @hy-sde-org/dsh-logseq-graph @hy-sde-org/dsh-tool-logseq

From this repository (pre-publish)

pnpm install            # workspace setup
pnpm -r build
pnpm --filter packages/logseq/logseq-graph pack
pnpm --filter packages/logseq/tool-logseq pack
dsh plugin --profile web add <tarball-or-catalog-url>.tgz

prepack rebuilds dist/, so the tarball is always current. Then bring the service row plus the tool row together in your composition as described under Mounting.

Mounting

Unlike dsh-browser, this family ships no `cordis.patch.yml` and no ready-made agent preset: the port scope is the .ts surface only, and the upstream harness wires these rows in its own web-app bundle patch. Add the two rows to your composition by hand:

• Service row (host plane) — ctx.wikiGraph is consumed by the host API

proxy / wiki drawer rows in the upstream harness, so it belongs in the host composition, not behind a preset realm:

- id: logseq-graph
    name: '@hy-sde-org/dsh-logseq-graph'
    config:
      graph: llm-wiki

• Tool row (agent plane) — the tools resolve tools + systemPrompt

from the agent bundle; add it to the agent preset:

- id: tool-logseq
    name: '@hy-sde-org/dsh-tool-logseq'
    config: {}

@hy-sde-org/dsh-tool-logseq declares @hy-sde-org/dsh-logseq-graph as a peer (and a workspace:* sibling dep in this repo) so the family ships and resolves together.

Verify

Nothing is inserted for you — after adding the two rows by hand (above) and mounting the preset, check the composed tree:

dsh web --dump-config

It must show the hand-added logseq-graph row loading @hy-sde-org/dsh-logseq-graph; the tool-logseq row comes from your agent preset, where the logseq:tools prompt section and the logseq_* tools appear in the session.

Uninstall

Remove the hand-added logseq-graph row from your composition and the tool-logseq row from your agent preset, then remove the packages:

dsh plugin --profile web remove @hy-sde-org/dsh-logseq-graph @hy-sde-org/dsh-tool-logseq

License

MIT — see LICENSE. Derived from the DeepSeek Harness logseq packages (@deepseek-ai/dsh-logseq-graph, @deepseek-ai/dsh-tool-logseq, MIT) — see THIRD-PARTY-NOTICES.md.