[GH-ISSUE #2056] Improve karakeep UI to introduce/teach/encourage usage of the Search Query Languages #1280

Open
opened 2026-03-02 11:56:15 +03:00 by kerem · 0 comments
Owner

Originally created by @xuatz on GitHub (Oct 19, 2025).
Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/2056

Describe the feature you'd like

This is a general suggestion that can involve various changes/improvements:

For example, we should provide a quick link to the docs from the search screen or search bar, so that people are aware of the search query language.

I do know that a link is available on the smart list modal, but the new users probably don't expect that.

Another more drastic example is that, every list/tag page, could be 100% based on the search query, similar to how github issues is like. even if you use the select menu for "author", it would also populate the search bar with author:xuatz.

Image

For karakeep case, for example in /dashboard/favourites, we could have the search bar already populated with is:fav.
This UI would hint to user that there exist some form of query language that power users can use. Some refactoring will have to be done for the application though, to prevent redirecting to /search immediately when the search bar is not empty.

Another possible idea could be that we can try see if we can support and hint to powerusers from different domains, by supporting autocompleting to supported keywords.
e.g. when typing is:, we should show the available options such as archived , inlist

Describe the benefits this would bring to existing Karakeep users

Expose to use the search query language, which can be quite useful for power users.

Can the goal of this request already be achieved via other means?

It's a UI/UX improvement over existing capabilities.

Have you searched for an existing open/closed issue?

  • I have searched for existing issues and none cover my fundamental request

Additional context

No response

Originally created by @xuatz on GitHub (Oct 19, 2025). Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/2056 ### Describe the feature you'd like This is a general suggestion that can involve various changes/improvements: For example, we should provide a quick link to the [docs](https://docs.karakeep.app/guides/search-query-language/) from the search screen or search bar, so that people are aware of the search query language. I do know that a link is available on the smart list modal, but the new users probably don't expect that. Another more drastic example is that, every list/tag page, could be 100% based on the search query, similar to how github issues is like. even if you use the select menu for "author", it would also populate the search bar with `author:xuatz`. <img width="1280" height="496" alt="Image" src="https://github.com/user-attachments/assets/2e97c401-9928-41d0-9896-ae53439a9882" /> For karakeep case, for example in `/dashboard/favourites`, we could have the search bar already populated with `is:fav`. This UI would hint to user that there exist some form of query language that power users can use. Some refactoring will have to be done for the application though, to prevent redirecting to /search immediately when the search bar is not empty. Another possible idea could be that we can try see if we can support and hint to powerusers from different domains, by supporting autocompleting to supported keywords. e.g. when typing `is:`, we should show the available options such as `archived `, `inlist` ### Describe the benefits this would bring to existing Karakeep users Expose to use the search query language, which can be quite useful for power users. ### Can the goal of this request already be achieved via other means? It's a UI/UX improvement over existing capabilities. ### Have you searched for an existing open/closed issue? - [x] I have searched for existing issues and none cover my fundamental request ### Additional context _No response_
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/karakeep#1280
No description provided.