does not open window

[fegyi001]

Was giving a try for this plugin, but it does not seem to do anything for me.

When invoking it does not seem to finding the open-pane.ts as can be seen here:

{"action_id":"open","command":["bun","run","src/sessionizer/open-pane.ts"],"error":"No such file or directory (os error 2)","finished_unix_ms":1785137023172,"log_id":"plugin-log-66","plugin_id":"sessionizer","started_unix_ms":1785137023167,"status":"failed","stderr":"","stdout":""}],"type":"plugin_log_list"}

I have all the requirements (bun, fzf).

[andrewchng]

Hey @fegyi001 — looking again, the No such file or directory isn't about the .ts file: stderr/stdout are empty, and if bun had started it would print its own error: Module not found …. So herdr failed to spawn bun before anything ran — most often this means ~/.bun/bin isn't on the PATH herdr inherits. Can you run command -v bun and echo $PATH from a pane inside herdr to confirm?

[aspiers]

Confirming @andrewchng's diagnosis from a separate reproduction on Linux (Herdr 0.7.5, Sessionizer 0.6.2) — it is the PATH, not the .ts file.

Same symptom: "error":"No such file or directory (os error 2)", empty stdout/stderr, started_unix_ms and finished_unix_ms identical to the millisecond. Bun installed via the official installer at ~/.bun/bin/bun.

What confirmed it here:

$ env -i HOME=$HOME sh -c 'command -v bun'   # bare env, no shell rc
(nothing)

$ env -i HOME=$HOME sh -c 'echo $PATH'
/usr/local/bin:/usr/bin:/bin:.

~/.bun/bin is added by the shell rc, which Herdr's plugin exec does not source — so exec bun fails with ENOENT before the script is reached. An interactive command -v bun succeeds, which makes it look like bun is installed correctly.

Fix that worked, putting bun on the PATH Herdr actually uses:

sudo ln -s ~/.bun/bin/bun /usr/local/bin/bun

After that the action ran (exit_code: 0) and the picker opened normally.

@fegyi001 — worth noting the check needs to be a non-interactive one. command -v bun in a Herdr pane runs through your shell rc and will likely succeed even while the plugin still fails; env -i HOME=$HOME sh -c 'command -v bun' is the one that reproduces what Herdr sees.

Might be worth a README note under Requirements, since the official bun installer puts it in ~/.bun/bin by default and anyone installing that way on Linux will hit this. Happy to send a PR if useful.

[andrewchng]

Hey @aspiers , this is worth a readme update ! PRs are welcome. Thanks for the further diagnosis!