Why command names are not case-sensitive

The command name itself is not case-sensitive. /Effort and /EFFORT both work exactly the same as /effort, since the name is matched regardless of how it happens to be typed.

This applies specifically to the command word itself, not to anything typed after it; arguments following the command name are passed through exactly as written, with their original casing fully preserved.

This is a small robustness choice: it means a command typed in a hurry, capitalized out of habit from starting a sentence, still works rather than failing on a technicality.

It also removes a whole category of easy-to-make mistakes from ever mattering: autocapitalize on a mobile SSH client, muscle memory from a different tool with case-sensitive commands, or simply pressing shift a beat too early, none of it breaks a command that would otherwise have worked.

This leniency applies only to the command word itself, never to file paths, search patterns, or other arguments passed to a command, all of which remain exactly as case-sensitive as the underlying filesystem or tool they are used with.