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

Good to know: dina feedback bug works even when you're not signed in — on purpose, so you can report a broken sign-in flow.

Report a bug

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:

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:

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

Or pipe it directly from stdin:

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

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.

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

General feedback

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”.

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

If a submission doesn’t go through

If the CLI can’t reach the platform when you submit — you’re offline, or the service is briefly unavailable — your feedback isn’t lost. It’s saved locally and queued for retry, and the command tells you so. The next time you run:

dina doctor --fix

the CLI resends anything waiting in the queue. dina doctor (without --fix) shows you how many items are pending.

To discard the queue without sending it — say you’ve decided a report isn’t worth filing — clear it:

dina feedback queue clear

The CLI confirms before deleting; pass --force to skip the prompt.

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 instead. That’s where we track work and where you’ll see the fix land.