Report a problem
Two fields, a short pile of automatic context, and a promise about what we never send.
Updated Aug 14, 20262 min readApplies to 1.1.5
Everything breaks, and early software breaks more. The faster we hear, the faster it is fixed.
Where it's
Help menu, Report a Problem. Or Settings, chapter 01 Account, the row REPORT A PROBLEM. Same sheet either way.
What it asks
Two fields.
- What happened? Required.
- What were you doing? Optional.
No category picker, no severity, no screenshot upload. Tell us what broke or froze or felt wrong, and what you were trying to do when it did.
What rides along automatically
| Sent with every report | Detail |
|---|---|
| App version and build | From the app bundle |
| Your macOS version and Mac model | For example, a Mac Studio on macOS 15.3 |
| Your plan tier | Solo Pro, Studio, Agency Plus, and so on |
| Your email | The one you sign in with |
| The active workspace name and id | So we know which archive you were in |
| A tail of your recent activity log | Capped, and scrubbed of anything key-shaped before it leaves your Mac |
| Four small facts | Your timezone, the timestamp, your locale, and the workspace name |
That last row is the whole of what we call the diagnostics blob. Four values. No memory reading, no disk reading, no hardware survey.
Crashes
If the app crashes, a breadcrumb gets written. Next launch you get a pre-filled crash report you can send with one tap. Same rules, no photos and no keys.
After you send
It writes into our bug tracker and emails Trent directly. He reads every one. If we can act immediately we do, and if we need more we reply to the email.
You can't attach a screenshot from the sheet. If one would help, reply to that email with it.
Was this helpful
Still stuck
Tell us what happened and we will usually answer the same day. If it is more of a question than a bug, ask the room. Every tester reads it, and you are already signed in.