How to post a good feature request

Feature requests are how the community shapes the roadmap. A well-written request is far more likely to earn upvotes, spark useful discussion, and land on the build queue. This guide explains how to write one that actually moves things forward.

Before you post

Search first. The most common outcome of a new request is that it duplicates an existing one. Use the search bar and try a few different phrasings. If you find a match, upvote it and add a comment with your specific context — that is more useful than a second thread on the same idea.

Writing the request

1. One idea per thread. Split compound requests into separate threads. A single, focused post is easier to evaluate, discuss, and track. "Better memory AND a mobile app AND dark mode" is three requests; post three threads.

2. Describe the problem, not just the solution. The most useful requests start from a real friction point, not a predetermined fix. Instead of "add a GPT-4o shortcut button", write: "When I switch between providers frequently, I lose several clicks each time because there is no way to pin a preferred model to a mode." The team may solve that problem in a way you did not anticipate — and a better understanding of the problem makes that more likely.

3. Include context. What mode, workflow, or feature were you using? What did you expect to happen, and what happened instead? A sentence or two of concrete context anchors the discussion.

4. One clear title. The title should state the outcome you want. "Allow pinning a model per mode" is scannable. "Suggestion for improvement" is not.

How upvotes affect the roadmap

The team reviews the feature-requests category regularly. Upvote count is a genuine signal — not a guarantee, but a real input into prioritisation. High-upvote requests get reviewed in planning cycles; low-signal or duplicate requests do not slow things down if they are consolidated.

Thank you for taking the time to write clearly. Good requests make ToRun better for everyone.