Steps to reproduce
Describe what you opened, what you clicked or typed, and what happened next. Include the smallest sequence that causes the issue consistently.
Have questions, feedback, or suggestions? We'd love to hear from you! Reach out to us through any of the methods below.
Send a message directly from here for support, feedback, bug reports, or feature requests.
A clear report makes a technical problem easier to reproduce. Never send passwords, OAuth secrets, private repository content, session verification keys, or values from a .env file.
Describe what you opened, what you clicked or typed, and what happened next. Include the smallest sequence that causes the issue consistently.
Share the browser name, device type, and whether you were using the normal frontend workspace, collaboration, GitHub, publishing, or Node.js mode.
Copy the exact safe error message and line number. A screenshot can help, but remove personal information, repository secrets, and private chat before attaching it.
Use Support for a feature that is available but not behaving as documented. Check the complete help guide first; it covers files, previews, GitHub, Node.js, publishing, and collaboration.
Choose Bug Report when the same action produces an error or broken interface repeatedly. A focused sample project is more useful than a large unrelated project.
Explain the task you are trying to finish, who it helps, and how you expect the workflow to behave. That context is more actionable than only naming a button.
Read the privacy and data guide, then contact us if you need clarification about browser storage, connected services, cookies, publishing, or collaboration data.
mailto: action. If no email application opens, send the same details directly to support@codxeditor.com.