Feature Requests
TotalRecalls is a one-person project, so there is no voting board and no queue to game. Requests are read as letters, and the ones that change the roadmap are the ones that explain a real workflow.
How to send one
Email contact@totalrecalls.app with your suggestion. A human reads every message.
What makes a request useful
- Describe the workflow, not just the feature. "I keep my notes in Obsidian and want my chats next to them" tells more than "add Obsidian support".
- Say what you do today instead. The current workaround usually reveals the actual problem.
- Mention which provider and how many conversations. Scale changes the design.
What happens next
Requests are read, grouped by the underlying need, and either folded into an existing plan, added to the roadmap as a design note, or set aside with a reason. There are no dates, because promising dates is how small projects break their word. If a request is already covered by a preview, adding your use case to it still helps — it shifts the order.