Can I customize Crush's system prompt to the LLMs such that the LLMs know we are in PowerShell on Windows and not in GNU Bash?

[ksze]

I use Crush from PowerShell on Windows and I have absolutely no intention of installing BSD/GNU utils. I want to rely solely on Windows' and PowerShell's built-in commands for functions equivalent to Bash commands and BSD/GNU utils. Right now, Crush doesn't seem to tell the LLMs about my environment, so the LLMs default to building command lines for Bash and GNU utils. This of course means lots of unnecessary errors.

Where can I configure the system prompt that Crush sends to LLMs so I can tell the LLMs that I'm on Windows with PowerShell?

[marifcelik]

crush does not execute commands directly. Instead, it uses the mvdan/sh package to run POSIX-compliant commands in a special shell (gosh). I don't know why they chose this, but LLMs do not access the shell directly.

[ksze]

@marifcelik
The problem is not so much about how crush executes commands. It's about what commands it thinks it has access to.