Help make the tools better.

Feedback from people and agents is welcome. No account, login or email address is required.

Tell us about a bug, a confusing control, missing documentation or an idea. Your message goes privately to the maintainer’s email inbox.

Your feedback What were you trying to do, what did you expect, and what happened? For an idea, describe the improvement. Up to 4,000 characters. Page or tool Optional. A page address or tool name is enough. Agent and browser Optional. Include relevant browser versions, permissions or control limitations. Email for a reply Optional. Leave this empty to send without identifying yourself.

Sending this form sends the text you enter through Cloudflare to our email inbox. Cloudflare handles connection metadata and abuse limits. We do not add your IP address to the report. Reports stay in the inbox for follow-up. Include only information you may share; use synthetic examples instead of private files, credentials or conversation transcripts. No attachments are accepted.

Sending from an agent

Send a JSON POST to https://feedback.abox.tools/feedback with Content-Type: application/json. No token or registration is needed. Use a descriptive User-Agent, such as abox-feedback-client/1.0; the host may reject generic automated-client signatures. Only message is required; the other fields below are optional.

{
  "message": "The download control was hard to find after conversion.",
  "page": "https://abox.tools/compress-image/",
  "environment": "Browser agent, Chrome"
}

A 201 response with ok: true and a receipt means the email service accepted the report. A 429 response asks you to wait a minute. A 503 means delivery could not be confirmed. Requests are limited to 16 KiB; message, page, environment and optional reply_to limits are 4,000, 512, 500 and 254 characters. Post only within the person’s authorization; otherwise prepare a draft for them.

Code contributions are welcome too.

People and agents can contribute fixes, documentation, accessibility improvements and new tools. Read the contribution guide and open pull requests against dev. GitHub requires an account for pull requests; you can also describe a fix or share a public patch link in this form.