Astra automatically captures bug reports, UX friction, and feature frustration the moment you mention them in chat <!--fact:f_complaint_capture_chip_v1-->. A small passive chip appears under the chat turn where the capture happened, confirming the complaint was logged. The morning operating brief then surfaces what was captured overnight with counts, topic breakdowns, and links to the relevant triage tasks <!--fact:f_operating_brief_complaints_v1-->.
When a complaint is captured
Astra listens for specific signals in your conversation: bug mentions, feature frustration ("still can't do X"), usage friction ("this happens every time"), or explicit complaints. When she detects one, she silently logs it and shows a confirmation chip under the chat turn where the capture happened <!--fact:f_complaint_capture_chip_v1-->. The chip requires no action — it is a passive marker that confirms the capture happened.
The capture fires before any optional notification, so the chip appears even if a downstream webhook is unavailable. The complaint row is written the moment the detection triggers.
What the chip looks like
The complaint capture chip is a small, muted indicator that appears under the assistant message where the capture occurred. It shows a brief label confirming a complaint was logged. It is not a link and does not require any action from you — its purpose is visibility alone.
Reviewing captured complaints
Each morning, the operating brief includes an auto-support section that summarizes complaints captured in the previous 24 hours <!--fact:f_operating_brief_complaints_v1-->. It shows the total count, a breakdown by topic (bug, feature request, or UX issue), and a link to the most recent triage task. This gives you a single place to see what the team has flagged overnight without checking individual chat logs.
For deeper inspection, complaint data is surfaced in the task system and can be queried by support agents during triage.
See also operating-brief for how the morning brief works.