Get unstuck fast.
Most answers are in the docs. If not, we're a short email away.
Documentation
Setup, every setting and every safeguard, plus a troubleshooting table.
Read the docs →Writrex Lite users
Ask questions and get help from the community and the team on GitHub Discussions.
Open GitHub Discussions →Paid licence holders
Every paid licence includes email support. Write to hello@writrex.com and we reply within 24 hours, Monday to Friday.
Bugs, technical issues and security reports
Report bugs, ask technical questions and raise security concerns on our public GitHub Discussions board. Search first: your question may already be answered.
- Bug reports and technical questions: open a new discussion at github.com/writrex/writrex-plugin/discussions.
- Security concerns: do not post exploit details, licence keys or API keys publicly. Start a discussion describing the area affected, or email hello@writrex.com for a private report.
What to include
- Your Writrex plan and plugin version, and your WordPress and PHP versions.
- What you were doing, what you expected, and what happened instead.
- The AI provider and model you were using.
- A screenshot of the message or the Pre-Publish Checklist, if relevant.
Diagnostics
If we ask for logs, enable Settings → Diagnostics → debug logging, reproduce the problem, and send us the entries from the Debug Log page. Turn diagnostics off again afterwards. Remove any API keys before sharing.