keyshot-mcp 0.0.0 → 0.4.1

package/CONTRIBUTING.md

@@ -0,0 +1,45 @@
+# Contributing / 贡献指南
+
+## English
+
+Contributions are welcome.
+
+Useful areas:
+
+- Test with more KeyShot versions.
+- Improve compatibility with macOS and Linux paths.
+- Add examples for Claude Desktop, Codex, and other MCP clients.
+- Add more precise wrappers for KeyShot `lux` APIs.
+
+Before opening a pull request:
+
+```bash
+npm install
+npm run build
+npm run status
+```
+
+Do not include proprietary KeyShot scenes, license data, customer assets, or private render outputs in issues or pull requests.
+
+---
+
+## 中文
+
+欢迎参与贡献。
+
+比较有价值的方向：
+
+- 测试更多 KeyShot 版本。
+- 改进 macOS 和 Linux 路径兼容。
+- 增加 Claude Desktop、Codex 和其他 MCP 客户端示例。
+- 为 KeyShot `lux` API 增加更精确的封装。
+
+提交修改前建议先运行：
+
+```bash
+npm install
+npm run build
+npm run status
+```
+
+请不要在 issue 或 pull request 里上传专有 KeyShot 场景、许可证数据、客户资产或私人渲染结果。

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 KeyShot MCP contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -1,4 +1,538 @@
-# keyshot-mcp placeholder
+# KeyShot MCP
 
-This is a temporary placeholder package used to configure npm Trusted Publishing.
-The real package is maintained at https://github.com/truman-t3/keyshot-mcp.
+[![MCP Badge](https://lobehub.com/badge/mcp/truman-t3-keyshot-mcp)](https://lobehub.com/mcp/truman-t3-keyshot-mcp)
+[![GitHub Release](https://img.shields.io/github/v/release/truman-t3/keyshot-mcp)](https://github.com/truman-t3/keyshot-mcp/releases)
+[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](LICENSE)
+
+English | [中文](#中文说明)
+
+A local MCP server for controlling KeyShot Studio through KeyShot headless scripting.
+
+It lets an AI app that supports MCP ask KeyShot to inspect scenes, render images, import models, change materials, adjust cameras, set environments, and save scenes.
+
+Optimized for Windows-based KeyShot Studio product visualization workflows.
+
+Unlike GUI-only automation scripts, this project targets KeyShot headless workflows and keeps a stable MCP interface for AI agents.
+
+## Who This Is For
+
+- Designers who want AI-assisted KeyShot rendering.
+- Developers who want a simple stdio MCP bridge for KeyShot.
+- Teams that already have KeyShot licenses configured on their machines.
+
+This project does not include KeyShot, does not bypass licensing, and does not store license keys.
+
+## What It Can Do
+
+- Check whether KeyShot headless can start.
+- Inspect a `.bip` or supported KeyShot scene file.
+- Render a scene to an image.
+- Batch render multiple named cameras from one scene.
+- Import a model into a scene.
+- Apply a material to an object.
+- Create or update a camera.
+- Set an environment when the installed KeyShot version exposes that function.
+- Save a scene to a new file.
+
+## Example Workflows
+
+- Batch render multiple camera views from one KeyShot scene.
+- Test several material options on the same product model.
+- Generate product hero images with consistent resolution and output naming.
+- Import a model, apply a material preset, set a camera, and render in one AI instruction.
+
+## Workflow
+
+![KeyShot MCP Workflow](assets/workflow.svg)
+
+## Requirements
+
+- KeyShot Studio with `keyshot_headless` support.
+- Node.js 20 or newer.
+- A valid KeyShot license already configured on the computer.
+
+## Compatibility
+
+| Platform | KeyShot Version | Node Version | Status |
+| --- | --- | --- | --- |
+| Windows 11 | KeyShot Studio 2025 / 14.1 | Node 22 | Tested |
+| macOS | Not tested | - | Need contributors |
+| Linux | Not tested | - | Need contributors |
+
+## Install
+
+### Install the published npm package
+
+```bash
+npm install -g keyshot-mcp
+```
+
+The current release line is `0.4.1`. The published package is the easiest option
+when you only want to use the MCP server. You still need KeyShot Studio and a
+local KeyShot license.
+
+### Install from source
+
+```bash
+npm install
+npm run build
+```
+
+## Copy-Paste Setup Prompt for an Agent
+
+If you use Codex or another coding agent, you can copy this prompt and let the agent install the MCP server for you:
+
+```text
+Install the KeyShot MCP server from https://github.com/truman-t3/keyshot-mcp.
+
+Please:
+1. Clone the repository or use my local copy if it already exists.
+2. Run npm install and npm run build.
+3. Find my KeyShot headless executable path.
+4. Add a keyshot MCP server entry to my MCP client configuration.
+5. Set KEYSHOT_HEADLESS_EXE to the detected keyshot_headless path.
+6. Test the setup by running the keyshot_status tool.
+7. Tell me the exact config that was added and whether the status check passed.
+
+Do not store license keys or account passwords. Use my existing local KeyShot license configuration.
+```
+
+## Configure
+
+Set the path to your KeyShot headless executable.
+
+Windows PowerShell example:
+
+```powershell
+$env:KEYSHOT_HEADLESS_EXE="C:\Program Files\KeyShot Studio\bin\keyshot_headless.exe"
+```
+
+macOS/Linux shell example:
+
+```bash
+export KEYSHOT_HEADLESS_EXE="/Applications/KeyShot Studio.app/Contents/MacOS/keyshot_headless"
+```
+
+Then test startup:
+
+```bash
+npm run status
+```
+
+## MCP Client Example
+
+Add a server like this to your MCP client config:
+
+```json
+{
+  "mcpServers": {
+    "keyshot": {
+      "command": "node",
+      "args": ["/absolute/path/to/keyshot-mcp/dist/index.js"],
+      "env": {
+        "KEYSHOT_HEADLESS_EXE": "/absolute/path/to/keyshot_headless"
+      }
+    }
+  }
+}
+```
+
+A generic Codex configuration template is in:
+
+```text
+examples/codex.example.json
+```
+
+## Codex Configuration
+
+For Codex, add a `keyshot` MCP server entry to your Codex MCP configuration and point it to the built server file:
+
+```json
+{
+  "mcpServers": {
+    "keyshot": {
+      "command": "node",
+      "args": ["/absolute/path/to/keyshot-mcp/dist/index.js"],
+      "env": {
+        "KEYSHOT_HEADLESS_EXE": "/absolute/path/to/keyshot_headless"
+      }
+    }
+  }
+}
+```
+
+Use `examples/codex.example.json` as a starting point and replace all paths with paths on your own computer.
+
+## Prompt Examples
+
+```text
+Render the current KeyShot scene into three views: front, 45-degree perspective, and top-down. Use 1920x1080 resolution and save the outputs to the configured output folder.
+```
+
+```text
+Import the model file at /path/to/model.step, apply a brushed metal material to the main housing, set a 45-degree camera, and render a product hero image.
+```
+
+```text
+Inspect this KeyShot scene and summarize the available objects, cameras, materials, and renderable outputs.
+```
+
+```text
+List the cameras in this KeyShot scene, create or update a camera named "Hero",
+save the scene to a new file, and render one preview from that camera.
+```
+
+## Environment Variables
+
+- `KEYSHOT_HEADLESS_EXE`: path to `keyshot_headless` or `keyshot_headless.exe`.
+- `KEYSHOT_OUTPUT_DIR`: default output folder for renders.
+- `KEYSHOT_LICENSE_ARGS`: optional KeyShot headless license arguments. Empty by default.
+- `KEYSHOT_TIMEOUT_MS`: operation timeout in milliseconds. Default: `600000`.
+
+`samples` and `maxTimeSeconds` select different KeyShot render modes. Provide one
+or the other, not both.
+
+## MCP Tools
+
+- `keyshot_status`
+- `keyshot_inspect_scene`
+- `keyshot_list_cameras`: list available camera names in a scene (handy before batch rendering)
+- `keyshot_render`: render a single image
+- `keyshot_batch_render`
+- `keyshot_render_queue`: run several render jobs sequentially (stops at first failure unless `continueOnError`)
+- `keyshot_import_model`
+- `keyshot_apply_material`
+- `keyshot_list_material_presets`: list presets from the material preset library
+- `keyshot_apply_material_preset`: apply a named preset from the library to an object
+- `keyshot_set_camera`
+- `keyshot_set_environment`
+- `keyshot_save_scene`
+
+### Material preset library
+
+`keyshot_apply_material_preset` reads a small JSON registry so you can reuse named
+looks instead of remembering exact KeyShot material names. Default location:
+`presets/materials.json` (override with the `KEYSHOT_MATERIAL_PRESETS` env var).
+
+```json
+{
+  "Brushed Steel": { "materialName": "Steel Brushed", "description": "metal parts" },
+  "Clear Glass": { "materialPath": "C:/materials/glass_clear.mtl" }
+}
+```
+
+Each preset must have a `materialName` or a `materialPath`. Use
+`keyshot_list_material_presets` to see what is available.
+
+## MCP Prompts and Resources
+
+- Prompt: `keyshot_product_render`
+- Resource: `keyshot://workflow`
+
+Each tool returns JSON with:
+
+- `ok`
+- `data`
+- `outputFiles`
+- `warnings`
+- `keyshotStdoutTail`
+- `error`
+
+## Notes
+
+KeyShot's Python `lux` API changes across versions. This server keeps the MCP interface stable and returns a clear error when an installed KeyShot version does not expose a requested headless function.
+
+## Roadmap
+
+- [ ] Auto-discover and batch render all cameras in a scene
+- [x] Material preset library
+- [ ] Camera preset templates
+- [x] Sequential render queue
+- [ ] Safer output directory restrictions
+- [ ] More tested KeyShot versions
+- [ ] macOS compatibility verification
+- [x] Claude Desktop / Cursor / Codex config examples
+
+## License
+
+MIT
+
+---
+
+# 中文说明
+
+[English](#keyshot-mcp) | 中文
+
+这是一个本地 KeyShot MCP 服务，可以让支持 MCP 的 AI 工具通过 KeyShot 的无界面脚本能力控制 KeyShot Studio。
+
+简单说：你可以让 AI 帮你检查 KeyShot 场景、渲染图片、导入模型、替换材质、调整相机、设置环境并保存场景。
+
+本项目优先面向 Windows 环境下的 KeyShot Studio 产品渲染自动化流程。
+
+与仅面向界面操作的自动化脚本不同，本项目优先面向 KeyShot 无界面工作流，并为 AI Agent 提供稳定的 MCP 工具接口。
+
+## 适合谁使用
+
+- 希望用 AI 辅助 KeyShot 渲染的设计师。
+- 想要 KeyShot MCP 桥接工具的开发者。
+- 已经在电脑上配置好 KeyShot 授权的团队。
+
+这个项目不包含 KeyShot，不绕过 KeyShot 授权，也不会保存许可证密钥。
+
+## 能做什么
+
+- 检查 KeyShot 无界面程序是否能启动。
+- 检查 `.bip` 或 KeyShot 支持的场景文件。
+- 把场景渲染成图片。
+- 从同一个场景批量渲染多个指定相机。
+- 把模型导入场景。
+- 给对象替换材质。
+- 创建或更新相机。
+- 在当前 KeyShot 版本支持时设置环境。
+- 把场景保存为新文件。
+
+## 典型使用场景
+
+- 批量渲染同一个 KeyShot 场景的多个相机视角。
+- 对同一个产品模型快速测试多组材质方案。
+- 统一输出产品首图、封面图、详情页渲染图。
+- 用一句自然语言完成导入模型、替换材质、设置相机、渲染出图。
+
+## 工作流程
+
+![KeyShot MCP Workflow](assets/workflow.svg)
+
+## 使用要求
+
+- 已安装支持 `keyshot_headless` 的 KeyShot Studio。
+- Node.js 20 或更新版本。
+- 电脑上已经配置好有效的 KeyShot 授权。
+
+## 版本兼容表
+
+| 平台 | KeyShot 版本 | Node 版本 | 状态 |
+| --- | --- | --- | --- |
+| Windows 11 | KeyShot Studio 2025 / 14.1 | Node 22 | 已测试 |
+| macOS | 未测试 | - | 需要贡献者 |
+| Linux | 未测试 | - | 需要贡献者 |
+
+## 安装
+
+### 安装已发布的 npm 包
+
+```bash
+npm install -g keyshot-mcp
+```
+
+当前发布版本为 `0.4.1`。如果你只是想使用 MCP 服务，直接安装 npm 包最简单。
+电脑仍需要安装 KeyShot Studio，并且已经配置好本地 KeyShot 授权。
+
+### 从源码安装
+
+```bash
+npm install
+npm run build
+```
+
+## 复制给 Agent 的安装提示词
+
+如果你使用 Codex 或其他编程 Agent，可以复制下面这段话，让 Agent 帮你安装和配置 MCP：
+
+```text
+请帮我安装 KeyShot MCP Server：https://github.com/truman-t3/keyshot-mcp。
+
+请你：
+1. 克隆这个仓库；如果本地已有，就使用本地版本。
+2. 运行 npm install 和 npm run build。
+3. 查找我电脑上的 KeyShot headless 可执行文件路径。
+4. 把 keyshot MCP server 添加到我的 MCP 客户端配置里。
+5. 把 KEYSHOT_HEADLESS_EXE 设置为检测到的 keyshot_headless 路径。
+6. 用 keyshot_status 工具测试是否配置成功。
+7. 最后告诉我实际添加的配置，以及状态检查是否通过。
+
+不要保存许可证密钥、账号密码或授权信息。直接使用我电脑上已有的 KeyShot 本地授权配置。
+```
+
+## 配置
+
+需要告诉 MCP 服务 KeyShot 无界面程序在哪里。
+
+Windows PowerShell 示例：
+
+```powershell
+$env:KEYSHOT_HEADLESS_EXE="C:\Program Files\KeyShot Studio\bin\keyshot_headless.exe"
+```
+
+macOS/Linux 示例：
+
+```bash
+export KEYSHOT_HEADLESS_EXE="/Applications/KeyShot Studio.app/Contents/MacOS/keyshot_headless"
+```
+
+然后测试能否启动：
+
+```bash
+npm run status
+```
+
+## MCP 客户端配置示例
+
+把类似下面的配置加到你的 MCP 客户端里：
+
+```json
+{
+  "mcpServers": {
+    "keyshot": {
+      "command": "node",
+      "args": ["/absolute/path/to/keyshot-mcp/dist/index.js"],
+      "env": {
+        "KEYSHOT_HEADLESS_EXE": "/absolute/path/to/keyshot_headless"
+      }
+    }
+  }
+}
+```
+
+通用 Codex 配置模板在：
+
+```text
+examples/codex.example.json
+```
+
+## Codex 配置
+
+如果你使用 Codex，请在 Codex 的 MCP 配置里添加一个 `keyshot` 服务，并指向构建后的服务文件：
+
+```json
+{
+  "mcpServers": {
+    "keyshot": {
+      "command": "node",
+      "args": ["/absolute/path/to/keyshot-mcp/dist/index.js"],
+      "env": {
+        "KEYSHOT_HEADLESS_EXE": "/absolute/path/to/keyshot_headless"
+      }
+    }
+  }
+}
+```
+
+`examples/codex.example.json` 是通用配置模板。使用时请把里面的路径换成自己电脑上的路径。
+
+## 提示词示例
+
+```text
+把当前 KeyShot 场景渲染成三个视角：正视图、45 度透视图和俯视图。分辨率为 1920x1080，并保存到默认输出文件夹。
+```
+
+```text
+导入 /path/to/model.step，给主体外壳应用拉丝金属材质，设置 45 度相机，并渲染一张产品主视觉图。
+```
+
+```text
+检查当前 KeyShot 场景，并总结场景中的对象、相机、材质和可渲染输出。
+```
+
+```text
+列出当前 KeyShot 场景中的相机，创建或更新一个名为“Hero”的相机，
+把场景保存为新文件，并用这个相机渲染一张预览图。
+```
+
+## 环境变量
+
+- `KEYSHOT_HEADLESS_EXE`：`keyshot_headless` 或 `keyshot_headless.exe` 的路径。
+- `KEYSHOT_OUTPUT_DIR`：默认渲染输出文件夹。
+- `KEYSHOT_LICENSE_ARGS`：可选的 KeyShot 无界面许可证参数，默认留空。
+- `KEYSHOT_TIMEOUT_MS`：单次操作超时时间，单位毫秒，默认 `600000`。
+- `KEYSHOT_MATERIAL_PRESETS`：材质预设库 JSON 文件路径，默认 `presets/materials.json`。
+
+`samples` 和 `maxTimeSeconds` 是两种不同的 KeyShot 渲染模式，请二选一，不要同时传入。
+
+## MCP 工具
+
+- `keyshot_status`：检查 KeyShot 是否能启动。
+- `keyshot_inspect_scene`：检查场景内容。
+- `keyshot_list_cameras`：列出场景中所有相机名称（批量渲染前很有用）。
+- `keyshot_render`：渲染单张图片。
+- `keyshot_batch_render`：批量渲染多个相机视角。
+- `keyshot_render_queue`：顺序执行多个渲染任务（默认遇错即停，设置 `continueOnError` 可继续）。
+- `keyshot_import_model`：导入模型。
+- `keyshot_apply_material`：替换材质。
+- `keyshot_list_material_presets`：列出材质预设库中的预设。
+- `keyshot_apply_material_preset`：把预设库中的某个命名材质应用到物体上。
+- `keyshot_set_camera`：设置相机。
+- `keyshot_set_environment`：设置环境。
+- `keyshot_save_scene`：保存场景。
+
+### 材质预设库
+
+`keyshot_apply_material_preset` 会读取一个小的 JSON 注册表，让你用"好记的名字"复用材质，
+而不必记住 KeyShot 里精确的材质名。默认位置：`presets/materials.json`
+（可用环境变量 `KEYSHOT_MATERIAL_PRESETS` 覆盖）。
+
+```json
+{
+  "拉丝钢": { "materialName": "Steel Brushed", "description": "金属件默认材质" },
+  "透明玻璃": { "materialPath": "C:/materials/glass_clear.mtl" }
+}
+```
+
+每个预设必须包含 `materialName` 或 `materialPath`。用 `keyshot_list_material_presets` 查看有哪些预设。
+
+## MCP 提示词和资源
+
+- 提示词：`keyshot_product_render`
+- 资源：`keyshot://workflow`
+
+每个工具都会返回 JSON，包含：
+
+- `ok`：是否成功。
+- `data`：主要结果。
+- `outputFiles`：生成的文件。
+- `warnings`：警告信息。
+- `keyshotStdoutTail`：KeyShot 输出摘要。
+- `error`：错误信息。
+
+## 说明
+
+KeyShot 的 Python `lux` API 会随版本变化。这个 MCP 会尽量保持对外工具名称稳定；如果当前 KeyShot 版本不支持某个无界面功能，会返回明确错误，而不是假装成功。
+
+## 路线图
+
+- [ ] 自动发现并批量渲染场景中的所有相机
+- [x] 材质预设库
+- [ ] 相机预设模板
+- [x] 顺序渲染队列
+- [ ] 更安全的输出目录限制
+- [ ] 测试更多 KeyShot 版本
+- [ ] 验证 macOS 兼容性
+- [x] 补充 Claude Desktop / Cursor / Codex 配置示例
+
+## 测试
+
+项目带了两套测试，不依赖真实的 KeyShot 也能跑：
+
+- **TypeScript 测试（Vitest）**：覆盖配置读取、参数校验（schemas）、结果封装，以及用"假 KeyShot"跑通一次成功路径并验证 `work/tmp` 临时文件会被清理。
+
+  ```bash
+  npm install
+  npm test
+  ```
+
+- **Python bridge 测试（unittest）**：用假的 `lux` 对象验证 `import_model` 会真正打开基础场景、`set_camera` 在拿不到相机对象时不会崩溃并回退到 `lux` 级 API。
+
+  ```bash
+  python tests/test_bridge.py
+  ```
+
+## 开源协议
+
+MIT
+
+## Star History / 星标趋势
+
+![Star History Chart](assets/star-history.svg)
+
+This chart is generated from GitHub stargazer data and refreshed by GitHub Actions.
+
+这张图由 GitHub star 数据生成，并通过 GitHub Actions 定时刷新。

package/SECURITY.md

@@ -0,0 +1,33 @@
+# Security / 安全说明
+
+## English
+
+This MCP server runs KeyShot headless on the local machine. It can read scene/model files and write rendered images or saved scenes.
+
+### Safe Use
+
+- Only connect this server to MCP clients you trust.
+- Only open scene/model/material files from trusted sources.
+- Do not put license keys, account passwords, or private tokens in prompts.
+- Prefer using the local KeyShot license configuration instead of passing license details through environment variables.
+
+### Reporting Issues
+
+If you find a security issue, open a private advisory or contact the project maintainer directly before posting details publicly.
+
+---
+
+## 中文
+
+这个 MCP 服务会在本机运行 KeyShot 无界面程序。它可以读取场景、模型、材质文件，也可以写入渲染图片或保存后的场景文件。
+
+### 安全使用建议
+
+- 只把这个服务连接到你信任的 MCP 客户端。
+- 只打开来源可信的场景、模型和材质文件。
+- 不要在提示词里输入许可证密钥、账号密码或私人 token。
+- 优先使用本机已经配置好的 KeyShot 授权，不建议通过环境变量传递许可证细节。
+
+### 报告安全问题
+
+如果发现安全问题，请先通过私密方式联系维护者，不要直接公开细节。

package/dist/cli/status.js

@@ -0,0 +1,5 @@
+import { getConfig } from "../config.js";
+import { runKeyShotSerialized } from "../runner.js";
+const result = await runKeyShotSerialized(getConfig(), { operation: "status" });
+console.log(JSON.stringify(result, null, 2));
+process.exit(result.ok ? 0 : 1);

package/dist/config.js

@@ -0,0 +1,51 @@
+import path from "node:path";
+import { fileURLToPath } from "node:url";
+const DEFAULT_KEYSHOT_EXE = process.platform === "win32" ? "keyshot_headless.exe" : "keyshot_headless";
+const DEFAULT_TIMEOUT_MS = 600_000;
+export function getConfig() {
+    const projectRoot = path.resolve(fileURLToPath(new URL("..", import.meta.url)));
+    const keyshotOutputDir = path.resolve(process.env.KEYSHOT_OUTPUT_DIR ?? path.join(projectRoot, "outputs"));
+    return {
+        projectRoot,
+        keyshotHeadlessExe: process.env.KEYSHOT_HEADLESS_EXE ?? DEFAULT_KEYSHOT_EXE,
+        keyshotOutputDir,
+        keyshotLicenseArgs: splitWindowsArgs(process.env.KEYSHOT_LICENSE_ARGS ?? ""),
+        keyshotTimeoutMs: parsePositiveInt(process.env.KEYSHOT_TIMEOUT_MS, DEFAULT_TIMEOUT_MS),
+        tmpDir: path.join(projectRoot, "work", "tmp"),
+        bridgeScriptPath: path.join(projectRoot, "scripts", "keyshot_bridge.py"),
+        materialPresetsPath: path.resolve(process.env.KEYSHOT_MATERIAL_PRESETS ?? path.join(projectRoot, "presets", "materials.json")),
+    };
+}
+function parsePositiveInt(value, fallback) {
+    if (!value)
+        return fallback;
+    const parsed = Number.parseInt(value, 10);
+    return Number.isFinite(parsed) && parsed > 0 ? parsed : fallback;
+}
+function splitWindowsArgs(value) {
+    const args = [];
+    let current = "";
+    let quote = null;
+    for (let i = 0; i < value.length; i += 1) {
+        const ch = value[i];
+        if ((ch === '"' || ch === "'") && quote === null) {
+            quote = ch;
+            continue;
+        }
+        if (ch === quote) {
+            quote = null;
+            continue;
+        }
+        if (/\s/.test(ch) && quote === null) {
+            if (current) {
+                args.push(current);
+                current = "";
+            }
+            continue;
+        }
+        current += ch;
+    }
+    if (current)
+        args.push(current);
+    return args;
+}