---
title: "Contact Helicon: email, issues and security"
url: https://helicon.sh/contact
description: "How to reach the person who maintains Helicon: email for anything private, GitHub issues for bugs and features, and a private advisory channel for security reports."
updated: 2026-09-19
site: Helicon
---

# Contact

Email me@harjotrana.com for anything private, licensing or press related. Open a GitHub issue for bugs and feature requests, because those get fixed in public. Report security problems through a private GitHub Security Advisory rather than an issue. Helicon is maintained by one person in New Delhi, India.

Helicon is maintained by one person, so the right channel matters more than it would at a company: the wrong one adds days, and the right one usually gets an answer the same week. Pick by what you are sending, not by what feels most formal.

## Which channel to use

| If you want to | Use | Typical response |
| --- | --- | --- |
| Report a bug, or ask for a feature | [GitHub issues](https://github.com/HarjjotSinghh/helicon/issues) | A few days. Public, searchable, and it is where fixes get tracked |
| Report a security problem | [Private security advisory](https://github.com/HarjjotSinghh/helicon/security/advisories/new) | Acknowledged within 72 hours, then coordinated disclosure |
| Ask something private, licensing, press or partnership | [me@harjotrana.com](mailto:me@harjotrana.com) | A few days |
| Ask how something works | [The FAQ](https://helicon.sh/faq) and [the guides](https://helicon.sh/guides) | Immediate, and already written down |
| Integrate with Helicon as a program | [The developer documentation](https://helicon.sh/developers) | Immediate. The API is public at https://helicon.sh/api/v1 |

## Email

[me@harjotrana.com](mailto:me@harjotrana.com) reaches the maintainer directly. It is the right address for anything that should not be public: licensing questions, press enquiries, trademark or takedown notices, and anything commercial. It is the wrong address for a bug, because a bug in an email helps exactly one person, and the same bug in an issue helps everyone who searches for it later.

## Reporting a bug well

Two lines of detail usually decide whether a bug is fixed this week or next month. Include these:

1. Your operating system and version, and whether Muse Code is running natively or inside WSL2.
2. The Helicon version, from Settings, and the output of `muse --version`.
3. What you did, what you expected, and what happened instead.
4. Whether approval modes were involved, and which one.

## Security

> Do not open a public issue for credential handling, authentication bypass, sandbox escape or WSL command injection. Use the [private advisory form](https://github.com/HarjjotSinghh/helicon/security/advisories/new) instead. Reports are acknowledged within 72 hours and disclosed in coordination with you.

## Who you are writing to

| Field | Value |
| --- | --- |
| Maintainer | [Harjot Singh Rana](https://harjotrana.com) |
| Email | [me@harjotrana.com](mailto:me@harjotrana.com) |
| Location | New Delhi, Delhi, India |
| Project | [https://github.com/HarjjotSinghh/helicon](https://github.com/HarjjotSinghh/helicon) |
| Issues | [https://github.com/HarjjotSinghh/helicon/issues](https://github.com/HarjjotSinghh/helicon/issues) |
| More | [About Helicon](https://helicon.sh/about) |

There is no phone line and no support desk. Helicon is free, MIT licensed software with one maintainer, and the honest expectation is best effort rather than a service level agreement. Anything reproducible, filed as an issue, is the fastest path to a fix.

## Frequently asked questions

### How do I report a Helicon bug?

Open an issue at https://github.com/HarjjotSinghh/helicon/issues with your operating system, your Helicon version, the output of muse --version, and the steps that reproduce it. Public issues are fixed faster than emails because they are tracked and searchable.

### Where do I report a security vulnerability in Helicon?

Through a private GitHub Security Advisory at https://github.com/HarjjotSinghh/helicon/security/advisories/new, never a public issue. Reports are acknowledged within 72 hours and disclosed in coordination with the reporter.

### Is there commercial support for Helicon?

No. Helicon is free, MIT licensed and maintained by one person on a best effort basis. For licensing or commercial questions, email me@harjotrana.com.

## Related

- [About](https://helicon.sh/about): Who builds Helicon, why a Muse Code desktop app exists at all, how it is funded, and what it deliberately is not. One maintainer, MIT licensed, no company behind it.
- [Developers](https://helicon.sh/developers): The public JSON API for Helicon: releases, downloads, documentation and search. No key, no account, read only, with an OpenAPI description and structured JSON errors.
- [Legal](https://helicon.sh/legal): Everything in one place: the MIT licence, what Helicon collects, the terms, the security policy, and the trademark position on Muse and Muse Code.
- [Privacy](https://helicon.sh/privacy): The Helicon desktop app has no account and no telemetry. It checks for updates and nothing else. This site uses analytics. Here is exactly what each one records.

---

Helicon is a free, MIT licensed, unofficial community client for Meta's Muse Code CLI. Not made, sponsored or endorsed by Meta. Source: https://helicon.sh/. Machine readable index: https://helicon.sh/llms.txt