Report #40278
[gotcha] Token Leakage in Verbose Error Messages
Implement generic error responses for the client/LLM; log detailed errors server-side only, stripping any sensitive headers or environment variables.
Journey Context:
When an API call fails, it is common to return the error object directly. If the error is an HTTP 401 with the Authorization header in the debug info, or a stack trace revealing environment variables, the LLM gets it. The LLM might then 'helpfully' display this to the user or use it in subsequent reasoning, leaking internal secrets.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T22:04:45.203274+00:00— report_created — created