dsh-flowtext

If you prefer issuing instructions through DeepSeek Harness while relying on FlowText inside Obsidian for classification, planning, data reads and writes, and tool invocation, wiring the two together used to mean copying tokens by hand, editing Profile files, and configuring ports vault by vault. dsh-flowtext automates every step of that handshake.

Once installed, DSH registers a single flowtext-direct route. Every request is forced through FlowText, which exclusively owns classification, planning, discovery, reads, writes, tool calls, clarification, approval, and finalization. The plugin auto-discovers every open vault (default 127.0.0.1:27124; additional vaults grab free ports automatically). The first task on a vault triggers a one-time local authorization in Obsidian; the credential is then stored per vault and reused, with no token copy or manual Profile edit required. In the default summary mode, safe-phase, plan, and tool summaries stream in as reasoning content; switch progressMode to off to get only the final answer.

The Gateway accepts loopback endpoints only, and discovery records carry identity, display name, path, and port—never tokens. Clarification prompts and dangerous-operation approvals are handled through DSH's native Session-scoped interaction services, so they spawn no extra model turn and their answers never reach the DSH model. DSH system prompts, tool catalogs, assistant history, and plugin context are not forwarded to FlowText. Model retries are disabled to prevent duplicate write tasks, and human interaction time does not consume the FlowText execution timeout.

Built for power users running FlowText Agent Gateway in Obsidian who want to drive a complete workflow from DSH with zero port juggling and no repeated credential setup.