Skip to content

fix(workbuddy): sanitize client environment WAF fingerprints in request payload - #310

Merged
caigee-cmd merged 1 commit into
caigee-cmd:mainfrom
favoroo:fix/workbuddy-waf-fingerprint
Oct 19, 2026
Merged

caigee-cmd merged 1 commit into
caigee-cmd:mainfrom
favoroo:fix/workbuddy-waf-fingerprint

Conversation

@favoroo

@favoroo favoroo commented Oct 18, 2026

Copy link
Copy Markdown
Contributor

Summary

WorkBuddy request payloads now sanitize client-environment fingerprint phrases (e.g. Main branch (target for pull requests) injected by ZCode / Claude Code) before dispatch. The Tencent WorkBuddy WAF detects these signatures and rejects requests with 11128: Illegal API invocation from an unapproved channel. The sanitizer rewrites them to neutral equivalents across all message roles and structured text parts, so requests are no longer rejected without discarding the user's system prompt.

Tests

  • go build ./..., go vet ./..., go test ./..., git diff --check
  • WorkBuddy client tests cover the sanitizer.

…est payload

- payload.go: transparently rewrite client signatures (e.g. 'Main branch (you will usually use this for PRs)') to prevent upstream WorkBuddy 11128 WAF rejection
- client_test.go: add TestPrepareBodySanitizesWAFFingerprints test coverage
- changelog/unreleased: add workbuddy-waf-fingerprint-sanitization.md
@caigee-cmd
caigee-cmd merged commit 6c81818 into caigee-cmd:main Oct 19, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants