Repository navigation
fix(installer): name System32's tar on Windows, not whatever PATH offers - #167
Open
jrlanglois wants to merge 1 commit into
Open
jrlanglois wants to merge 1 commit into
jrlanglois wants to merge 1 commit into
Conversation
jrlanglois
force-pushed
the
jrlanglois/fix/windows-tar-install
branch
2 times, most recently
from
November 16, 2026 19:27
8d091a3 to
1e39aab
Compare
An editor started from a Git Bash terminal hands its extension host that shell's PATH, where GNU tar sits ahead of System32. extractArchive asked for the bare name "tar", so GNU tar read the staging path C:\...\download.zip as a remote host:path - /usr/bin/tar: Cannot connect to C: resolve failed, exit 128 - and OpenCode V2 never launched: the agent card read "launch prerequisite unavailable". GNU tar cannot open a .zip at all either, and runtime-resolver.ts serves .zip on Windows, so bsdtar was the only tool that could do the job whatever the colon did. tarCommand(platform, env) resolves the tool instead of letting PATH pick it: the bare name everywhere else, SystemRoot (SystemDrive, then C:) 's System32\tar.exe on Windows - bsdtar, which reads .zip and .tar.gz and takes Windows paths, and ships with Windows 10 1803+. A tool that won't start now reports the path it tried. vitest pins the resolution and, on a Windows host, proves what it resolves really reports itself as bsdtar. Signed-off-by: Joël R. Langlois <joel.r.langlois@gmail.com>
jrlanglois
force-pushed
the
jrlanglois/fix/windows-tar-install
branch
from
November 16, 2026 20:01
1e39aab to
b974e31
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
An editor started from a Git Bash terminal hands its extension host that shell's PATH, where GNU tar sits ahead of System32.
extractArchiveasked for the bare nametar, so PATH handed it GNU tar. GNU tar read the staging pathC:\....\download.zipas a remotehost:path:/usr/bin/tar: Cannot connect to C: resolve failed, exit 128.Therefore, OpenCode V2 never launched; the agent card read "launch prerequisite unavailable".
GNU tar cannot open
.zipat all anyway, andruntime-resolver.tsserves.zipon Windows: onlybsdtarcould do the job.Repro
/usr/bin/tarprecedes System32 on PATH..zip.Cannot connect to C: resolve failed, exit 128; the agent card reads "launch prerequisite unavailable".Solution
tarCommand(platform, env)resolves the tool instead of letting PATH pick it: the bare name everywhere else,%SystemRoot%(SystemDrive, thenC:)'sSystem32\tar.exeon Windows - bsdtar, which reads.zipand.tar.gz, takes Windows paths, and ships with Windows 10 1803+.A tool that won't start now reports the path it tried. vitest pins the resolution and, on a Windows host, proves what it resolves really reports itself as
bsdtar.