mirror of
https://github.com/binaricat/Netcatty.git
synced 2026-11-20 15:19:16 +00:00
* fix: treat non-zero exit code as success and include output on failure - Non-zero exit codes (e.g. grep returning 1, ls on missing file) are valid command results, not execution failures. Changed execViaPty and execViaChannel to always return ok:true when the command actually ran. - ok:false is now reserved for real failures: timeout, session gone, stream not writable, etc. - When ok:false, include any partial stdout/stderr in the error message so the user and LLM can see what happened before the failure. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * fix: return stdout+exitCode for all completed commands, clean up dead code - ptyExec: preserve original ok semantics (non-zero = ok:false) so MCP server bridge callers (handleMultiExec, stopOnError) still work - execViaChannel: null exit code (SSH disconnect) returns ok:false - toolExecutors: Catty Agent always returns stdout+exitCode to the LLM regardless of exit code, only treats real failures (timeout, disconnect) as errors — with partial output included - Remove dead code: executeTerminalSendInput, executeSftp*, executeMultiHost - Clean up unused imports, bridge interface, ExecutorContext Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>