Skip to main content

Feedback and privacy

AI responses can offer Style feedback and Report this reply. Style feedback is written to profile data on the current device to shape later response style. A report uses a separate sending workflow tied to the signed-in account. Their destinations and workflows are different.

Style feedback​

Choose one or more style tags and optionally add a note. Submitting stores locally:

  • the current conversation ID and message ID;
  • selected tags;
  • your note; and
  • up to the first 500 characters of the response.

Use it for issues such as excessive length, insufficient detail, or an unsuitable tone. It does not enter the Report this reply delivery queue. Later style adjustment gives the model a summary of the selected labels, not the complete saved response excerpt. Do not place credentials, wallet recovery information, or unrelated personal data in the note.

Report this reply​

Open More actions → Report this reply on an AI response. Reports are tied to the signed-in account, so sign-in is required.

  1. Select a problem category.
  2. Optionally describe what you expected.
  3. Review Include conversation content, which is on by default. Turn it off if the report should exclude replies, surrounding turns, and Tool content.
  4. Read the What will be sent preview.
  5. Select Send report.

Include conversation content is on by default. With it off, conversation text is omitted, but the category, note, run statistics, and context fields listed in the preview are still sent. When it remains on, the report includes the current response, surrounding turns, and excerpts from related Tool arguments, outputs, or errors. These can contain commands, file paths, read results, and service responses. What will be sent extracts message text and Tool names; it does not enumerate those Tool inputs and outputs, so it is not a complete payload preview. Turn Include conversation content off before sending if you do not want them included.

Preview and redaction​

The preview lists estimated size, context fields, message excerpts, and Tool counts. It states that recognized API keys, tokens, and other credential patterns are replaced with [REDACTED] before leaving the device. Pattern detection is not a reason to include secrets: review every field and remove unnecessary content or notes.

Offline delivery​

When the network is unavailable, Ghast may show Saved for delivery. The report is in a local delivery queue rather than delivered and may retry after connectivity returns.

Closing the dialog does not submit it. If preview creation fails, the dialog states that nothing has been sent.