fix: add null guards for output.output in tool.execute.after hooks #1755
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #1746
Problem
Three
tool.execute.afterhooks crash withTypeError: undefined is not an object (evaluating 'output.output.toLowerCase')when MCP tools return results whereoutput.outputisundefined. This breaks ALL external MCP tools since v3.5.0.Affected Hooks
comment-checker/hook.tsoutput.output.toLowerCase()edit-error-recovery/hook.tsoutput.output.toLowerCase()task-resume-info/hook.ts.startsWith(),.includes(),.trimEnd()Fix
Added
if (!output.output || typeof output.output !== "string") returnguard at the top of each affected hook handler.Testing (TDD)
output.output— all passRelated
Summary by cubic
Prevent crashes in tool.execute.after hooks caused by undefined output from MCP tools, restoring compatibility with external tools. Fixes #1746.
Written for commit 8b44d3b. Summary will update on new commits.