During npm release work in /Users/kjopek/Workspace/ashby-mcp, terminal-pilot 0.0.37 still behaved unexpectedly.\n\nRepro from a repo with terminal-pilot installed:\n\nsh\nnpm install terminal-pilot@latest\nnpm install -g terminal-pilot@latest\nnpm list terminal-pilot --depth=0\nnpm list -g terminal-pilot --depth=0\nnpx terminal-pilot --version\nterminal-pilot --version\nterminal-pilot create-session --session tp-history-repro --observe -- zsh -lc 'echo hello'\nterminal-pilot wait-for-exit --session tp-history-repro --timeout 30000\nterminal-pilot read-history --session tp-history-repro --last 20\n\n\nObserved:\n- local/global npm package installs reported terminal-pilot@0.0.37, but npx terminal-pilot --version printed 1.0.0 and global terminal-pilot --version printed 0.40.2.\n- after wait-for-exit reports the process exit code, read-history fails with Session ... was not found. No active sessions are available.\n- same issue happened after a failed command, which meant the failure output was unavailable and I had to rerun the command outside terminal-pilot to see the error.\n\nExpected:\n- CLI version should identify the installed terminal-pilot npm version or otherwise clearly report the product/build version.\n- completed sessions should retain history long enough to inspect output after wait-for-exit, especially failures.\n\nThis made terminal-pilot hard to use as the supervised runner for release commands, because failures lost their diagnostic output.
During npm release work in /Users/kjopek/Workspace/ashby-mcp, terminal-pilot 0.0.37 still behaved unexpectedly.\n\nRepro from a repo with terminal-pilot installed:\n\n
sh\nnpm install terminal-pilot@latest\nnpm install -g terminal-pilot@latest\nnpm list terminal-pilot --depth=0\nnpm list -g terminal-pilot --depth=0\nnpx terminal-pilot --version\nterminal-pilot --version\nterminal-pilot create-session --session tp-history-repro --observe -- zsh -lc 'echo hello'\nterminal-pilot wait-for-exit --session tp-history-repro --timeout 30000\nterminal-pilot read-history --session tp-history-repro --last 20\n\n\nObserved:\n- local/global npm package installs reported terminal-pilot@0.0.37, butnpx terminal-pilot --versionprinted1.0.0and globalterminal-pilot --versionprinted0.40.2.\n- afterwait-for-exitreports the process exit code,read-historyfails withSession ... was not found. No active sessions are available.\n- same issue happened after a failed command, which meant the failure output was unavailable and I had to rerun the command outside terminal-pilot to see the error.\n\nExpected:\n- CLI version should identify the installed terminal-pilot npm version or otherwise clearly report the product/build version.\n- completed sessions should retain history long enough to inspect output afterwait-for-exit, especially failures.\n\nThis made terminal-pilot hard to use as the supervised runner for release commands, because failures lost their diagnostic output.