NATS Studio is maintained by Himanshu Chavda. Here is where each kind of message should go, so it reaches the right place and gets an answer.
Open an issue on GitHub: github.com/himanshu-systems/nats-studio/issues. This is the fastest route and the preferred one, because the discussion stays public where other users can find it, add detail, and confirm whether they hit the same thing.
For a bug report, the most useful details are: your operating system and NATS Studio version (shown at the bottom of the sidebar), the NATS server version you connected to, what you expected to happen, and what happened instead. If the app showed an error message, paste the exact text.
Please do not open a public issue for a security vulnerability. Report it privately through GitHub's Report a vulnerability form, or by email to himanshu.tech.profile@gmail.com.
You will get an acknowledgement as soon as possible, and the fix and disclosure will be coordinated with you. The full policy is published in SECURITY.md.
Email himanshu.tech.profile@gmail.com, or reach out on LinkedIn. Questions about whether NATS Studio fits a particular workflow are welcome — so is feedback that it does not.
NATS Studio is a free, MIT-licensed open-source project maintained by one person, not a company with a support desk. There is no paid support tier and no response-time guarantee, but genuine questions do get answered.
Pull requests are welcome. The contribution guide, including how to build from source and what the review process looks like, is in CONTRIBUTING.md. If you are planning a substantial change, opening an issue first to discuss the approach will save you rework.