[Bug] keys show does not read SAIL_PASSPHRASE from .sail/.env.local, but the daemon does

[walkonwayvs]

Summary

sailor keys show prompts for a passphrase even when SAIL_PASSPHRASE is set
correctly in .sail/.env.local. The daemon reads the same value from the same
file without prompting, so the two commands disagree about where the passphrase
comes from.

OS

Pop!_OS (Linux 6.18.7-76061807-generic)

Node.js version

v20.20.0

Install method

npm (@sail.money/sailor)

Sailor version

2.2.1

Chain

chain-independent

Command run / code executed

sailor keys show

Expected behavior

keys show reads SAIL_PASSPHRASE from .sail/.env.local, the same way the runner
does, and displays the keys without prompting.

Actual behavior

It prompts for a passphrase:

$ sailor keys show
Keys in .sail/keys/:
Password for agent wallet key:

Meanwhile sailor run and the installed systemd service both decrypt and sign
without prompting, using that same value from that same file.

Additional context

The failure reads as a wrong passphrase rather than as a command that doesn't
look in that file, so the natural response is to go re-verify a value that was
already correct.

Suggested fix: have keys show load .sail/.env.local the same way the runner
does, or state in the prompt that it reads only from the process environment.

[aadopii]

Confirmed and fixed. keys show called the key loader directly, which only read process.env.SAIL_PASSPHRASE, while the runner and daemon inject it from .sail/.env.local first. The two commands disagreed because they loaded the passphrase through different paths.

The fix moves that injection into the shared loader, so every key-loading command now reads the passphrase the same way the daemon does. Merged to feature/harbor (a833b92) and will land in the next release.

You called it precisely: the failure reads as a wrong passphrase, which sends someone to re-verify a value that was already correct. That framing made the root cause obvious. Thank you.