Feedback and Suggestions

These two things have different entry points, and the difference is worth spelling out:

• Report a problem lives in the ⋯ menu of each session ("Report a Problem") and is submitted together with the current session.

• Submitting an idea (suggestion) has no entry point in the window — not a deeply hidden one, there genuinely isn't one. To submit an idea, tell Klaus directly and it files it for you (files can be attached).

• Feedback collects context automatically, so you don't have to paste it yourself: the session id, that session's working directory, the path to the full conversation record file (included only if it exists), the git branch/HEAD of that directory and whether it has uncommitted changes, plus the system, machine model and app version. Feedback must be attached to a session; with no session there is nothing to submit.

• A suggestion can attach up to 8 files totaling no more than 20 MB; picking the same file more than once counts once. A description over 80,000 characters is truncated, with a note at the end stating how much was cut.

• Written to disk first, then uploaded: whether or not the send succeeds, the report is written out as a JSON file first — feedback goes to ~/.klaus/feedback/fb_*.json, suggestions to ~/.klaus/suggestions/sg_*.json. So a failed submission loses no content: you can open that file yourself to read or forward it.

• Signed out means stored locally only, never sent: uploading requires the desktop app's login token. While signed out the interface tells you to sign in to your Klaus account before submitting to the support team, and the submission result records that it was skipped for being signed out rather than pretending to succeed. To actually reach the Klaus team, sign in on the account page first.

• This is an outward-facing action, so when you have Klaus submit on your behalf, it shows you the content it is about to send and waits for your approval.