This release fixes issues for SREs watching stability and regressions.
✓ No known CVEs patched in this version
Topics
+13 more
Summary
AI summaryFixed MartinLoop execution in Claude Code desktop, VS Code, and Codex IDE by using the system Node.js instead of bundled Electron versions.
Full changelog
Fixes MartinLoop inside Claude Code desktop, VS Code, and Codex IDE
The problem
When MartinLoop runs inside Claude Code desktop, VS Code extensions, or the Codex IDE, it was only working in standalone PowerShell — not in the IDE terminal or agent panel.
Root cause: These applications bundle their own Electron Node.js. When MartinLoop spawned subprocesses using process.execPath, it was using Electron's Node — which has different module resolution and cannot reliably execute system npm CLI shims.
The fix
resolveSystemNode() now finds the actual system node.exe on PATH, skipping any path that contains "electron", "claude", "vscode", or "cursor" in its name. Falls back to process.execPath only if no system Node is found.
Escape hatch: Set MARTIN_NODE_PATH=/path/to/node to explicitly control which Node MartinLoop uses for subprocess execution.
What this fixes
martin runinside Claude Code desktop ✓martin runinside VS Code terminal ✓martin runinside Codex IDE ✓- PowerShell (was already working) ✓
Install
npm install -g [email protected]
Weekly OSS security release digest.
The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.
No spam, unsubscribe anytime.
Share this release
About Keesan12/Martin-Loop
All releases →Related context
Related tools
Earlier breaking changes
- vmcp-v0.1.3 martin_status uses oneOf for selector exclusivity, latest as const.
- vmcp-v0.1.3 maxIterations and maxTokens modeled as integers in tool schemas.
- vmcp-v0.1.3 Tool schemas enforce additionalProperties: false on public contracts.
- vmcp-v0.1.3 Packaged artifacts now require and ship server.json alongside package.json.
Beta — feedback welcome: [email protected]