Repository navigation
Releases
dsh-automation-suite 0.2.3
dsh-automation-suite 0.2.3 — home branding, Chinese UI, in-app picker
This release updates plugin content and one profile composition; the installer
flow is unchanged.
Added
- Home hero branding (
dsh-ui-brandmark): the landing headline is now
dsh-automation-suite, the badge isTIA-V17, and the mark is the desktop
shell's app icon (128 px PNG taken fromdesktop/DshSuite.Shell/app.icoand
inlined as a data URL at build time). Only the twoconversationkeys
(hero.headline,hero.preview) are overridden; every other string falls
through to the stock dictionaries, and the mark occupies the existing
conversation.hero.brand.markslot instead of the whale fallback. - Distinct guide icons for the five suite tabs on the right sidebar's start
page: PLC Blocks, Versions, Changes, Hardware and Drawings each ship their own
36-viewBox artwork, instead of the generic cube the start page shows when a
tab type has no icon. - Chinese sidebar names:
Prompt Guide→提示词引导and
Project Dashboard→项目看板. The prompt-guide client now registers a
dictionary and binds its rail label and iframe title through the locale
service; the page's heading, title and meta line follow the app language too.
Changed
- In-app directory picker: the suite profile disables upstream
dsh-host-directory-picker-autoand pins the browse pair
(dsh-host-directory-picker-browse+dsh-client-ui-directory-picker-browse).
"Add workspace" now always opens the in-app "Select Workspace Directory"
surface — on the loopback desktop/dev env as well as for remote/SSH clients —
instead of the Windows folder dialog. The installer andstart-envread the
same profile composition.
Verification
pnpm -r test(16 packages, all green),pnpm -r build,pnpm -r typecheck.build-app-layer.mjs --version 0.2.3: offline--dump-config+ doctor.- 0.2.3 silent install + fixed profile + shell
--smoke-test. - Manual preview under a zh-CN client: branded hero, Chinese sidebar, in-app
picker, and five distinct tab icons.
Upgrade
Exit the running app, then run this setup with the same DSH_HOME used by the
previous version (or let it use the default). The installer updates the shell and
app layer and keeps the fixed profile; previous cordis.patch.yml overrides are
backed up and merged.
Assets
dsh-automation-suite-setup-0.2.3.exedsh-automation-suite-setup-0.2.3.exe.sha256desktop-manifest.json
The installer is still unsigned; SmartScreen may show “Unknown publisher”.
dsh-automation-suite 0.2.2
dsh-automation-suite 0.2.2 — DSH desktop title bar
This is a shell-only visual/UX release. It changes no profile or plugin content
and no installer flow; it makes the desktop shell's window match the official
DeepSeek Harness desktop app and removes the line that appeared above the title
bar.
Added
- Frameless window matching the DSH desktop app: the DSH web client already
reserves a 40 px Windows title strip when the desktop marker is present. The
shell now sets that marker and renders theApplication/Editcaption menus
and the minimize / maximize / close controls inside it, using the DSH theme
tokens (light/dark follow the app theme). - Dragging the strip, double-click maximize/restore and the system menu on it are
handled by WebView2's non-client region support (IsNonClientRegionSupportEnabled),
the same interaction model as the official Electron app. Application→ About / Open Logs / Run Doctor / Exit;Edit→ Undo, Redo, Cut,
Copy, Paste, Select All. Paste reads the host clipboard over WebMessage and
inserts withexecCommand("insertText"), preserving the undo stack.- The old 30 px status line and
Readytext are gone; startup uses a full-client
loading layer that hides after navigation. - The initial window uses 90% of the monitor work area and centers itself (the
old fixed 1440×900 physical size was only ~740 CSS px wide at high DPI and made
the DSH layout collapse the sidebar).
Fixed
- Thin black line above the title bar (light and dark theme): the window's
client area now covers the whole window viaWM_NCCALCSIZE, so the title strip
starts at the visible top edge instead of below the system 8 px sizing frame.
DWMWA_BORDER_COLOR = DWMWA_COLOR_NONEsuppresses the DWM 1 px border.
Theme detection now uses the application's owndata-ds-dark-thememarker, not
the OSprefers-color-scheme(which used to paint the frame black in light
mode on a dark Windows theme). - Because there is no native non-client frame, resizing is initiated from the web
content: left/right/bottom edges detect a press and ask the host to start the
regular Win32 sizing loop (WM_NCLBUTTONDOWN). The 40 px top strip remains the
drag region; maximized clients are pinned to the monitor work area.
Verification
pnpm -r test(withDOTNET_ROOTpointed at.dotnet10),pnpm -r build,
pnpm -r typecheck.- 0.2.2 silent install + fixed profile + shell
--smoke-test. - Manual: strip drag, double-click maximize/restore, edge resize, window buttons,
both menus, copy/paste with the system clipboard, close-to-tray, Exit (DSH child
process gone), light and dark themes.
Known limitations
- The window buttons are drawn by the web page, so the Windows 11 snap-layout
flyout (hovering the maximize button) is not available. Dragging to a snap zone
and double-clicking the strip still work. - The top 40 px strip is the drag region; resize from the left, right or bottom
edges.
Upgrade
Exit the running app, then run this setup with the same DSH_HOME used by the
previous version (or let it use the default). The installer updates the shell and
app layer and keeps the fixed profile; previous cordis.patch.yml overrides are
backed up and merged.
Assets
dsh-automation-suite-setup-0.2.2.exedsh-automation-suite-setup-0.2.2.exe.sha256desktop-manifest.json
The installer is still unsigned; SmartScreen may show “Unknown publisher”.
dsh-automation-suite 0.2.1
dsh-automation-suite 0.2.1 — DPI and icon hotfix
This is a hotfix for 0.2.0. It changes no profile/plugin content and no
installer flow; it fixes the desktop shell's visual presentation.
Fixed
- Low-resolution / blurry UI: the shell project declared
ApplicationHighDpiMode=PerMonitorV2, butProgram.csdid not call
Application.SetHighDpiMode(...), so the process stayed system-DPI-aware and
Windows bitmap-scaled the window. The shell now explicitly sets
HighDpiMode.PerMonitorV2before creating any window; the process reports
awareness=2. - Missing application icon: added
desktop/DshSuite.Shell/app.icowith
16/24/32/48/64/128/256 sizes. The exe, window, tray icon, installer, desktop
shortcut and uninstall entry now use it instead of the default .NET icon.
Verification
- 0.2.1 installer silent install + fixed profile + shell smoke: pass.
- Shell process DPI awareness:
2(per-monitor). - Embedded icon extracted from both
DshSuite.Shell.exeand the setup exe. - Visual check on the host: icon and DPI are correct.
The functional acceptance from 0.2.0 (clean Windows 11 LTSC VM, DSH/WebView2
bootstrap, profile, doctor, shell smoke, uninstall) is unchanged.
Upgrade
Exit the running app, then run this setup with the same DSH_HOME used by 0.2.0
(or let it use the default). The installer updates the shell/app layer and keeps
the fixed profile; previous cordis.patch.yml overrides are backed up and merged.
Assets
dsh-automation-suite-setup-0.2.1.exedsh-automation-suite-setup-0.2.1.exe.sha256desktop-manifest.json
The installer is still unsigned; SmartScreen may show “Unknown publisher”.
dsh-automation-suite 0.2.0
dsh-automation-suite 0.2.0 — desktop installer
This is the first desktop installer release of dsh-automation-suite. It
installs the WebView2 shell, a materialized fixed profile, the local plugins,
and the graph engine; it does not require npm/pnpm at install time.
Correction: the “missing DSH” and “missing WebView2” cases were validated in
separate runs, not one VM that lacked both at the same time. Windows 11
restored WebView2 after reboot, so the WebView2-missing run used a controlled
removal right before setup.
Requirements
- Windows 10/11 x64.
- Internet access during setup if DSH or WebView2 is missing (they are downloaded
from the official sources and verified). - TIA Portal V17 / PLCSIM are not bundled; the suite reports their state via
doctor and the TIA plugin still requires a local TIA installation.
What setup does
- Materializes the app layer under
%LOCALAPPDATA%\dsh-automation-suite\app\0.2.0. - If
dsh.cmdis missing, downloads the official DSH installer, verifies its
SHA-512 and DeepSeek Authenticode signature, installs it silently, and waits
fordsh.cmd. - If WebView2 Runtime is missing, downloads the Evergreen Bootstrapper and
installs it. - Copies
app\0.2.0\profileto the fixed profile
%USERPROFILE%\dsh-automation-suite-home\profiles\dsh-automation-suite. - Merges previous user overrides from
cordis.patch.ymlwith the new baseline
and keeps a.bak-<stamp>copy. - Writes
install.json/current.txtand runsdoctor.ps1 -Json. - Creates the desktop/Start Menu shortcuts and the uninstaller.
Verified acceptance
Clean VM: Windows 11 Enterprise LTSC 2024 Evaluation. Two acceptance runs,
because Windows restores WebView2 during reboot:
- DSH absent, WebView2 present: setup installed DSH 0.2.2-rc.1, the fixed
profile, doctor, and the shell smoke passed. - WebView2 absent, DSH present: setup's WebView2 bootstrap installed
157.0.4341.42, the fixed profile, doctor, and the shell smoke passed.
install exit 0
DSH install 0.2.2-rc.1 (silent; SHA-512 + Authenticode)
WebView2 bootstrap 157.0.4341.42
install.json present
fixed profile present
current.txt present
doctor 8 OK / 4 WARN / 0 FAIL
shell --smoke-test ok=true, navigation=completed
uninstall install dir removed, DSH_HOME retained
The DSH download path was additionally verified with
bootstrap-dsh.ps1 -VerifyOnly against the live official feed.
Known limitations
- The installer is unsigned; Windows SmartScreen may show “Unknown
publisher”. Use “More info → Run anyway” for this build. - No auto-update. Upgrade by running a newer setup; it keeps the DSH_HOME and
the user's profile overrides. Previous app layers are kept side-by-side. - DSH version policy is not implemented yet: an existing DSH is used as-is and
doctor warns if it differs from the tested version. - Windows 10 was not separately acceptance-tested; the clean VM was Windows 11
LTSC. - TIA Portal / PLCSIM remain external prerequisites.
Assets
dsh-automation-suite-setup-0.2.0.exedsh-automation-suite-setup-0.2.0.exe.sha256desktop-manifest.json
The installer is self-contained for the shell; DSH is downloaded only when
missing.
dsh-automation-suite 0.1.5
dsh-automation-suite 0.1.5
发布日期:2026-11-07 · 最后一个以 Web 方式启动的版本
0.1.5 仍是“本机 Web UI”:start.cmd 启动 DSH 的 Web profile,用系统浏览器打开
http://127.0.0.1:<port>/?token=…,控制台窗口保留;桌面壳与安装器从下一阶段开始。
这个版本带来什么
新增 doctor:先告诉你能用什么
安装末尾会自动运行 doctor.ps1,解压目录里也有可双击的 doctor.cmd。它报告:
| 检查 | 说明 |
|---|---|
| DSH / profile / 插件行 | 合并后的 profile 是否能真正加载 |
图谱引擎 --self-test |
原生 SQLite + 解析 + 只读闸门;不依赖系统 .NET |
| .NET Framework 4.8 | TIA / PLCSIM 控制器的前提 |
| TIA Portal V17 | Openness DLL + 当前用户是否在 Siemens TIA Openness 组 |
| PLCSIM Advanced | API 4.0 是否存在 |
| Git | git.exe 是否可用 |
| 图纸 / Excel | pdfium WASM、unpdf、xlsx、fast-xml-parser 是否装上 |
| 模型凭据 | 首次启动仍需自己配 API key |
输出 [ OK ] / [WARN] / [FAIL]:只有 [FAIL] 会阻止启动;[WARN] 表示对应能力暂不可用。
doctor.ps1 -Json 是给桌面安装器复用的机器可读契约。
图谱引擎不再要求用户安装 .NET
dsh-engineering-graph 从 net8.0 升到 .NET 10 LTS,发布 tarball 里是 self-contained
win-x64 单文件(约 39 MB)。TIA Portal 只提供 .NET Framework 4.8、DSH 只提供 Node,
所以旧版实际上要求用户为一个插件单独装 .NET 8;0.1.5 起不再需要。仓库里的
engine/bin 仍是开发/测试用的 framework-dependent 构建,维护者重新构建需要 .NET 10 SDK。
Changes 面板(P1,只读)
右侧栏新增 Changes:按会话工作目录读取真实 git 状态,列出未提交文件与每文件
+N/−M,面板可见时每 5 秒刷新。提交区(P2)尚未实现,这个版本只读。
数据来自宿主的一条只读路由 GET /changes/api/status,不写工作区、不执行提交。
0.1.4 之后补齐的插件
dsh-drawing(电气图纸)、dsh-ui-versions(版本历史)、dsh-ui-hardware(硬件机架)、
dsh-ui-prompt-guide(Prompt Guide)、dsh-ui-project-dashboard(工作区面板)、
dsh-ui-changes(Changes)全部进入发行版:13 个本地插件 + dsh-opencode-go。
--dump-config 为 2090 行 / 14 个插件行(DSH 0.2.1-rc.2,全新 profile)。
安装
- 下载
dsh-automation-suite-0.1.5.zip; - 解压后双击
install.cmd(推荐;不要直接双击.ps1,MOTW 会让窗口一闪而过); - 安装末尾看 doctor 的能力表;
- 双击
start.cmd,浏览器打开本机 Web UI; - 首次进入在 设置 → Models 填 API key。
默认使用专用 home %USERPROFILE%\dsh-automation-suite-home,默认 profile
dsh-automation-suite-v0.1.5;与日常 ~/.dsh 完全隔离。
从旧版本升级
- 并存(推荐):解压新 zip 到新目录 →
install.cmd→ 用新目录的start.cmd。
新 profile 与旧 profile 并存;API key、workspace 注册表、会话目录都在同一个DSH_HOME下,会保留。 - profile 级设置不会自动迁移:旧 profile 的
cordis.patch.yml里应用回写的设置
(requestTimeoutMs、模型可见性等)需要复核/重设。固定 profile 原地升级可用
install.ps1 -Profile <名字> -Force,它会先备份package.json/cordis.patch.yml,
但仍需从备份合并用户覆盖项。 - 回退:用旧目录的
start.cmd,或dsh --profile dsh-automation-suite-v0.1.4。
已知限制
- TIA 部分仅 Windows + TIA Portal V17;需要 Openness DLL、.NET Framework 4.8,
当前用户在Siemens TIA Openness本地组里。 - PLCSIM 功能需要 PLCSIM Advanced API 4.0。
- Git 工具需要
git.exe;doctor 会报告缺失。 - Excel/PDF 不需要 Office/Acrobat,但安装时 npm 依赖需要访问 registry。
- 首次安装有网络依赖:十三个 tarball(约 34 MiB)+ npm 依赖。
- 没有自动更新:升级 = 下载新版本并重跑安装。
资产
dsh-automation-suite-0.1.5.zip- 13 个插件 tarball(含自包含图谱引擎)
manifest.json(版本、URL、大小、sha256、minDshVersion/testedDshVersion)
测试宿主:DSH 0.2.1-rc.2。
dsh-automation-suite 0.1.4
The preset picker now offers only the distribution's three presets.
What changed in 0.1.4
- The four built-in modes are disabled by default (Standard / PTC / Minimal / Creator).
They declare none of the distribution's engineering tool rows, so switching to one silently drops
TIA, git, engineering-context, and knowledge-graph tools. The profile now marks
preset-standard,preset-ptc,preset-minimal, andpreset-cordisasdisabled: true;
agentPresets.list()only returns registered presets, so they disappear from the picker. - The picker keeps
leader,auditor, andexpert.auditorandexpertmust stay
registered because thesubagenttool dispatches to them by preset id;auditorcan also be
opened directly. - Plugin tarballs are unchanged from 0.1.3.
To restore the built-in modes
Edit the installed profile's cordis.patch.yml and delete the four - id: preset-* /
disabled: true entries, then restart. This is not recommended: those modes have no engineering
tools and no distribution policy.
Upgrading
Install 0.1.4 into the private home as usual; it creates dsh-automation-suite-v0.1.4 alongside
0.1.3. The workspace list stays per-release-home and remains empty until you add folders.
# install once (extracted 0.1.4 zip)
.\install.cmd
# start
.\start.cmdIf you installed with a custom -DshHome / -Profile, start.cmd reads install.json, so it
launches the same place without arguments.
dsh-automation-suite 0.1.3
The release edition now gets its own DSH_HOME, so its workspace list is no longer shared with the everyday DeepSeek Harness desktop app.
What changed in 0.1.3
- Private home by default.
install.ps1installs the profile under
%USERPROFILE%\dsh-automation-suite-homeinstead of the everyday~/.dsh. DSH keeps
storages\workspace.json(the left-sidebar workspace registry), sessions, settings, and model
credentials underDSH_HOME; a private home means this edition starts with an empty workspace
list and only shows folders you add inside it. The desktop app's list is untouched, and the two
apps no longer write the same registry. start.cmdlauncher. After installing, double-clickstart.cmd. It readsinstall.json
(written by the installer, so custom-DshHome/-Profileinstalls work too), sets
DSH_HOME, picks a free port starting at 3093 (3080 is often taken on Windows), and opens the
browser. Options:-NoOpen,-Port 3093,-DshHome,-Profile.- Unchanged from 0.1.2:
install.cmd(double-click install, MOTW/execution-policy safe),
versioned profile names (dsh-automation-suite-v0.1.3), backups on-Force, junction refusal.
If you already installed 0.1.1/0.1.2 into ~/.dsh, that profile still exists there; the new
install does not use or modify it. You can delete it after verifying 0.1.3:
cmd /c rmdir /s /q "%USERPROFILE%\.dsh\profiles\dsh-automation-suite-v0.1.2"Install
- Download
dsh-automation-suite-0.1.3.zipand extract it. - Double-click
install.cmd(or run it from a terminal). - Double-click
start.cmd. - Configure a model API key on first launch (Settings → Models). Credentials live in the private
home, separate from the desktop app.
Requirements
- DeepSeek Harness 0.2.1-rc.x (presets generated from 0.2.1-rc.2)
- Node.js ≥ 22.19; pnpm comes from the DSH installation
- TIA features: Windows x64, TIA Portal V17, Openness DLL, .NET Framework 4.8, membership in
theSiemens TIA Opennesslocal group
Contents
Seven plugin tarballs plus dsh-opencode-go: TIA Openness V17, PLC simulation, engineering
context, engineering knowledge graph, git tools, PLC Blocks UI, TIA console UI. manifest.json
carries sha256 checksums for every asset.
dsh-automation-suite 0.1.2
Packaging-only release. Plugin contents are identical to 0.1.1; the only change is the installer entry point.
Fix: double-clicking the installer no longer flashes and closes
Files extracted from a downloaded zip carry the Windows mark-of-the-web (ZoneId=3). With the default RemoteSigned execution policy, double-clicking the unsigned install.ps1 fails with "cannot be loaded ... not digitally signed", and the PowerShell window closes before the message can be read. Installation never starts.
This release adds install.cmd:
- not subject to the PowerShell execution policy;
- runs
install.ps1with a per-process-ExecutionPolicy Bypass(the machine-wide policy is untouched); pauses at the end, so success output and errors stay on screen.
If you already installed 0.1.1, you do not need to reinstall: check for %USERPROFILE%\.dsh\profiles\dsh-automation-suite-v0.1.1, or run dsh --profile dsh-automation-suite-v0.1.1 --dump-config. This release is for future downloads.
Install
-
Download
dsh-automation-suite-0.1.2.zipand extract it. -
Double-click
install.cmd(or run it from a terminal). -
Start the profile printed by the installer:
dsh --profile dsh-automation-suite-v0.1.2
The profile is dsh-automation-suite-v0.1.2 by default, so it coexists with development profiles (dsh-automation-suite) and older releases. -DshHome, -Profile, and -Force work as before; -Force backs up package.json and cordis.patch.yml and refuses junctions.
If you prefer the .ps1 directly: right-click it → Properties → Unblock, or run
powershell -NoProfile -ExecutionPolicy Bypass -File .\install.ps1Contents
Seven plugin tarballs plus dsh-opencode-go: TIA Openness V17, PLC simulation, engineering context, engineering knowledge graph, git tools, PLC Blocks UI, TIA console UI. See the 0.1.1 notes for the asset table; manifest.json carries sha256 checksums.
dsh-automation-suite 0.1.1
Unofficial DeepSeek Harness distribution: TIA Portal V17 Openness, PLC simulation, an engineering knowledge graph, engineering-context tools, git tooling, and two Web UI plugins — plus the distribution's agent policy layer.
What changed in 0.1.1
- Release profiles are versioned. The installer now defaults to
dsh-automation-suite-v0.1.1instead of reusingdsh-automation-suite, so:- a development profile named
dsh-automation-suite(the default ofscripts/start-env.ps1, in its own isolatedDSH_HOME) is never touched, and - installing 0.1.2 later creates a new profile directory instead of colliding with this one.
- a development profile named
- Upgrades are explicit. To keep one stable name and upgrade in place, run
install.ps1 -Profile dsh-automation-suite-release -Force(or any name). Before overwriting, the installer backs up that profile'spackage.jsonandcordis.patch.ymlto.bak-<timestamp>. - Junctions are refused. The installer never writes through a junction/symlink, even with
-Force; it prints the exactcmd /c rmdircommand to remove the link instead. dsh-plcsim-advancedis included (seven plugins total).
Install (Windows, PowerShell)
-
Download
dsh-automation-suite-0.1.1.zipand extract it. -
Run the installer:
pwsh -NoProfile -File install.ps1
-
Start the profile printed by the installer:
dsh --profile dsh-automation-suite-v0.1.1
Useful switches: -DshHome <dir> (defaults to %USERPROFILE%\.dsh), -Profile <name> (defaults to dsh-automation-suite-v0.1.1), -Force (replace an existing real profile of that name, with backups).
The installer writes only <DSH_HOME>/profiles/<name>/ (three files), then installs the seven plugin tarballs attached to this release as direct URL dependencies. No npm account or repo checkout is needed.
Upgrading from 0.1.0
Run this release's install.ps1. It creates dsh-automation-suite-v0.1.1 alongside anything that already exists. If you want to keep using the old profile name, either start the new versioned profile or delete the old profile with cmd /c rmdir /s /q <path> after verifying the new one.
Requirements
- DeepSeek Harness 0.2.1-rc.x (the policy layer's presets are generated from 0.2.1-rc.2)
- Node.js ≥ 22.19; pnpm comes from the DSH installation
- TIA features: Windows x64, TIA Portal V17, Openness DLL, .NET Framework 4.8, membership in the
Siemens TIA Opennesslocal group - Model API key configured on first launch (Settings → Models)
Assets
| Asset | Contents |
|---|---|
voltarenyah-dsh-tia-openness-v17-min-0.1.0.tgz |
TIA V17 Openness block read/write via the whitelisted C# controller |
voltarenyah-dsh-plcsim-advanced-0.1.0.tgz |
PLC simulation workflows (snapshot/restore, download, TCP/IP) |
voltarenyah-dsh-engineering-context-0.1.0.tgz |
create_engineering_project / project_status / project_sync |
voltarenyah-dsh-engineering-graph-0.1.0.tgz |
XML → SQLite engineering knowledge graph (net8 engine included) |
dsh-tool-git-0.1.3.tgz |
Structured git tools (vendor copy of lxj808624/dsh-tool-git) |
dsh-ui-plc-source-0.1.0.tgz |
Web UI: PLC Blocks sidebar |
dsh-ui-tia-console-0.1.0.tgz |
Web UI: TIA console |
manifest.json lists sha256 checksums for every asset.
Verify
dsh --profile dsh-automation-suite-v0.1.1 --dump-configExpected: exit 0, all eight plugin rows (seven above + dsh-opencode-go), the preset-leader / preset-auditor / preset-expert rows, and engineering-context with disabled: true.
This is an unofficial project, not affiliated with DeepSeek or Siemens. MIT licensed; third-party notices are in the repository.
dsh-automation-suite 0.1.0
Unofficial DeepSeek Harness distribution: TIA Portal V17 Openness, an engineering knowledge graph, engineering-context tools, git tooling, and two Web UI plugins — plus the distribution's agent policy layer.
Install (Windows, PowerShell)
-
Download
dsh-automation-suite-0.1.0.zipand extract it. -
Run the installer:
pwsh -NoProfile -File install.ps1
-
Start the profile:
dsh --profile dsh-automation-suite
The installer writes only <DSH_HOME>/profiles/dsh-automation-suite/ (three files), then installs the six plugin tarballs attached to this release as direct URL dependencies. No npm account or repo checkout is needed.
Useful switches: -DshHome <dir> (defaults to %USERPROFILE%\.dsh), -Profile <name>, -Force (replace an existing profile).
Requirements
- DeepSeek Harness 0.2.1-rc.x (the policy layer's presets are generated from 0.2.1-rc.2)
- Node.js ≥ 22.19; pnpm comes from the DSH installation
- TIA features: Windows x64, TIA Portal V17, Openness DLL, .NET Framework 4.8, membership in the
Siemens TIA Opennesslocal group - Model API key configured on first launch (Settings → Models)
What is in assets/
| Asset | Contents |
|---|---|
voltarenyah-dsh-tia-openness-v17-min-0.1.0.tgz |
TIA V17 Openness block read/write via the whitelisted C# controller |
voltarenyah-dsh-engineering-context-0.1.0.tgz |
create_engineering_project / project_status / project_sync |
voltarenyah-dsh-engineering-graph-0.1.0.tgz |
XML → SQLite engineering knowledge graph (net8 engine included) |
dsh-tool-git-0.1.3.tgz |
Structured git tools (vendor copy of lxj808624/dsh-tool-git) |
dsh-ui-plc-source-0.1.0.tgz |
Web UI: PLC Blocks sidebar |
dsh-ui-tia-console-0.1.0.tgz |
Web UI: TIA console |
manifest.json lists sha256 checksums for every asset.
Verify
dsh --profile dsh-automation-suite --dump-configExpected: exit 0, all seven plugin rows (six above + dsh-opencode-go), the preset-leader / preset-auditor / preset-expert rows, and engineering-context with disabled: true.
This is an unofficial project, not affiliated with DeepSeek or Siemens. MIT licensed; third-party notices are in the repository.