---
title: "Share feedback"
description: "Report a problem or tell the HyperFrames team what would make the product better."
---

Useful feedback explains the outcome you wanted and what stopped you from reaching it.

## Send feedback from the command line

From a HyperFrames project, run:

```bash
npx hyperframes feedback --rating 7 --comment "The render finished, but the captions were missing."
```

The rating is from 0 to 10. The comment is optional, but a specific example is usually more useful than a score alone.

## Report a reproducible bug

Use `--file-issue` when the project can be shared publicly:

```bash
npx hyperframes feedback \
  --rating 3 \
  --comment "The timeline freezes when this GSAP scene is opened." \
  --file-issue
```

<Warning>
  This flow asks for confirmation before uploading the selected project directory to a public URL.
  It is not a privacy scrubber and may include most of that project. The safest approach is to copy
  only the files needed to reproduce the bug into a separate clean folder, inspect it, then pass
  that folder with `--dir`. Never publish private media, customer data, credentials, or secrets.
</Warning>

HyperFrames then opens a prepared GitHub issue in your browser. Review it before submitting; the issue is not posted automatically.

You can also [open a GitHub issue directly](https://github.com/heygen-com/hyperframes/issues).

## Include enough evidence

A useful report includes:

- what you were trying to make;
- the action or command you used;
- what you expected;
- what happened instead;
- the exact error message;
- whether it happens every time;
- a screenshot or short recording for a visual problem;
- a small project when it is safe to share.

Do not include API keys, access tokens, credentials, private media, or customer information.

## About feedback data

HyperFrames may occasionally show a short rating prompt after a render or during a Studio session. You can ignore or dismiss it.

Feedback can include the rating, an optional comment, and basic environment information used to understand the problem. It does not include your composition HTML, video files, project names, file paths, or environment-variable values.

To turn off CLI telemetry:

```bash
npx hyperframes telemetry disable
```

That also stops the feedback prompt and takes the install out of any
[canary rollout](/contributing/canary-rollouts) — nothing that reports nothing
is ever picked for a staged release.

Studio feedback is controlled separately from the CLI setting.

## Related topics

- [Get unstuck](/help)
- [Diagnose common project and render problems](/guides/troubleshooting)
- [Search or open a GitHub issue](https://github.com/heygen-com/hyperframes/issues)
