Filing a bug
Golden Retriever ships with a built-in bug report form. Reports are sent directly to our triage inbox — no account or email required. Read on for what’s captured, what’s optional, and how to keep sensitive content off the wire.
Opening the report sheet
Section titled “Opening the report sheet”There are two ways to start a report:
- Menu bar → Help → Report a bug…
- Keyboard shortcut:
⌘⇧?
No persistent button lives in the UI — the Help menu is the discoverable entry point.
Filling out the form
Section titled “Filling out the form”| Field | Required | Notes |
|---|---|---|
| What happened? | Yes | Plain-language description of the problem. No character limit. |
| Can you still use the app? | Yes | Pick the impact level: minor annoyance, has workaround, or blocking. |
| Area | Yes | Rough category so we route it to the right track. |
| No | Only needed if you want us to follow up. | |
| Video or screenshot | No | Attach a file up to 200MB, or paste an external link (Loom, Drive, etc.). |
Attaching a video
Section titled “Attaching a video”Click Choose file… to pick any video or screenshot from disk — up to 200MB. If the recording lives somewhere else (Loom, Google Drive, Dropbox), paste the share link into Or paste a video link instead of uploading.
What diagnostic info gets sent
Section titled “What diagnostic info gets sent”Golden Retriever automatically captures a few pieces of context so we can reproduce issues without a lot of back-and-forth. Open the Diagnostic info being sent section to see exactly what’s included — everything is inspectable before you hit Send.
Always included
Section titled “Always included”- App version — e.g.
0.9.1 (20260417142843) - macOS version — e.g.
26.3.1
Opt-out toggles (included by default, you can uncheck)
Section titled “Opt-out toggles (included by default, you can uncheck)”- Source view — the screen you were on when you opened the report (e.g. “search”)
- Navigation history — the last ten screens and in-app actions (filter pills, searches, AI questions, settings tabs, library additions). Only event names are captured; query text and file paths stay out.
- Sentry event ID — if a crash or error happened earlier in the session, the ID of that event so we can correlate it with your report
- Log tail — the most recent 100 entries from Golden Retriever’s internal audit log (ingestion events, auth state changes, etc.)
Opt-in (off by default)
Section titled “Opt-in (off by default)”- Raw view state — if you flip this on, we also include the timestamp and section name captured at sheet-open time. We ship a second batch labeled “may contain query text or file paths” for future screens that need deeper context — right now it’s minimal, but leaving it off keeps your search queries and personal data out even if we expand later.
Privacy
Section titled “Privacy”Golden Retriever is local-first and bring-your-own-cloud. The feedback flow is held to the same standard:
- We don’t capture your knowledge base content. File paths, document text, search queries, and AI answers never leave your device unless you explicitly opt in via the raw state toggle.
- You see exactly what’s being sent before hitting Send. Every toggle is visible.
- Email is optional. Submit anonymously if you prefer.
- Videos live on our storage for triage purposes and are only accessible to Golden Retriever’s maintainers via short-lived presigned URLs.
- Full privacy details are in the Privacy Policy.
What happens after you hit Send
Section titled “What happens after you hit Send”You’ll see a brief “Thanks, we got it 👍” confirmation. Click Done to close the sheet.
Reports land in our internal triage dashboard. If you left an email, expect a reply within a few business days — no automated acknowledgement, but a real person reads every submission during beta.
If submission fails
Section titled “If submission fails”If the network is flaky or the server rejects the report, you’ll see an inline error plus two options:
- Retry — simply press Send again
- Copy report to clipboard — copies the description plus diagnostic summary so you can paste it into an email, Slack, or a GitHub issue as a fallback