Send feedback

Found a bug or have an idea? In the beta it goes straight to Chris; on your own machine KPD turns it into a tidy Markdown file you attach to an email. Either way, nothing about your project is sent behind your back.

How it works

Open Help → Send feedback.
Choose Bug or Improvement, and fill in a summary and the details. For a bug you can add steps to reproduce, and what you expected versus what actually happened.
Click Create feedback file. KPD downloads a file named kpd-feedback-<date>.md (usually to your Downloads folder).
Email it to the address KPD shows you and attach the file — there's an Open email button that starts the message for you, so you just drag the file in and send.

In the beta

If you're using KPD through the beta website, Send feedback goes straight to Chris — no email step. Fill in the same form, click Send feedback, and you'll get a reference back like FB-0007 so it can be followed up. The beta already knows who you are, so name and email are optional.

If it can't be sent for any reason — your beta session has ended, or you're offline — KPD falls back to the Markdown file for you to email, exactly as below, so your feedback is never lost.

What's in the file

Your name and email (remembered for next time), the summary and details you typed, and a little context that makes a bug report useful: the KPD version, your browser and operating system, and whether a pipeline or the Domain map was open.

Private by designYour name and email are stored only in this browser. The file never contains your project's contents, schemas or any client data — only the version, your browser, and what you wrote. You can see exactly what's attached in the Attached automatically box before you create the file.

Questions?The feedback form is for bugs and ideas. For "how do I…" questions, the rest of this guide is the quickest answer — start with Quick start or the keyboard shortcuts.