Pulse v0.3.2-beta

Hotfix over 0.3.1-beta — MCP client connectivity and Claude Desktop compatibility.

Release-blocking fixes

Named-pipe exhaustion (IPC)

PulseMCP was healthy (listening on stdio) but could not reach PulseService:

• Symptom: IPC timeout connecting to PulseService / ERROR_PIPE_BUSY (231)
• Cause: pipe instance limit too low for UI + status-daemon + Cursor + Claude
• Fix: max_pipe_instances 32 (config + binary); clearer CreateNamedPipe error logging

Windows path / Claude Store config

• Cursor/Claude registration uses cmd.exe /c when the install path has spaces (Program Files)
• ASCII path preference for non-ASCII install trees (e.g. Masaüstü → C:\dev\Pulse-src when present)
• Microsoft Store Claude config path supported:
  %LOCALAPPDATA%\Packages\Claude_*\LocalCache\Roaming\Claude\claude_desktop_config.json
  (Register writes Store + classic %APPDATA%\Claude\...)

Claude tool name validation

Claude Desktop rejects dotted MCP tool names (FrontendRemoteMcpToolDefinition.name / ^[a-zA-Z0-9_-]{1,64}$).

Wire names are now underscores:

• system_cpu, process_list, mcp_self, report_export, …

PulseMCP 0.7.2.

Upgrade

1. Install Pulse-Setup-0.3.2-beta-windows-x64.exe
2. Restart PulseService if the installer did not (Diagnostics → Service)
3. Settings → AI Integration → Unregister → Register (Cursor + Claude)
4. Fully quit and reopen Cursor / Claude Desktop

Artifacts

• Pulse-Setup-0.3.2-beta-windows-x64.exe
• Pulse-0.3.2-beta-windows-x64.zip
• SHA256SUMS-0.3.2-beta.txt

See also v0.3.1-beta (private Node runtime) and v0.3.0-beta (MCP M2–M7).