精选
为什么选中它
待人工精选——以下事实来自源码仓库。
它能做什么
DSH plugin: auto-sync conversation turns to Honcho memory service
适合谁
想用 DSH 获得这项能力的用户;装前建议先看源码和文档。
风险提示
- 未发现明显风险信号;安装前仍建议查看源码。
DSH plugin: auto-sync conversation turns to Honcho memory service
待人工精选——以下事实来自源码仓库。
DSH plugin: auto-sync conversation turns to Honcho memory service
想用 DSH 获得这项能力的用户;装前建议先看源码和文档。
dsh plugin --profile web add github:nanpaidashi/dsh-honcho-sync 作者没有声明支持的平台。
bash # 方式 1:从 GitHub 直接安装(推荐) dsh plugin --profile web add link:https://github.com/nanpaidashi/dsh-honcho-sync dsh web # 方式 2:从 npm 安装 dsh plugin --profile web add @nanpaidashi/dsh-honcho-sync@latest ### 配置 方式 1:可视化面板(推荐) 打开 DSH → 左下角 设置 → Honcho Memory,直接填写: - Honcho URL(API 地址) - Workspace(工作区名称) - User / Agent Peer(标识符) - Debounce、Recall Budget、Max Chars(调优参数) - Auto Recall / Auto Sync(开关) 点击 Save 即生效,无需重启。 方式 2:环境变量 bash export HONCHO_URL="http://your-honcho-server:8000" # 必填 export HONCHO_WORKSPACE="your-workspace" # 必填 方式 3:cordis.patch.yml 在 ~/.dsh/profiles/web/cordis.patch.yml 中追加: yaml - id: honcho-sync config: honchoUrl: "http://your-honcho-server:8000" # Honcho API 地址(必填) workspace: "your-workspace" # Workspace 名称 userPeer: "user" # 用户标识 agentPeer: "agent" # Agent 标识 debounceMs: 3000 # 同步防抖(毫秒) autoRecall: true # 会话启动时自动 recall recallBudget: 2000 # recall token 上限 autoSync: true # 自动同步开关 messageMaxChars: 25000 # 单条消息最大字符数 环境变量速查: | 变量 | 默认值 | 必填 | 说明 | |------|--------|------|------| | HONCHO_URL | — | 是 | Honcho API 地址 | | HONCHO_WORKSPACE | — | 是 | Workspace 名称 | | HONCHO_USER_PEER | user | 否 | 用户标识 | | HONCHO_AGENT_PEER | agent | 否 | Agent 标识 | | HONCHO_DEBOUNCE_MS | 3000 | 否 | 同步防抖延迟(毫秒) | ### 架构 DSH Session │ ├─ session/event ──→ 自动同步(debounce)──→ Honcho API (POST messages) │ ├─ honcho_recall / search / remember / context / status │ └────────→ AI 可调用的记忆工具 │ ├─ session/start ──→ 上下文自动注入(autoRecall) │ └─ 设置面板 ──→ /_dsh/dsh-honcho-sync/status (loopback-only) ### 依赖 - Honcho — 需自行部署(Docker 一行命令) - DeepSeek Harness ≥ 0.1.0-rc.6 ### 许可证 MIT --- ## English ### What is this? A bridge plugin connecting DeepSeek Harness to Honcho memory. After installation, DSH auto-syncs every conversation turn to a self-hosted Honcho service (NAS, server, or cloud), and the AI gains built-in tools to recall, search, and remember across sessions. All settings are editable from a visual panel — no YAML editing required. ### Features | Feature | Description | |---------|-------------| | Visual Settings Panel | DSH Settings → "Honcho Memory" — all configuration in a graphical UI, no YAML editing | | Auto-sync | Every conversation turn synced to Honcho (debounced 3s default), no AI action needed | | honcho_recall | Semantic search across long-term memory. Call at session start or before important tasks. | | honcho_search | Search across ALL sessions for precise lookups. | | honcho_remember | Save facts, decisions, preferences to persistent memory. | | honcho_context | Get full conversation context for the current session. | | honcho_status | Check Honcho server health. | | Context injection | Auto-load recent context from Honcho on session start. | | Deduplication | Same content in same session won't be pushed twice. | ### Installation Prerequisite: Deploy Honcho first (one Docker command) bash # Option 1: Install from GitHub (recommended) dsh plugin --profile web add link:https://github.com/nanpaidashi/dsh-honcho-sync dsh web # Option 2: Install from npm dsh plugin --profile web add @nanpaidashi/dsh-honcho-sync@latest ### Configuration Option 1: Visual panel (recommended) Open DSH → bottom-left Settings → Honcho Memory, then fill in: - Honcho URL (API address) - Workspace (name) - User / Agent Peer (identifiers) - Debounce, Recall Budget, Max Chars (tuning) - Auto Recall / Auto Sync (toggles) Click Save — takes effect immediately, no restart needed. Option 2: Environment variables bash export HONCHO_URL="http://your-honcho-server:8000" # required export HONCHO_WORKSPACE="your-workspace" # required Option 3: cordis.patch.yml Append to ~/.dsh/profiles/web/cordis.patch.yml: yaml - id: honcho-sync config: honchoUrl: "http://your-honcho-server:8000" # Honcho API URL (required) workspace: "your-workspace" # Workspace name userPeer: "user" # User identifier agentPeer: "agent" # Agent identifier debounceMs: 3000 # Sync debounce (ms) autoRecall: true # Auto-recall on session start recallBudget: 2000 # Token budget for recall autoSync: true # Auto-sync toggle messageMaxChars: 25000 # Max chars per message Environment variables: | Variable | Default | Required | Description | |----------|---------|----------|-------------| | HONCHO_URL | — | Yes | Honcho API base URL | | HONCHO_WORKSPACE | — | Yes | Workspace name | | HONCHO_USER_PEER | user | No | User peer_id | | HONCHO_AGENT_PEER | agent | No | Agent peer_id | | HONCHO_DEBOUNCE_MS | 3000 | No | Sync debounce delay (ms) | ### Architecture DSH Session │ ├─ session/event ──→ Auto-sync (debounced) ──→ Honcho API (POST messages) │ ├─ honcho_recall / search / remember / context / status │ └────────→ Memory tools callable by the AI │ ├─ session/start ──→ Context auto-injection (autoRecall) │ └─ Settings panel ──→ /_dsh/dsh-honcho-sync/status (loopback-only) ### Dependencies - Honcho — Self-hosted memory service (one Docker command) - DeepSeek Harness ≥ 0.1.0-rc.6 ### License MIT不看 Star,人工一条条挑的。
把 DSH 的 settings.yaml 做成可视化看板:所有已注册的 settings namespace——包括官方界面从未覆盖的第三方插件配置——都渲染成可编辑表单。项目还早,但方向很对:告别手改 YAML。
给 DSH 的 DIY 轨迹可视化:把 agent 的计划与执行画成图,不用翻原始日志也能看清它在干嘛。项目还早,但补上了「一眼看懂 agent 在做什么」这个真实缺口。
从 Claude Code / Codex 把活派给 DSH:在宿主内拉起带分级预设的 DSH agent 会话,看原生子代理进度,还能借它的多模态桥给纯文本的 DSH 补上视觉和生图。编排型插件,把 DSH 变成其他编码 agent 的后端。