Most bug reports never get written. Something misbehaves, you are mid-task, and writing it up properly means gathering versions and error messages you do not have to hand. So the problem goes unreported and stays unfixed for you and everyone else.
/feedback (new in v1.82.0) removes the homework. Say "report this" when something goes wrong, and Dex investigates on your machine, writes the report itself, shows it to you, and sends it with a reference number. When the fix ships, your next session opens with the good news and which version has it.
What a report contains, and what it never contains
A report is built from a fixed list of ingredients, and this is the whole list:
- Which version of Dex you are running.
- Which feature misbehaved — the command or automation name, nothing more.
- What happened and what you expected instead, described as Dex mechanics.
- Error text from Dex's own workings, including the file paths inside Dex's code.
- A few facts about the machine: your operating system, which app you run Dex in, and whether each connected tool is working, off, or broken. Never the settings themselves — that a calendar is connected, never which calendar.
- What Dex found when it looked into the problem, expressed as counts and mechanisms. "Checked five lines in the daily plan, none carried a task reference" — never the five lines.
- Anything you type yourself, if you choose to add a note.
Your notes, meetings, people, tasks, and the conversation you were having are never a source. Dex does not read the transcript to write a report. Paths to your own files are described by their role — "a person page under the People folder" — rather than named.
Three things make that checkable rather than a promise you have to take on faith:
- The list is enforced in the code, not just in Dex's instructions. The program that does the sending refuses to send anything outside the list above, and the receiving end refuses it a second time. There is no setting that widens it. What goes inside those entries — the wording of what happened, the counts Dex found — is written by Dex under the rules above, which is why the next point matters.
- You see the exact words before they go. Every report is shown to you in full, and you can edit any part of it. If you later choose to let Dex send routine reports without stopping to ask, you can switch that back at any time, and the first report is always shown regardless.
- You keep a copy of everything. Every send attempt, whether it succeeded or not, is written to
System/.dex/feedback-log.jsonlon your machine, and each report keeps its own file underSystem/.dex/feedback/. Ask Dex to show you the log and you can read precisely what left your computer, and when.
Reporting something
When Dex misbehaves, say so in the moment:
That went wrong. Report it with /feedback — show me the report before it goes.
Dex investigates, drafts the report, and shows it to you. Approve it and you get a reference like DEX-142. The Doctor checkup (/dex-doctor) offers the same thing when it finds something that is genuinely a Dex problem rather than a setup problem on your machine.
By default you review every report before it goes. Once you have seen a few and trust what they contain, you can tell Dex to send future ones automatically; you can switch back any time by asking.
The first report asks you to connect, once
Sending feedback requires signing in, by design, so that fixes can find their way back to the person who reported the problem. The first report walks you through it: a page opens at heydex.ai, you sign in, create a short code, and paste it into the terminal. It takes about thirty seconds and never needs doing again. It is the same connection the DexDiff publishing flow uses, so if you already publish diffs you are already connected.
Hearing back
You do not need to chase anything. When a release fixes your bug, your next session opens with a note: which report, which version has the fix, and any comment from the team. Run /dex-update when you are ready and you have it.
To check in the meantime:
What's the status of my feedback reports?
That shows every report this account has filed, with its current state: received, being looked at, fixed in a version, or waiting on an answer from you.
When the team needs to ask you something
Sometimes one detail is missing and the fix stalls without it. Rather than emailing you a list of things to go and check, the team can leave a question on your report, and your Dex — which is already sitting on the machine where the problem happened — can go and find the answer.
This is the part people most want to understand before they rely on it, so here is exactly how it works.
Nothing reaches into your machine. Your Dex asks; it is never told. Once a day at the start of a session, if you have filed a report, Dex asks heydex.ai whether there is any news on it. The answer that comes back can only be a status, a comment, or a question — words on a screen. It cannot instruct Dex to do anything, and it carries no access to your vault. If you never file a report, this never runs at all.
A question can only be about a report you filed. There is no way for anyone to ask your Dex a general question about your work, your calendar, or your files. Questions attach to a ticket you opened, about a fault you chose to report.
The answer carries the conclusion, not the evidence. Answers follow the same fixed list as reports: findings as counts and mechanisms, error text from Dex's own workings, never the underlying content. "Three duplicate entries, all created by the meeting sync, earliest on 2 July" is an answer. The three entries themselves are not — not their titles, not who was in them, not what they were worth.
You see every answer, and nothing goes without your yes. Answering means Dex looked inside your vault on someone else's prompt, so the draft is always shown to you in full and always waits for your approval — including for people who have chosen to let routine reports send automatically. That setting does not apply here. Decline and the question simply sits there; it never nags, and the report stays open.
And as with reports, every answer is recorded in the log on your machine — whether it sent or not — so there is a permanent record of what went out on your behalf.
If something looks off
Every send attempt, successful or not, is recorded in System/.dex/feedback-log.jsonl, and each report keeps its own file under System/.dex/feedback/. If a send fails, Dex says so plainly rather than pretending it went; try again later or ask Dex to show you the log.