Repository navigation
Fixes found by watching real sessions. The README now shows four of them: a flange modeled from one paragraph, a selected face rounded on request, a shaft and flange assembled and checked, and the drawing exported.
dsh plugin --profile web add @dshworks/dsh-solidworks@0.2.1
On a Windows VM paired with an earlier version, run pair.cmd again so the VM gets the new bridge. From this version on, an outdated bridge says exactly that instead of "unknown tool".
Why upgrade
- The right document. With a part and its drawing open under the same name,
sw_export {doc: "flange.slddrw"}exported the part. An exact name now always wins, and a.sldprt,.sldasmor.slddrwname only matches that kind of document. - Cuts that land. A cut sketched on a plane at the body's boundary pointed away from the material and removed nothing; a session spent three calls finding
reverse. With no direction given, such a cut is now made the other way and the step saysreversed. - You can watch it. In documents the bridge made or opened, builds and assemblies zoom to fit, so the part is on screen while dsh works.
- Clearer coordinates for the model: a 12 mm plate on the top plane has its top face at y = 12.
Verified, 2026-10-18
- SOLIDWORKS 2016 SP1 and 2019 SP0: 66 of 66 live checks each with this exe, including both fixes (an exact π·5²·4 mm³ reversed cut; a drawing exported by its
.slddrwname). - The four README clips: real dsh 0.2.0-rc.2 sessions with
deepseek-flash, 12, 17, 23 and 13 tool calls.
The exe
swbridge.exe below is the one in the npm package. CI rebuilds it from source to the same SHA-256 (bridge/swbridge.exe.sha256, .NET SDK 8.0.426):
fd6ec61c1e1200f3d45f618bdeed1a1140e78a88ecb68185bffe8a6b7fbd304b swbridge.exe
It is not code-signed; Windows SmartScreen may ask before the first run of a downloaded copy.
🤖 Generated with Claude Code