Bug: TALXIS CLI MCP fails on Windows due to invalid `~` path expansion in process path / working directory

[zdeneksrejber]

Bug: TALXIS CLI MCP fails on Windows because ~ is resolved to invalid paths

Summary

On Windows, the TALXIS CLI MCP server fails to start from VS Code because a path under the user profile is rewritten to ~ and then resolved incorrectly.

Observed bad paths:

• ~\.nuget\packages\talxis.cli.mcp\1.16.0\tools\net10.0\any\TALXIS.CLI.exe
• c:\~\Sources\my-agent-team

Error:

System.ComponentModel.Win32Exception (267)
The directory name is invalid.

Environment

• OS: Windows
• Workspace: c:\Users\zdene\Sources\my-agent-team
• Related repo also open: c:\Users\zdene\Sources\PCT21016
• MCP config: c:\Users\zdene\Sources\my-agent-team\.vscode\mcp.json
• txc version: 1.16.0+7c3d7b6f1f50617575ff5b0a1e59290d2b8947a1

MCP config

{
  "servers": {
    "TALXIS CLI": {
      "type": "stdio",
      "command": "dnx",
      "args": ["TALXIS.CLI.MCP", "--yes"]
    }
  }
}

Repro

1. Open VS Code on Windows.
2. Open a workspace under the user profile, e.g. c:\Users\zdene\Sources\my-agent-team.
3. Configure the MCP server with dnx TALXIS.CLI.MCP --yes.
4. Run any TALXIS CLI MCP operation.

Notes

• Reproduces after VS Code reload and MCP restart.
• txc --version works in terminal.
• txc workspace explain works in terminal.
• This appears to be MCP startup/path handling on Windows, not a repo issue.

Workaround

Use txc directly in a terminal instead of MCP.

[TomProkop]

Please test. Tried fix in PR #127. The MCP host now normalizes home-relative operational paths, including file URI workspace roots and tilde-prefixed subprocess paths, against the current user profile instead of letting them turn into invalid execution paths. Regression tests were added for MCP root conversion and path normalization behavior.

[TomProkop]

Released in txc / TALXIS.CLI.MCP v1.17.0.

Update local tools with:

dotnet tool update -g TALXIS.CLI --version 1.17.0
dotnet tool update -g TALXIS.CLI.MCP --version 1.17.0

Please retest with the latest MCP package and let us know if the Windows path issue still reproduces.

[zdeneksrejber]

Retested on Windows with talxis.cli / talxis.cli.mcp 1.17.0.

The fix did not help. I might run MCP locally to try fix the issue myself.

{
  "status": "failed",
  "error": {
    "message": "An error occurred trying to start process '~\\.dotnet\\tools\\.store\\talxis.cli.mcp\\1.17.0\\talxis.cli.mcp\\1.17.0\\tools\\net10.0\\any\\TALXIS.CLI.exe' with working directory 'c:\\~\\Sources\\my-agent-team'. The directory name is invalid.",
    "exitCode": -1
  },
  "diagnosticsUri": "txc://logs/80dcd528f1167492199ba6f5e2867601",
  "support": {
    "sessionId": "66ee3c1c-5b52-4340-87bc-0539253d617d",
    "operationId": "80dcd528f1167492199ba6f5e2867601",
    "reportUrl": "https://github.com/TALXIS/tools-cli/issues"
  }
}

[zdeneksrejber]

I can't reopen the issue, however I have solved my issue and here's the PR #132