[FEATURE]: secrets redaction at tool output boundary #32183

Activity

1. github-actions

   assigned

   StarpTech

   on Jun 13, 2026
2. github-actions commented on Jun 13, 2026

   

   github-actionsBot

   on Jun 13, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue doesn't fully meet our contributing guidelines.

   What needs to be fixed:

   • Feature requests must use the [FEATURE]: title prefix (e.g., [FEATURE]: secrets redaction at tool output boundary)
   • The feature request template requires a verification checkbox confirming you have searched for existing similar requests before submitting

   Please edit this issue to address the above within 2 hours, or it will be automatically closed.

   ---

   This issue might be a duplicate of existing issues. Please check:

   • [FEATURE] Pre/post API call hooks in Provider interface for secret redaction and exfiltration prevention #19425: Pre/post API call hooks in Provider interface for secret redaction and exfiltration prevention — very similar goal of redacting secrets before they reach the LLM
   • [FEATURE]: Security Context-aware handling of sensitive files (credentials, tokens, secrets) Body: #26084: Security Context-aware handling of sensitive files (credentials, tokens, secrets) — overlapping scope around preventing secret leakage to the model

   If you believe this was flagged incorrectly, please let a maintainer know.
3. github-actions

   added

   needs:complianceThis means the issue will auto-close after 2 hours.This means the issue will auto-close after 2 hours.

   on Jun 13, 2026
4. MethodWhite

   changed the title [-]feat: secrets redaction at tool output boundary[/-] [+][FEATURE]: secrets redaction at tool output boundary[/+] on Jun 13, 2026
5. github-actions

   removed

   needs:complianceThis means the issue will auto-close after 2 hours.This means the issue will auto-close after 2 hours.

   on Jun 13, 2026
6. github-actions commented on Jun 13, 2026

   

   github-actionsBot

   on Jun 13, 2026 – with GitHub Actions

   Contributor

   More actions

   Thanks for updating the issue! It now meets the contributing guidelines — the title prefix, verification checkbox, and description are all in order. Removing the compliance flag.
7. MethodWhite

   closed this as not plannedon Jun 13, 2026
8. MethodWhite commented on Jun 13, 2026

   

   MethodWhite

   on Jun 13, 2026

   Author

   More actions

   Closing as duplicate of #19425. Left a design spec at https://github.com/MethodWhite/opencode/blob/spec-secrets-redaction/specs/secrets-redaction.md that may be useful for implementation.