Send the Chat bridge's Druks MCP header without a second Bearer prefix - #752
Merged
Merged
Conversation
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.
The Druks MCP token is a header row. Its stored value is
Bearer <token>, and egress puts that value where the placeholder is. The Chat bridge still addedBearerin front of the placeholder, so Druks gotAuthorization: Bearer Bearer druks_pat_…and returned 401.The bridge now sends the placeholder as the header value, the same way the harnesses send header rows. The bridge test's fake agent now expects the placeholder with no prefix.
Fixes #751
🤖 Generated with Claude Code