Describe the workflow pain
“Add a tool” is less actionable than explaining which repetitive task you want to shorten.
🔒 Browser-side processing
Bug reports, feature requests, and usage feedback are easiest to review when they come through a public, trackable channel.
Do not include sensitive personal data, passwords, API keys, or production tokens in a public report.
Channels
If the issue tracker is unavailable, a public note through the repository or blog route is still better than a vague report with no reproduction details.
Bug Reports
Requests
“Add a tool” is less actionable than explaining which repetitive task you want to shorten.
Concrete examples help determine scope and implementation feasibility much faster.
It helps to know whether the feature can stay client-side or would depend on an external API.
Issues in frequently used tools, confusing security copy, and mobile layout problems are reviewed first.