Do not open a public issue containing exploit details. Use a private GitHub security advisory. If that channel is unavailable, email hello@openminion.com with the subject “Desktop security report”. Do not include API keys or other credentials.
Include the affected Desktop and OpenMinion revisions, reproduction steps, expected impact, and whether the issue crosses the renderer, preload, Electron main, native capture, attachment, packaging, or daemon boundary.
OpenMinion Desktop follows these rules:
- report vulnerabilities privately first,
- do not publish proof-of-exploit details before maintainers can assess and respond,
- identify the affected process and permission boundary, and
- distinguish package-owned behavior from operating-system, daemon, provider, or deployment-specific behavior.
The OpenMinion daemon owns agent execution, sessions, policy, credentials, and durable state. Electron main owns operating-system access and authenticated daemon communication. Preload exposes a narrow fixed-purpose bridge. The renderer is untrusted and sandboxed.
Captured media, attachment bytes, daemon credentials, native paths, raw tool arguments, and tool results must not be exposed to the renderer unless a reviewed contract explicitly requires and bounds that data.
Process isolation is separate from protection of saved files. Desktop's SQLite database, OpenMinion profile JSON and previous-config backup are not encrypted by Desktop. Saved profile credentials remain in the config; draft text and transcripts may also contain sensitive information. Protect these files and backups with your operating system's access and disk-protection controls.
A local daemon can call configured model providers and external tools. Managed installation and runtime update checks also use the network. See Privacy and Connections for these boundaries and Desktop Data for storage and backup scope. Logs and exported transcripts must be reviewed before being attached to a report.
Call out whether an issue depends on a specific OpenMinion revision, Electron version, macOS permission, provider, or host configuration. That distinction helps identify whether the issue belongs to Desktop, OpenMinion, the operating system, or an external integration.