返回目录
其他 待识别

dsh-multi-tools

pirate-608/dsh-multi-tools

Multimodal tool suite for DeepSeek Harness: ModLens vision, local ComfyUI, Unity, creative apps, CAD, and Ren'Py.

Stars
1
Forks
0
Issues
0
更新
18 天前

PROJECT TOPICS

项目标签

PROJECT README

README

DSH Multi Tools

English | 简体中文

A private, install-once multimodal integration suite for DeepSeek Harness 0.1.2-alpha.3 or newer. One bundle adds the ModLens vision core, a Multi Tools settings page, dependency status, and independently managed Agent Presets for creative applications, game engines, and CAD tools.

Install

dsh plugin --profile web add github:pirate-608/dsh-multi-tools

Git dependencies build their Host and browser bundles during pnpm installation. If pnpm blocks the package's prepare script, add the exact package key it reports under allowBuilds in the Web profile's pnpm-workspace.yaml, then repeat the command. The package has no postinstall hook and does not install MCP runtimes, download models, or start desktop applications.

Restart the Web profile, then open Settings → Plugins → Multi Tools. ModLens is always present but has no route by default. Every optional integration starts disabled; enabling one creates its dedicated managed Preset for new sessions.

Remove a previously installed standalone @pirate-608/dsh-modlens bundle before adding the aggregate; both packages intentionally refuse to register the same modlens_read_image tool.

Multimodal workflow

  • modlens turns image files into logged structured evidence for text-only models through local Codex, an OpenAI-compatible endpoint, or local Ollama.
  • comfy-local inspects and runs local ComfyUI workflows through Comfy's first-party MCP and CLI tools.
  • Unity, Adobe, CAD, and Ren'Py integrations produce structured state plus file-based screenshots, previews, renders, or exports. They can pass those files to ModLens when visual interpretation is needed.
  • Native multimodal adapters remain in control of their own image input. The fallback never guesses capability from a model name.

The status page performs a passive installed check when opened. A live check runs only after the user requests it and contacts loopback services or short-lived local MCP probes without installing, downloading, launching applications, or exercising cloud vision routes.

CLI

dsh-multi-tools status [--live] [--json] [--integration <id>]
dsh-multi-tools doctor
dsh-multi-tools integrations set [<id>...] [--json]
dsh-multi-tools runtime <id> install|remove

Runtime actions remain explicit CLI operations. Unsupported removals fail clearly instead of guessing which user files are safe to delete.

ModLens routes live in the dsh-multi-tools section of the DSH settings document. No route is implied by installation:

dsh-multi-tools:
  modlens:
    routes:
      ollama:
        type: ollama
        baseUrl: http://127.0.0.1:11434
        model: qwen3-vl
    failover: [ollama]

Codex reuse additionally requires consent: true; OpenAI-compatible secrets remain DSH credential references rather than literal settings values.

Included integrations

Package Purpose
modlens Always-on text-first visual evidence through an explicitly configured Codex, OpenAI-compatible, or Ollama route
comfy-local Local ComfyUI discovery, workflow validation, generation, job monitoring, and output collection
unity Unity Editor automation through MCP for Unity 10.1.2 with file-based visual evidence
after-effects After Effects automation through ae-mcp
photoshop Photoshop automation through Windows COM
premiere Premiere Pro automation through a CEP bridge
autocad AutoCAD and headless DXF automation
solidworks SolidWorks COM and MCP workflows
renpy Ren'Py development, preview, and validation

The aggregate build copies an explicit allowlist of integration payloads and records a SHA-256 manifest. It excludes virtual environments, caches, tests, Codex manifests, and workspace dependencies. After Effects, Photoshop, Premiere, and AutoCAD remain personal-build integrations because their first-party redistribution status has not been resolved; this root package is private and must not be published to npm.

Development

Requires Node.js 22.19+ or 24+ and pnpm 10.

pnpm install
pnpm run check

Build and test commands do not publish the package, install external runtimes, download models, or connect to local creative applications.

CLASSIFICATION EVIDENCE

分类依据

项目类型待识别
功能分类其他
规则置信度

系统优先读取 GitHub Topics,再与站内分类词典和词根规则比对。当前命中: 无有效分类标签。