Get unstuck

Troubleshooting

Start with the boundary and the exact released package versions, then reduce the problem with synthetic input.

01 · Troubleshooting

Common paths

Do not paste the original sensitive value into an issue, log, screenshot, or diagnostic.

Nothing changed: confirm the value actually crosses the wrapped handler, processor, callback, or tool-result boundary.
The request blocked: check for unsupported binary, encoded, structured, or protocol fields before changing policy.
Versions disagree: reinstall the exact current command shown on this site and inspect peer ranges.
A secret was missed: reproduce with an unmistakably synthetic value and compare the configured profile with the support matrix.
A false positive appeared: capture detector identity, action, and safe surrounding structure without the original secret.

02 · Troubleshooting

Potential vulnerabilities and sensitive reports belong in the private security channel, not a public issue.