Keep your paths intact
Prepared commands preserve spaces, dollar signs, backticks, apostrophes and Unicode characters in Windows PowerShell 5.1 and PowerShell 7.
Attune Harness 1.8.1 · Checked November 16, 2026
Version 1.8.1 fixes prepared PowerShell commands containing Windows paths with spaces, special characters and trailing backslashes. Choose your configuration and see what the tests establish.
Prepared commands preserve spaces, dollar signs, backticks, apostrophes and Unicode characters in Windows PowerShell 5.1 and PowerShell 7.
In PowerShell 5.1, a path with whitespace and a trailing backslash no longer consumes the option that follows it.
The fix covers setup, plan and repair previews, review intake, and roundtable preparation. When a response is JSON, decode the command value before using it. Read the release notes.
Server tests, Windows 11 desktop observations and native ARM64 Python are separate profiles. Results below keep the package version and interpreter that were actually tested.
Scroll the table horizontally to compare all three columns.
| Configuration | What the evidence shows | What remains open |
|---|---|---|
| Windows Server 2022 and 2025x64 CPython 3.12.10 | Published 1.8.1 wheel passed. Each server passed 4,550 base tests, with 281 skips, two deselections and two passing subtests. Each also passed 94 offline SDK tests. Release checks. | These server results do not establish Windows 11 desktop or browser acceptance. |
| Windows 11 on x64 hardwarex64 CPython 3.12.10 | Published 1.8.0 report workflow passed. Three runs completed across PowerShell 5.1 and 7. Both probes passed 77 tests per run; HTML bytes and protected-file hashes matched. Desktop checkpoint. | A fresh 1.8.1 desktop walkthrough, browser inspection and investigation of a separate timed-out run. |
| Windows 11 on ARM64 hardwarex64 CPython 3.12.10 under emulation | 227 fix-candidate checks passed in Parallels across PowerShell 5.1 and 7. They covered argument transport, preparation and intake, including trailing backslashes. Candidate evidence. | The tested candidate still had 1.8.0 metadata. Its fix ships in 1.8.1, but this was not a fresh 1.8.1 desktop installation test or native ARM64 Python run. |
| Windows 11 on ARM64 hardwareNative ARM64 CPython 3.12 | Binary-only base installation is blocked. Version 1.8.1 retains tiktoken==0.12.0 and cryptography==50.0.2. Neither release provides a Windows ARM64 wheel in the checked PyPI file inventory. | Dependency resolution, source-build validation and native ARM64 runtime qualification. The retained 1.8.0 installation attempt stopped at tiktoken; no native Harness workflow ran. |
The supplemental windows-latest CI job also uses a Windows Server image. It does not replace a Windows 11 desktop check. GitHub runner images.
An ARM64 Windows device can run x64 Python under emulation. That is the interpreter used in the Parallels results above. Native ARM64 Python is a separate installation and validation path.
To compare your machine with the recorded desktop configurations, use x64 CPython 3.12 in a fresh environment on fixed local NTFS. Keep existing working environments and saved tasks intact. Start with the versioned installation guide, then choose a documented Windows workflow.
Record the hardware architecture, Windows build, Python version and architecture, shell version, and installed Harness version with each result. Python reporting win-amd64 identifies its target architecture; it does not prove that the hardware is x64.
Plan acceptance and execution remain separate decisions. Passing software checks does not establish model quality or full Windows parity. Read the reliability requirements.
f2baa8b1f9c0acaab2109cbc7facfb029c596586attune_harness-1.8.1-py3-none-any.whlf83e924599b0eb0b3d40c428a80cb8fc5794c22cf2341752702cccf2f98ceaaeThe earlier 1.7.0 release rehearsal and PowerShell 5.1 offline-report rehearsal retain their original versions and limits. Matching generated HTML bytes is separate from inspecting the report in a desktop browser.