Include enough to reproduce it
- Browser name and full version.
- Operating system and version.
- Clipplane extension version and, if detected, Host version.
- Capture mode: Selection, Page, or Element.
- Exact steps from opening the page to the failure.
- What you expected and what visibly happened.
- Whether Clipplane confirmed a local copy before any sync error.
Use a public test page when possible. If the problem happens only on a private page, describe its general structure instead of sharing its contents.
Never post these
Crop screenshots to the relevant control. Replace private titles, URLs, folder names, and workspace names with neutral placeholders before uploading.
Share diagnostics safely
Source testers may run npm run doctor. Read the output before posting it. Keep version, registration state, and pass/fail lines, but remove user names, home-directory paths, notes paths, and any configuration detail that could identify a private destination.
Do not paste raw operating-system credential-store output. Clipplane diagnostics are not supposed to print credential values; if you ever see one, stop and report only that a secret was exposed.
Security-sensitive reports
Do not demonstrate a security issue with a real credential or private document. Open a minimal issue asking for a private coordination channel, with no exploit details or sensitive data in the title or body.
For ordinary bugs and setup failures, use the public issue tracker. There is no separate email support desk or paid support tier.