Summary
Strix treats the colon in a Windows drive letter as the separator between a source file and its optional sandbox destination
Passing a bare path such as C:\temp\wordlist.txt makes Strix look for a file named C and stop before the scan starts
Reproduction on Windows
Run these commands in PowerShell on Windows
$dir = Join-Path $env:TEMP "strix-workspace-file-repro"
New-Item -ItemType Directory -Force $dir | Out-Null
Set-Content -Path (Join-Path $dir "wordlist.txt") -Value "admin"
strix -n --target https://example.com --workspace-file (Join-Path $dir "wordlist.txt")
Current result and expected result
Argument parsing exits with code 2 and reports that C is not an existing file
Strix should use the complete Windows path as the source and wordlist.txt as the default destination
The explicit PATH:DEST form should also work when PATH starts with a Windows drive letter
Technical note
resolve_workspace_files calls rpartition(":") before deciding whether the colon belongs to a drive letter
Scope
The parser needs to handle both C:\path\file and C:\path\file:dest/file without changing relative or POSIX path behavior
A focused regression test for those two Windows forms should be enough to protect the fix
Summary
Strix treats the colon in a Windows drive letter as the separator between a source file and its optional sandbox destination
Passing a bare path such as
C:\temp\wordlist.txtmakes Strix look for a file namedCand stop before the scan startsReproduction on Windows
Run these commands in PowerShell on Windows
Current result and expected result
Argument parsing exits with code 2 and reports that
Cis not an existing fileStrix should use the complete Windows path as the source and
wordlist.txtas the default destinationThe explicit
PATH:DESTform should also work whenPATHstarts with a Windows drive letterTechnical note
resolve_workspace_filescallsrpartition(":")before deciding whether the colon belongs to a drive letterScope
The parser needs to handle both
C:\path\fileandC:\path\file:dest/filewithout changing relative or POSIX path behaviorA focused regression test for those two Windows forms should be enough to protect the fix