Using the workspace

Feedback for Duscode

Problems Dus runs into in Duscode itself are listed on your computer. Turn on sending, see each report before it goes, and hear "Fixed in version X" when a release fixes it.

When Dus runs into a problem in Duscode itself (a sandbox limit, a tool that misbehaves, a confusing error message, a capability it needed and didn't have), it notes it once and lists it in Settings → About & updates → Feedback for Duscode. The same problem again counts up instead of repeating.

The list stays on your computer. Sending it to Duscode is your choice, and it is off until you turn it on.

Sending problems to Duscode

1. Open Settings → About & updates and turn on Send problems to Duscode.
2. Next to a problem, choose Review and send. You see exactly what will be sent:
   • the problem in one sentence and the error lines that show it;
   • the Duscode version and your system (for example "linux x64");
   • an error signature: a short code made from the kind of problem and its error line, so the same problem from different computers is counted once. It says nothing readable about your project;
   • who it is from: your Duscode account when you are signed in, otherwise an anonymous install id (a random code kept on this computer, never your name or email).
3. Choose Send to Duscode.

What is never sent unless you choose it, for that one report:

• The longer output. Tick Include this excerpt to send it, masked.
• Your project's name. Tick Include the project's name to send it. Otherwise it is replaced by "<project>", and every folder path by "<path>".

What is never sent at all: your code, file contents, prompts, keys and secrets. Secrets are masked before the preview is built: values in your vault, API keys and tokens in known formats, passwords in connection strings and secret-looking assignments.

After the first send, if the same problem happens again, Duscode sends the new count with the same choices, without asking again.

Hearing that it is fixed

The people who build Duscode see reports grouped by problem, ranked by how many installs hit them. When a release fixes one, your app hears about it on its next check (at start and every few hours): the problem is marked Fixed in version X in the list, and the bell says so.

Signed in, you can also get an email: turn on "problem fixed" emails in Settings → Notifications (they are off until you choose them).

Privacy mode turns it off

When privacy mode is Local models only (Settings → Models & keys → Allowed providers), nothing leaves your computer, problem reports included: the switch is greyed out and says why. An organisation can also block reports in the config file with "privacy": { "feedbackReports": false }; a project's config can block them but never allow them.

In Duscode's own repository

If you build Duscode itself, Dus reads the list in that repository by itself, and Platform admins also see the triaged problems from everyone (the duscode_feedback tool). A fix is linked to its problem with a commit trailer, Fixes-Duscode-Issue: <id>; the release picks the trailers up and tells the reporters.