Files
hyperframes/packages/cli/src
Michael WangandClaude Opus 5.5 a07d4cf738 fix(cli): printed Windows commands read folder names literally in every shell (#7769)
* fix(cli): printed Windows commands read folder names literally in PowerShell, cmd and Git Bash

shellArg's Windows branch wrapped any non-plain name in double quotes,
where PowerShell and Git Bash still expand $ and backticks. Names with
those characters (or PowerShell's curly quotes) are now single-quoted,
which both shells read literally; a name that cmd.exe would also split
on & | < > ^ gets no printed path, and the hint says to run the command
from the project folder. A bare comma or leading @ is quoted so
PowerShell does not read an array or a splat. Ordinary names with
spaces, accents and apostrophes print as before.

The background preview's stop footer uses the same helper instead of
JSON quoting, which left $(...) live in POSIX shells and PowerShell.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(cli): printed Windows paths with backslashes keep them in Git Bash

A Windows word containing a backslash printed bare, and Git Bash strips
unquoted backslashes, so C:\Users\Bob\film reached the CLI as
C:UsersBobfilm. Such words now take double quotes, which PowerShell,
cmd.exe and Git Bash all read as written; trailing backslashes are
doubled so they do not escape the closing quote.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(cli): open --json gives a null stopCommand when the folder has no safe spelling

When no spelling of the project folder is safe to paste in every Windows
shell, the left-running preview's stopCommand held prose. It is now null,
and stopCommandFromProject names the command to run from inside the
project folder. The printed line is unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* chore(cli): drop a comment the nullable return type already states

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(cli): a Windows name with no spelling common to every shell prints no path

PowerShell single quotes do not group a word in cmd.exe, and Git Bash
reads 'it''s' as its, so the single-quoted form printed for names with
$, a backtick or a curly double quote was wrong in two of the three
shells. Those names now take the existing null fallback, and the hint
says to run the command from the project folder.

Round-trip tests check that every printed Windows word reaches the
program unchanged: through Git Bash everywhere, and through cmd.exe and
PowerShell on Windows, where the CLI's Windows CI job now runs them.
The names cover apostrophes, typographic quotes, mixed quotes, cmd
operators and trailing backslashes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* test(cli): run the cmd.exe round-trip through spawnSync

execFileSync's options type has no windowsVerbatimArguments, so the
Windows-only cmd.exe test failed typecheck. spawnSync takes the option,
and the test now also checks the exit status.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* test(cli): expect the quoted Windows path in the relative open command

On Windows a relative path holds a backslash, which shellArg now prints in
double quotes so Git Bash keeps it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(cli): a Windows name with %NAME% or ! prints no path

cmd.exe expands %NAME% inside double quotes, and interactive Git Bash
history-expands ! there, so neither name reads literally in every
Windows shell. Both now take the null fallback. A lone % such as 100%
still prints.

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-15 06:35:32 +00:00
..