Getting Help with Varity
Documentation
Section titled “Documentation”Check these first. Most questions are answered here:
- Quick Start: Get running in 5 minutes
- Troubleshooting: Common issues and fixes
- CLI Reference: Command-line tool guide
- MCP Server: Deploy from Claude Code or Cursor
Community
Section titled “Community”Our Discord is the fastest way to get help from the team and other developers.
Channels: #help for questions, #general for discussion, #showcase to share what you build.
Report Issues
Section titled “Report Issues”Found a bug or have a feature request? Reach out on GitHub or Discord.
When reporting bugs, include:
- Steps to reproduce
- Expected vs actual behavior
- OS, Node version, and package versions
- Error messages or logs
Security Issues
Section titled “Security Issues”Do not report security vulnerabilities publicly.
Email security@varity.so instead. We typically respond within 24 hours.
Feedback
Section titled “Feedback”We welcome bug reports, documentation improvements, and feature requests. The fastest way to reach us is Discord, or open an issue on GitHub.
Response Times
Section titled “Response Times”| Channel | Typical Response | Best For |
|---|---|---|
| Discord | Typically a couple of hours | Quick questions |
| GitHub Issues | Typically within a day | Bugs and feature requests |
| Typically within 24 hours | General inquiries |