Security fixes target the latest release and the main branch.

Do not open a public issue for a vulnerability involving credential files, clipboard contents, arbitrary process execution, named-pipe authorization, worker permissions, or provider session data. Use GitHub's Report a vulnerability flow under the Security tab.

Include the affected version, Windows version, reproduction steps, privilege level, configured profile or worker provider, and practical impact.

• TerminalApp launches commands explicitly configured by the local user. It is not a sandbox for interactive terminal sessions.
• Worker jobs are separately governed by broker permission policy, timeout, depth, isolation, and provider availability.
• Provider CLIs own authentication. TerminalApp does not store their API keys, but the optional usage panel reads and may refresh their existing OAuth credentials.
• Broker control uses a current-user/SYSTEM ACL on SID-scoped Windows named pipes and a per-user singleton.
• Clipboard and dropped-file paths are local OS resources and should be treated as sensitive.

TerminalApp has no telemetry or cloud synchronization.