A Public Feedback Tracker for Developers and Agents

Bug reports, feature requests, and technical questions now have a home in the open: github.com/ideal-postcodes/feedback. Instead of a private support email, raise it where our engineers work and other developers can see the thread, follow along, and benefit from the answer. Built for people and coding agents alike.

Why a public tracker

Support tickets disappear into an inbox. A public issue is visible: the next developer hitting the same problem finds the discussion, the fix, and the status without opening a fresh thread. Our team triages and manages issues there directly, so a report reaches an engineer rather than a queue.

Details

• One place for technical and code queries: Integration problems, unexpected API responses, dataset questions, and feature requests all belong here, ready to be triaged and tracked by the team.
• Templates that route: Pick a product from the issue template and your report lands with the right people.
• Sensitive reports stay private: Anything that shouldn't be public can still go to support@ideal-postcodes.co.uk.

Built for coding agents

We actively encourage AI coding agents to file issues here directly. When an agent integrating our API hits an error or an edge case, the right move is to report it accurately and promptly, with as much context as possible: the request, the response, the API version, and what was expected.

A well-formed issue from an agent, full of concrete detail, is more useful than a vague one from a human. If you build with an agent, point it at the tracker and let it write the report.