fix(tools): content_read returns graceful not-found on 404 instead of error - #74
Merged
Merged
Conversation
… error
Reading a file that doesn't exist (e.g. probing an optional workflow/approvals
JSON when the backing MCP server isn't wired) returned { error, status: 404 },
which the client renders as a red OUTPUT-ERROR badge. Treat 404 as a graceful
not-found result ({ content: null, found: false, status: 404 }, no error field)
so absence reads cleanly and non-404 failures still surface as errors.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
mhaack
approved these changes
Aug 18, 2026
Contributor
|
🎉 This PR is included in version 1.30.3 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Reading a file that doesn't exist (e.g. probing an optional workflow/approvals JSON when the backing MCP server isn't wired) returned { error, status: 404 }, which the client renders as a red OUTPUT-ERROR badge. Treat 404 as a graceful not-found result ({ content: null, found: false, status: 404 }, no error field) so absence reads cleanly and non-404 failures still surface as errors.