Editorial contact
Use this address for inaccurate instructions, outdated sources, broken links, accessibility problems, or feedback about the publication. We are an independent guide, not the upstream plugin's support team. There is no contact form or upload feature on this website.
For a factual correction, include the page URL, the sentence or command concerned, and a primary source that supports the correction. If your report concerns a platform difference, give the host name, version, operating system, and integration method.
Keep reports useful and private
Do not send credentials, API keys, private repositories, customer information, or full production logs. Redact private paths and account details. A short nonprivate reproduction usually explains an installation problem more clearly than a large log archive.
Email is handled by the mail systems used to send and receive it. The message and reply address are used to understand and respond to your request; see the contact-data information. We do not promise a response time or ask for remote access to your coding environment.
For Ponytail product issues
Report reproducible problems in the software to the official Ponytail issue tracker, following the project's own reporting guidance. Use the relevant host's official support route for account, billing, login, or host-platform issues.
If you are unsure whether the problem is setup or task behavior, start with the troubleshooting table. It helps separate missing commands, hook loading, configuration precedence, and an implementation that does not meet your requirements.
Maintained by the Ponytail Guide editorial team. Found an outdated command or a factual error? Send a correction. Do not include secrets or private code.