Registers the local flowix-cli MCP server so the agent can search, read, create, and edit Flowix memos and mind-map artifacts.
Install
# from GitHub (first run asks for allowBuilds approval — follow the hint, retry)
dsh plugin --profile web add github:text2future/flowix#path:/dsh-flowix-memory
Any plugin you install runs third-party code with your own permissions — it can read your files, use your credentials, and reach the network, and tool approvals don’t sandbox it. GitHub-sourced plugins also run build scripts at install time — pnpm blocks those until you allow them, so an install can stop with ERR_PNPM_GIT_DEP_PREPARE_NOT_ALLOWED or ERR_PNPM_IGNORED_BUILDS; dsh prints the exact key to add under allowBuilds in your profile’s pnpm-workspace.yaml, and the install works on the next run. Allowing a build is a trust decision: only install sources you trust, and pin a commit (github:owner/repo#sha).
README
A DeepSeek Harness bundle
that registers the local flowix-cli MCP server with any Harness
instance. Once installed, the agent gets the
mcp__flowix__memo tool to search, read, create, and edit
Flowix Markdown memos, and to create declared plugin artifacts such as mind
maps.
The bundle includes a small launcher. It transparently proxies to flowix-cli
when installed; otherwise it keeps the tool registered and returns an
actionable installation error to the agent. The launcher is a cordis.patch.yml
that inserts one
@deepseek-ai/dsh-mcp-client
row, which ships inside every Harness distribution. Nothing here connects to a
remote Flowix service — the CLI is spawned locally over stdio and reads the
local notebook data directory.
Prerequisites
- A
flowixcommand onPATH(or setFLOWIX_CLI_PATHto the absoluteflowix-clibinary path) is needed to use the memo operations. If it is missing, the tool explains how to install Flowix fromhttps://flowix-memo.com/latest.json. The CLI is built from the flowix-main repository (app/flowix-cli, binaryflowix-cli). - Access to the Flowix notebook data the CLI should manage. Defaults to the
user config directory (
~/.flowix); override withFLOWIX_HOME/FLOWIX_DATAwhen the data lives elsewhere.
Install
dsh plugin manages one profile at a time and requires --profile <name>.
Flowix uses the flowix profile. In other DSH clients, flowix is simply a
custom profile name and can be created by the same command. The bundle remains independent from
Flowix's host/control bridge and ships in the
flowix-main repository and is not yet
published to npm, so install it from the checkout:
# from the flowix-main checkout root
dsh plugin --profile flowix add ./dsh-flowix-memory
Once published, the npm package installs the same way:
dsh plugin --profile flowix add dsh-flowix-memory
The row activates for that profile. Other DSH clients can start it with
dsh --profile flowix; this profile also ships dsh-appserver so the
Flowix App Server JSON-RPC surface is available out of the box.
Verify
Start Harness with the profile you installed into (dsh --profile flowix),
then check that the tool is registered:
mcp__flowix__memo
Prefer structured arguments:
{"action":"search","query":"product plan","notebook":"work","tag":"project/flowix","limit":20}
The legacy { "command": "search ...", "stdin": "..." } form remains
accepted for compatibility but is no longer the recommended contract.
Configuration
| Key | Default | Meaning |
|---|---|---|
FLOWIX_CLI_PATH |
flowix (PATH lookup) |
Absolute path to the flowix-cli executable |
If the CLI is unavailable, calling the tool returns an installation message
with https://flowix-memo.com/latest.json. Install Flowix, then restart the
profile so the launcher reconnects to flowix-cli mcp.
Uninstall
dsh plugin --profile flowix remove dsh-flowix-memory
Notes
- The MCP stdio bridge strips ambient credential-like variables and all
DSH_*variables before spawning the child; other ambient variables (includingHOME/PATH) are inherited. - Flowix Desktop installs this same bundle into its
flowixprofile and setsFLOWIX_DSH_MCP_CLI. Other DSH clients can install it into any profile and useFLOWIX_CLI_PATHor theflowixexecutable on PATH. There is one canonical bundle patch and no embedded duplicate row.
Links
More in this category
vectorize-io/hindsight#coding-agents★ 48490
Hindsight, agent memory that learns: long-term project memory with auto recall and retain, knowledge pages, deep reflection, and per-repo memory banks.
volcengine/OpenViking#examples/dsh-memory-plugin★ 39688
OpenViking memory and context bundle for DeepSeek Harness: pre-step auto-recall and profile injection, session capture, `viking://` URI guarding, and recall/write memory tools backed by an OpenViking server.
agentscope-ai/ReMe#dsh★ 3578
Connects DeepSeek Harness to ReMe's local-first, self-evolving personal knowledge base: automatically captures completed main-agent conversations as user-owned Markdown memory, searches conversations and source material through reme_search with BM25, optional embeddings, and wikilink expansion, and schedules daily memory consolidation.
zilliztech/memsearch#MemSearch★ 2736
Shared Markdown memory for DSH and other coding agents, with automatic capture, pre-step context injection, searchable recall, and memory-to-skill self-evolution through a review panel.
vshulcz/deja-vu#extensions/dsh★ 1176
Reads the session files thirty-three other coding agents on this machine already wrote — Claude Code, Codex, Cursor, VS Code Copilot Chat, opencode, OpenClaw, Hermes, Kimi, Cline, Zed and more — including sessions from before it was installed: six tools (deja_recall, deja_session, deja_blame, deja_fix, deja_how, deja_remember), a /deja command, and optional automatic recall added to the runtime context. Local BM25 index, no LLM, no embeddings, no network (dsh plugin --profile web add dsh-deja).
adoresever/graph-memory★ 644
Traceable, searchable cross-session memory for DeepSeek Harness — conversation knowledge as typed graph nodes (TASK/SKILL/EVENT) and typed edges.
Community comments
Comments are public GitHub Discussions. Loading them connects to GitHub and Giscus; a GitHub account is required to post.