Before you submit
Search existing issues
Check the GitHub Issues page for open and closed requests. Your idea may already be tracked, in progress, or have been discussed and declined.
Check the roadmap
Review the ROADMAP.md in the repository. Features already on the roadmap do not need a new issue.
What to include
A good feature request answers three questions:What is the problem?
Describe the specific workflow or limitation you are running into. Feature requests grounded in a real problem are easier to evaluate and prioritize.
What is your proposed solution?
Describe the behavior you want. Be specific: which part of the UI, which command, which configuration option.
What are the alternatives?
List any workarounds you have tried and why they are not sufficient. This helps the maintainers understand the urgency.
Scope guidance
| Type | Where to propose |
|---|---|
| New agent support | GitHub Issue, include the agent’s CLI name and install instructions |
| New theme | Pull request with a theme.json file in src/themes/ |
| New Tauri command | GitHub Issue with the proposed Rust signature and use case |
| UI layout change | GitHub Issue with a description or sketch |
| Documentation improvement | Pull request directly against tempest-docs |
After submission
Feature requests are reviewed on a rolling basis. A maintainer will label the issue (enhancement, needs-discussion, accepted, or wont-fix) and respond with questions or a decision. Accepted features are added to the roadmap before implementation begins.