Engineering Bridge v1.2.1
v1.2.1 is a Windows compatibility patch for both supported executors: Codex and DSH.
DSH support itself was introduced in v1.2.0. This release focuses on making npm-installed Codex and DSH CLIs launch correctly and safely on Windows.
What changed
- Fixed Windows command resolution for npm-installed:
@openai/codex@deepseek-ai/dsh
- Standard Windows npm shims such as
codex.cmdanddsh.cmdare now resolved to their official Node entrypoints:@openai/codex/bin/codex.js@deepseek-ai/dsh/lib/bin.js
- Real
codex.exe/dsh.exeinstallations remain directly supported and preferred. - Both executors continue to run under Bridge's supervised read-only execution boundary.
Safer Windows launch path
The new Windows path does not rely on:
cmd.exeComSpecshell: true
Instead, npm-installed CLIs are launched through process.execPath and their official JavaScript entrypoints.
Codex instructions continue to travel through JSON-RPC stdin, while DSH instructions remain a single argv argument. If a trusted npm target cannot be resolved, Bridge fails closed instead of falling back to shell execution.
Windows verification
This release was validated on a real GitHub Actions windows-latest runner using:
- Node.js 22
- actual npm-installed
@openai/codex - actual npm-installed
@deepseek-ai/dsh
The smoke test confirmed:
- real
codex.cmdanddsh.cmdnpm layouts - Bridge command discovery on Windows
- successful launch of both official Node CLI entrypoints
- focused Codex / DSH executor tests
- clean build and typecheck
This verifies the Windows npm CLI launch path introduced in v1.2.1. It is not a claim of full certification across every Windows environment, MCP client, or installation method.
Also included from v1.2.0
Engineering Bridge supports both:
executor: "codex"executor: "dsh"
DSH remains pinned to Bridge's read-only execution boundary, including DSH_PERMISSION_MODE=read-only.
Release commit: 30e6b74b895d383ebf006e184a4b470c89020cf0