# Send feedback

We read everything you send. Bug reports are especially helpful — they tell us exactly what broke, often with enough detail to fix it without another round trip.

You can send feedback from inside the CLI without opening a browser or filing a GitHub issue. Three flavours:

| Command | What it's for | Requires sign-in? |
|---|---|---|
| `dina feedback bug` | Something broke or behaved unexpectedly | No |
| `dina feedback feature` | You want the CLI to do something it doesn't | Yes |
| `dina feedback` | General thoughts, comments, a rating | Yes |

<div class="callout"><strong>Good to know:</strong> <code>dina feedback bug</code> works even when you're not signed in — on purpose, so you can report a broken sign-in flow.</div>

## Report a bug

```sh
dina feedback bug
```

The CLI opens a short interactive form: a title, a description, and a severity (`low`, `medium`, or `high`). Fill it in and submit.

Want to skip the form? Pass the fields as flags:

```sh
dina feedback bug \
  --title "deploy --wait hangs on failed builds" \
  --description "Expected exit 1 after 'build_failed'; the process stalled for 10 minutes" \
  --severity high
```

### Attaching logs or context

If you have a log file or a stack trace that helps explain the issue, attach it as **context**:

```sh
dina feedback bug --context-file ./build.log
```

Or pipe it directly from stdin:

```sh
dina apps logs --app my-app --lines 500 | dina feedback bug --context-file -
```

You can also paste context inline with `--context "..."` (useful for short snippets). You can use one or the other — not both.

### What we see

Every bug report automatically includes the version of the CLI you're running and the OS and architecture. That helps us reproduce problems faster. We don't send anything else from your machine.

## Request a feature

```sh
dina feedback feature
```

Same shape as a bug report, without the severity. Tell us what you want the CLI to do and, ideally, the workflow you're trying to accomplish.

```sh
dina feedback feature \
  --title "Allow env vars from .env files" \
  --description "Would love a --env-file flag on apps env set."
```

## General feedback

```sh
dina feedback
```

Open-ended: share a comment, a thought, or a 1-to-5 rating. Good for "this was delightful" or "this one flow could be smoother".

```sh
dina feedback --message "The new error messages are much clearer, thanks!" --rating 5
```

## When you need a conversation

If you need a back-and-forth — for a security issue, a production outage, or a complex bug — please [file a GitHub issue](https://github.com/dinacomputer/cli/issues) instead. That's where we track work and where you'll see the fix land.