DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to give Claude Code bash-style commands on Windows with Fauxnix

Connect Claude Code to Fauxnix so its bash commands run natively on Windows with GNU-style output.

Who it is forA developer on Windows using Claude Code who has no Git Bash or WSL installed and sees agent commands fail on PowerShell syntax.

The problemAgents write bash by default. On Windows, plain bash commands often fail or return PowerShell error dumps, and installing a bash toolchain is not always possible.

The outcomeClaude Code runs the bash commands it already knows through Fauxnix, and errors come back in bash style, such as 'cat: nope.txt: No such file or directory'.

What you need first

  • A Windows machine with PowerShell 5.1 or later (built in)
  • Node.js 22.20.0 or later (Node 18 and 20 are unsupported in v2)
  • npm to install the fauxnix-cli package
  • An agent harness such as Claude Code, Codex, OpenCode, Kimi Code, Qwen Code, or any MCP client

Steps

  1. npm install -g fauxnix-cli
  2. fauxnix install --claude
  3. fauxnix doctor
  4. claude mcp add fauxnix -- fauxnix mcp (only if you prefer to add the server by hand)

Prompt for your agent

Using the fauxnix MCP server from the 20000419/fauxnix repo, run `ls -la <target-dir> | head -5` through the bash tool. Expect GNU-style `ls -l` columns and no PowerShell table output, then confirm `fauxnix doctor` reports a successful MCP round trip.

Caveat. Fauxnix translates only the listed command subset, while unknown commands such as git and npm are passed through natively, so results outside that subset are not covered by the GNU-match claims.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page