Please do not open a public issue for security vulnerabilities.

Report privately through GitHub's private vulnerability reporting:

https://github.com/PerryLink/dsh-background-agents/security/advisories/new

That flow keeps the report confidential while we triage, and it is the channel we watch first.

• Redact sensitive data from any logs, session excerpts, or config files you attach: tokens, API keys, secrets, Authorization/request headers, personal paths, and account identifiers. Trimmed session excerpts are usually enough.
• Include, when possible: the plugin version, the harness (dsh) version, Node and OS versions, and the minimal steps to reproduce.

• Acknowledgment: within 5 business days.
• Triage: within 10 business days we confirm the issue and assess severity, or ask for more details.
• Fix: security fixes are prepared in a private fork, released as a patch version, and announced in the release notes.

• We follow coordinated disclosure: a public advisory (and CVE request where appropriate) is published once a fix ships.
• Reporters are credited in the advisory unless they ask to remain anonymous. There is no bug bounty program at this time.

This plugin builds on the official subagent seam inside the harness: child agents run in their own sessions and inherit the session's LLM route. The plugin itself makes no direct network requests and never changes OS-level sandbox policy. Vulnerabilities in the harness itself should be reported to the official harness maintainers instead.