Support

Support and security reporting

Prepare useful diagnostics without publishing private data or assuming an unavailable contact is monitored.

Pre-release. Reviewed November 3, 2026. This review covers code behavior, not a packaged release or provider certification.

Pre-release support availability

No public support SLA is promised. Write to hello@commandem.ai for help or feedback, privacy@commandem.ai for privacy questions, and security@commandem.ai for vulnerabilities. Do not put vulnerability details in a public thread.

Prepare a bounded reproduction

  1. Record commandem version, app build, OS and timestamp.
  2. Describe the action, expected result, observed result and whether a retry changed it.
  3. Include a content-free error or a redacted fictional reproduction. Preserve original receipts locally.
  4. Never attach raw environments, credential files, private account labels or complete real transcripts.

Report a suspected vulnerability privately

Email security@commandem.ai, or use Report a vulnerability on the repository Security tab when it is enabled. Do not disclose the vulnerability publicly.

Remove data deliberately

  1. Inventory projects, history, receipts and notes you need to keep. Back up required local state first.
  2. Removing the app bundle does not remove Commandem's local state or provider-owned credentials/history.
  3. Inspect the specific application's data directory and the provider's controls. Delete only confirmed targets; there is no recommended blanket cleanup command.
  4. Local deletion does not remove copies sent to providers or sync destinations. Use each service's verified deletion process.

See Privacy, Security and troubleshooting. This is operational guidance, not a legal-compliance certification.