Introducing the PiPilot community — and a roadmap you help write

Until today, if something in PiPilot broke on you, your options were an email address and hope. You would send it, hear nothing for a while, and have no idea whether anyone had reproduced it, whether it was being worked on, or whether the thing you asked for had quietly shipped three weeks ago. That is a bad deal, and it is the one we were offering.

The community at pipilot.dev/community replaces it. Everything you send now has a public home you can follow.

The boards that do work come first

Most forums open with a wall of equally-weighted categories and a General board that swallows everything. Ours puts three boards above the rest, because they are the ones that produce outcomes: Bug Reports, Feature Requests and Feedback.

• Bug Reports carry a severity and an "affects me too" count, so a widespread problem shows up as one loud thread instead of forty quiet duplicates.
• Feature Requests are ranked by votes, and those votes are what drives the roadmap.
• Feedback is deliberately low-friction — no status machine, no process, just tell us how it feels to use.

Then the rest: Help & Support, where you mark the reply that actually solved it; Show & Tell for what you shipped; Prompts & Recipes; Templates; and a Lounge for everything else.

A roadmap that starts with you asking

Feature requests move across a public board — Requested, Planned, In progress, Shipped. Every card on it began as somebody’s request, and a shipped card links to the changelog entry that shipped it.

That last detail is the one we care most about. It closes the loop. You can follow a request from the moment you type it to the release note that says it is live, without asking anyone whether it went anywhere.

Report it without leaving your build

There is now a help button in the builder, beside the model and mode control. It files a bug, a feature request or feedback right there, and it attaches the context automatically: framework, model tier, build mode and project.

That is not a convenience feature. Most bug reports stall on one missing detail, and by the time anyone asks for it the reporter has moved on and cannot reproduce it either. Collecting it at the moment something goes wrong is the difference between a report that gets fixed and one that gets closed.

Built for people who build

Two things make this a builder’s forum rather than a generic one. Share a prompt in a prompt block and anyone reading gets an "Open in PiPilot" button that hands it straight to the builder, ready to run — so a good prompt is something you can use, not just read. And paste the URL of an app you published and the thread embeds the running app, not a screenshot of it.