erros using the cli

[navelya]

I have installed both gemeni and copilot and they both working inside a seperaet cli, whne trying to use them inside mysti i get those erros, for both of them i have tried to chagne the path manually, for gemeni it worked but it takes tons of time to answer a simple question even using the flash model.

for copilot it still didnt worked and now i got this error : "Error: spawn EINVAL"

[BahaAbuNojaim]

@navelya is this on windows? Can you share OS details

[navelya]

@navelya is this on windows? Can you share OS details

Yes , I'm on windows 11,
First I have tried the extension on antigravity, then I have tried on Vs code. Same results for both of them

[ryzen88]

For what its worth, i had exactly the same issue with the Einval, so i asked codex to fix it, this is what he came up with
Had errors with claude and gemini as well. Asked codex to fix it, seems to work now.

I traced the failure to Mysti’s Windows CLI launch path. On this machine, Codex works when spawned through a shell, but Mysti 0.4.0 was trying to spawn the CLI directly, which reproduces Error: spawn EINVAL.

I enabled mysti.useShellForCli in settings.json. Try Mysti chat again. If it still uses the old state, run Developer: Reload Window in VS Code once.
Mysti’s background suggestion/classifier code was looking for claude without .exe, then spawning it without a shell, which caused the spawn claude ENOENT errors. I set:

mysti.useShellForCli: true for the Codex spawn EINVAL path
mysti.claudeCodePath to the working bundled Claude binary:
C:\Users\user.vscode\extensions\anthropic.claude-code-2.1.81-win32-x64\resources\native-binary\claude.exe

I changed Mysti to use real executables instead of shell/npm shims in settings.json: mysti.claudeCodePath now points to claude.exe, mysti.codexPath now points to C:\Users\user.codex.sandbox-bin\codex.exe, and mysti.useShellForCli is back to false.

That should fix both the earlier spawn errors and the new Codex code 1 path. I also verified that codex.exe exec --json --dangerously-bypass-approvals-and-sandbox --skip-git-repo-check - runs successfully in J:\ComfyUI. Run Developer: Reload Window

I fixed the Gemini launch issue.
Mysti now uses a dedicated wrapper at mysti-gemini.cmd that calls your real node.exe, and settings.json now points mysti.geminiPath to that wrapper with mysti.useShellForCli enabled. I verified the wrapper runs gemini --version successfully.

[BahaAbuNojaim]

@ryzen88 Thank you so much for the detailed information. It would be great if you can contribute this fix and create a PR for it as we haven't managed to test this throughly on windows yet. Your contribution will be highly appreciated