Repository navigation
2.4.6: reports to a webhook go as JSON (context and text) - #23
Merged
Merged
Conversation
… on request Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
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
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.
Why
Mitchell's report webhook is a Cursor automation. Its webhook hands the agent what arrives under
contextin a JSON body; 2.4.5 sent plain text.What changes
engine/report.py: a report to a webhook is sent as JSON with the whole report undercontextandtext(chat webhooks readtext), plustitle."format": "text"in~/.config/matthew-studio-kit/report.jsonsends plain text instead. The token stays in theAuthorizationheader only.Checked
One labelled test report sent to the real webhook in this format was accepted. Suite: 288 run, 285 pass; the same three fail on
mainin this checkout because hismy-styles/is in place here.🤖 Generated with Claude Code