Support and security
Useful context.
No sensitive payloads.
Use the public support route for installation, release-authority, website and security questions. The MCP itself does not accept support messages.
01 / Contact
One route for public support.
Email support@codex-cortex.com for general support. Use a clear subject such as “Plugin installation”, “Release authority”, “Website” or “Marketplace review”.
02 / What to include
Send enough evidence to reproduce the issue.
- The affected surface: website, public MCP, plugin or local Cortex tooling
- Relevant version, authority epoch, release ID or public artifact URL
- What you expected and what happened instead
- Minimal reproduction steps and approximate timestamp
- Sanitized error class or response status, if available
- Your operating system and Codex host when the issue is local
Prefer public identifiers and a minimal reproduction over full logs or project material.
03 / Security reporting
Mark security reports clearly.
Send security concerns to support@codex-cortex.com with “Security” at the start of the subject. Include the affected URL or version, impact, reproducible steps and whether the issue is already public.
04 / Sensitive information
Do not send secrets or repository contents.
Never email credentials, API tokens, signing keys, private keys, access links, customer data or proprietary repository contents.
If sensitive project context is genuinely required, wait until Codex Cortex provides and explicitly authorizes an approved future mechanism. Ordinary email and the public MCP are not that mechanism.
Redact paths, identifiers and logs where they are not necessary to reproduce the problem.