[Bug] Kernel bootstrap fails on native Windows — venv Python resolved as bin/python #1401
Laythros
started this conversation in
Bug reports
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Affected area
Installation or updates
What happened?
On native Windows, every kernel bootstrap fails at the pip-install step with "Failed to set up the Python kernel runtime."
Cause: bootstrapVenv and ensureKernelPython build the venv interpreter path as /bin/python unconditionally, but uv creates Windows venvs with the Scripts\python.exe layout (packages/coding-agent/src/core/kernel/bootstrap.ts, two call sites).
Everything else on Windows already works; daemon on named pipes, Git Bash shell resolution, uv.exe handling, so this appears to be the last blocker to a working ipython kernel on native Windows.
I have a verified fix (small venvPythonPath() helper mirroring the existing uv.exe platform branch): tested on Windows 11 with a fresh install and no PRIME_AGENT_KERNEL_PYTHON override — auto-bootstrap builds the venv and an ipython tool call executes end-to-end against a local Ollama model. Branch: Laythros/prime-agent:fix/windows-kernel-venv-python, happy to open the PR.
Steps to reproduce
Expected behavior
The kernel venv bootstraps and the ipython tool call executes.
Prime Agent version
0.7.2 — installed from the v0.7.2 GitHub release tarball via npm install -g (not the install.sh script, which is macOS/Linux-only)
Environment
Windows 11 Home (build 10.0.26200), native — not WSL. Node.js v24.12.0, npm 11.x global install. uv 0.11.1 (x86_64-pc-windows-msvc) on PATH. Git for Windows installed (Git Bash at the default path per docs/windows.md). Kernel Python: uv-managed 3.11. Shell: PowerShell / Windows Terminal. Model provider during repro: local Ollama (qwen3:8b) declared in ~/.prime/agent/models.json.
Additional context
No response
All reactions