Fish shell support

[maherbeg]

Hi!

I just started setting this up to experiment with. I love how it works at a high level but have had trouble with my setup which is definitely unusual, so feel free to close this.

I'm running

• fish shell
• pi
• on nixos

which means a lot of the traditional pieces for scanning things, or locating binaries may not work. Since fish isn't supported, the path extraction didn't work until I manually added something to ~/.profile - but it'd be nice to have it work without that.

On this same setup, right now, I get a "Couldn't load this folder" error when adding a new directory for a project. The error details is Litter.ClientError.Rpc("sever error -32604: failed to spawn command: No such file or directory (os error 2)"). I'm still hunting through the code to figure out what command is being spawned here and re-creating it in a non-interactive shell.

[0xSero]

Confirmed against current main. SSH commands are now forced through a POSIX shell, which avoids parsing fish syntax, but PROFILE_INIT still does not import fish or Nix profiles. The folder-load spawn failure also needs to be separated from binary discovery. Please attach the current resolver diagnostics and the specific failing spawned command when available.

[0xSero]

Draft PR #216 now covers the proven shell-environment gap: Fish login PATH import plus common Nix profile locations, while generated commands stay under POSIX sh. Focused/SSH/full Rust suites pass. A live Fish/NixOS SSH host remains the acceptance gate, and the reported folder-picker -32604 is explicitly not claimed fixed without host diagnostics.

[0xSero]

Shipped in #345 (merged): SSH import now includes fish and Nix profile paths, so login shells configured through them resolve on the shared Rust SSH path. Thanks for the report — closing.

[0xSero]

Status update: the shell-environment half of this is merged on main via #345 (85e5e2df) — SSH remote setup now imports Fish login PATH plus common Nix profile locations, while generated commands stay POSIX sh. Covered by three new PATH-resolution tests in cargo test -p codex-mobile-client (790 passing).

Still open from your report: the folder-picker -32604 error. That one needs host-side diagnostics on a live Fish/NixOS SSH host — if you can share the remote's $PATH shape (or the server log line around the picker call), that would unblock reproducing it here. Leaving the issue open for that piece; happy to close if the fish PATH import alone resolves your setup.