jdx/fnox v1.21.0

v1.21.0: PowerShell integration and Windows fixes

on GitHub

v1.21.0 brings first-class PowerShell support for auto-loading secrets, plus two important fixes for Windows users.

Added

PowerShell integration (#421) -- @nbfritch

fnox now supports PowerShell (pwsh / powershell) alongside bash, zsh, fish, and Nushell for automatic secret loading. Add the following to your PowerShell profile to enable it:

(&fnox activate pwsh) | Out-String | Invoke-Expression

The integration hooks into the PowerShell prompt to run hook-env on each prompt, sets and unsets environment variables as you change directories, and prints the familiar fnox: +1 FOO / fnox: -1 FOO diff output. Tested on PowerShell 7.6 on macOS and Windows, as well as Windows PowerShell 5.1. See the Shell Integration guide for setup details.

Fixed

Windows: Nushell activation errors from backslashes in paths (#425) -- @john-trieu-nguyen

On Windows, fnox activate nu emitted paths with backslashes (e.g. C:\Users\john) inside Nushell double-quoted strings, which Nushell parses as escape sequences -- producing unrecognized escape after "\\" in string. Paths are now normalized to forward slashes so Nushell integration works out of the box on Windows.

Windows: Executable resolution for commands with extensions (#427) -- @john-trieu-nguyen

fnox exec -- npm install and similar commands previously failed on Windows because the Windows process API doesn't search PATHEXT the way a shell does, so npm (really npm.cmd) wouldn't be found. fnox exec, fnox edit, and the MCP server's exec tool now use which on Windows to resolve executables, matching shell behavior:

fnox exec -- npm install    # now works on Windows

Changed

• Switched from an inlined clap-sort module to the published clap-sort crate (#409)

New Contributors

• @nbfritch made their first contribution in #421
• @john-trieu-nguyen made their first contribution in #425

Full Changelog: v1.20.0...v1.21.0