# Contact plainkit.tools

> How to report a bug, request a feature, or ask a question about plainkit.tools.

The project is maintained in the open, so the fastest way to reach a human is the public issue tracker. Bug reports and feature requests filed there are read alongside the code they concern, and anyone else hitting the same problem can follow along.


[Open an issue on GitHub](https://github.com/nomanyaqub/gpt-text-cleaner/issues)

## Report a bug or request a feature

Open an issue on the GitHub repository with what you pasted (or a minimal example that shows the same problem), what you expected, and what you got. Invisible-character bugs are easiest to fix when the report includes the exact characters involved, so pasting the problem text itself is more useful than describing it. Issues are triaged in the open; there is no private support queue jumping ahead of them.

## Ask a question

Questions about cleaning behavior, the detypo engine, or the command line tool are welcome on the tracker as well. Before asking, the FAQ on the homepage and the blog guides on zero-width spaces, curly quotes in code, and AI watermarking already answer the most common ones. A question that reveals a gap in those pages usually ends with the pages improved, so asking in public helps the next person too.

## What not to send

There is no email support channel and no account system, so there is nothing to recover and no inbox to write to. Do not post passwords, private documents, or anything you would not want public on the tracker; the cleaner itself needs none of that, since it runs entirely in the browser and nothing pasted into it is transmitted anywhere.