Unlike Google NotebookLM and Open Notebook, KnowNote focuses wholeheartedly on "user-centricity": greater convenience, lighter weight, and deeper understanding of you. We want to hear your needs and suggestions.
This is a Discussion, not an issue. Ideas and workflow pain points are collected here; once something is approved as work it moves into its own issue with an owner, an acceptance list and a milestone. The current plan is the v1.4 epic — see #82.
What makes feedback easier to act on
- Describe the workflow, not the feature. "I have 30 PDFs and only want to ask about 3 of them" is more actionable than "add a source filter".
- Say what you do today instead. The workaround tells us where the friction actually is.
- One topic per discussion. Start a new one for a distinct idea instead of commenting on an unrelated thread — that way it can be turned into an issue without losing context.
- Bugs do not belong here. They need to be reproducible and tracked separately, so please open a bug report.
Requests from this thread that became work
| Request |
Issue |
| Fine-grained chat context |
#94 |
| Ingestion status, retry and re-index |
#95 |
| Global search across sources and notes |
#96 |
| Multiple chat sessions per notebook |
#97 |
| Batch and folder import |
#98 |
| Cross-notebook source reuse |
#99 |
| Model connection diagnostics and first-run readiness |
#100 |
| KnowNote as a local MCP server |
#79 (ADR), #80 (implementation) |
How requests are answered
Feedback here is read, and not everything here will be built — but anything deliberately not built gets said out loud rather than left to rot. The "Explicit non-goals" section of #82 is where that happens, and the README's "What is not here yet" is kept honest for the same reason.
Unlike Google NotebookLM and Open Notebook, KnowNote focuses wholeheartedly on "user-centricity": greater convenience, lighter weight, and deeper understanding of you. We want to hear your needs and suggestions.
This is a Discussion, not an issue. Ideas and workflow pain points are collected here; once something is approved as work it moves into its own issue with an owner, an acceptance list and a milestone. The current plan is the v1.4 epic — see #82.
What makes feedback easier to act on
Requests from this thread that became work
How requests are answered
Feedback here is read, and not everything here will be built — but anything deliberately not built gets said out loud rather than left to rot. The "Explicit non-goals" section of #82 is where that happens, and the README's "What is not here yet" is kept honest for the same reason.