Community
Help us
Help us
build better.
Answer questions from the team. Vote on decisions. Share context. Account required — one response per question.
Loading questions...
◈ Responses are tied to your account. Voting is not anonymous internally, but your name is never displayed publicly. Have a feature idea instead?
How this feeds the product
Community questions are a structured signal layer — not a forum, not a chat. Here's how they work:
Questions are written by the team
Each question is about a real decision — something in active development, a direction we're uncertain about, or context we need to calibrate before shipping. They're not polls or engagement hooks.
Responses are read, not just counted
Comments and written responses are reviewed individually. The team reads them. A question with 5 thoughtful responses carries more weight than one with 50 clicks. Volume is not the goal.
Results stay internal until acted on
Vote counts and response breakdowns are not shown publicly. This is deliberate — early access means small numbers, and small numbers are easy to misread. When a question's results change something, it shows up in the changelog.
Closed questions stay in the archive
After a question closes, it moves to the archive below. The responses contributed to a decision. Reading the archive tells you what the team was thinking about and when.
◈ Archive
Closed questions. Vote counts are not shown — reflect and share a thought without being anchored by results. Thoughts feed back into the team feedback pipeline.
Loading archive...