Repository navigation
fix: the log says when Plug refuses a client's request and why, where a refusal left no trace - #348
Merged
cyberpapiii merged 1 commit intoOct 8, 2026
Conversation
… a refusal left no trace Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
cyberpapiii
enabled auto-merge (squash)
October 8, 2026 13:55
cyberpapiii
deleted the
ship/the-log-says-when-plug-refuses-a-client-s-reques
branch
October 8, 2026 14:01
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
1 participant
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.
A client whose request Plug refused left nothing in the log, so the Grok Bot failure fixed in #347 took reading the client's own records to find.
Plug now logs each refusal with its reason. Sign-in challenges are routine and are left out.
🤖 Generated with Claude Code