Shell Support: Validate and fix CMD (Command Prompt) syntax

[KatsuJinCode]

Summary

The CMD/Command Prompt syntax generator is currently untested and has known limitations. CMD has very limited alias support compared to other shells.

What needs testing

• Batch file syntax is correct
• IF/ELSE chains work properly
• DOSKEY commands function as expected
• Environment variable handling
• Profile names with special characters are handled
• Arguments pass through correctly (%*)

Known limitations

CMD doesn't support proper function definitions like other shells. The current implementation uses DOSKEY macros or batch files.

How to help

1. Generate a command with Smart Install enabled
2. Try to use it in CMD
3. Report back:
   • ✅ What worked
   • ❌ What failed (with error messages)
   • 🔧 Suggested fixes or workarounds

Recommendation

Consider using PowerShell instead of CMD for better functionality.

Related

Part of the multi-shell validation effort.

[KatsuJinCode]

@codex review and propose complete implementation plan

[chatgpt-codex-connector]

Here’s a concrete implementation plan to validate and fix CMD (Command Prompt) command generation.

Issue 1: Harden CMD batch generation for profile switching and argument passthrough
:::task-stub{title="Stabilize CMD batch generation in js/commands.js"}

• In js/commands.js (generateCmdCommand), switch comparisons to IF /I with an early guard for missing %1, and normalize %~1 to uppercase to align with other shells’ case-insensitive profile matching.
• Wrap generated bodies in setlocal EnableDelayedExpansion and escape %/! tokens so environment variables and special characters in profile names are preserved.
• Ensure the generated command sets a default profile when %1 is empty and passes arguments via %* (after shifting the profile token) so profiles and argument passthrough both work.
• Add a clearer fallback block for unknown profiles that emits a helpful message and non-zero exit code.
  :::

Issue 2: Provide a DOSKEY macro option for ephemeral sessions
:::task-stub{title="Add DOSKEY macro generation path"}

• Extend js/commands.js with a DOSKEY-specific generator (e.g., generateCmdDoskeyMacro) that emits doskey <alias>=cmd ... $* for single-session use, and surface it in the UI when the terminal is CMD.
• Update wrapCmdInstall to present both “create batch file” and “register DOSKEY macro” snippets, with correct percent escaping, so users can choose persistence level.
  :::

Issue 3: Add automated coverage for CMD output syntax
:::task-stub{title="Introduce tests to lock CMD syntax behavior"}

• Add a lightweight Node test harness (e.g., package.json + vitest or uvu) and export the generator helpers from js/commands.js for importability.
• Write fixtures that cover: multiple profiles with IF/ELSE chains, environment variable values containing %/!, profile names with spaces/special characters, %* passthrough, and DOSKEY macro output.
• Wire the test command into a CI-friendly script (npm test) and document how to run it locally in README.md or a short CONTRIBUTING section.
  :::

Issue 4: Clarify CMD limitations and guidance in the UI
:::task-stub{title="Enhance CMD warnings and usage tips in the UI"}

• In js/ui.js (or wherever terminal warnings are rendered), surface a CMD-specific notice that highlights limited alias support, the recommended PowerShell alternative, and links to the new batch/DOSKEY instructions.
• Add inline help near the generated command output explaining how to save the batch file, reload %PATH%, and how argument passthrough works.
  :::

View task →