starred/karakeep

Fork 0

mirror of https://github.com/karakeep-app/karakeep.git synced 2026-04-25 07:56:05 +03:00

[PR #1361] [CLOSED] feat(tags): infer todo tag from text content #1805

New issue

Closed

opened 2026-03-02 11:59:16 +03:00 by kerem · 0 comments

kerem commented

2026-03-02 11:59:16 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/karakeep-app/karakeep/pull/1361
Author: @xuatz
Created: 5/5/2025
Status: ❌ Closed

Base: main ← Head: feat/infer-todo-tag

📝 Commits (1)

d460405 feat: infer todo tag from text content

📊 Changes

2 files changed (+2 additions, -1 deletions)

View changed files

📝 docker/docker-compose.dev.yml (+0 -1)
📝 packages/shared/prompts.ts (+2 -0)

📄 Description

Summary

Add extra prompt instruction, to infer text bookmarks as potential tasks, and give it an #todo tag

Notes

Firstly, thank you for this wonderful app! This is truly the bookmark app of my dreams. This is partially why I am making this PR to introduce a change that is catered specifically to my workflow.

In my opinion, I'm coming from the same perspective as what you wrote in the recent changelog:

Karakeep was born because I don't want to spend time organizing what I hoard. I just throw stuff in there and karakeep's tagging and search will help me retrieve it later.

I love the autotagging feature and all i need to make it perfect is to allow me to make "todos" without having to select a special input type, and have the LLM to infer it.

I see that https://github.com/karakeep-app/karakeep/pull/505#issuecomment-2398016762 there is a consideration to allow users to insert their own custom prompts, but I have a selfish desire to make todo an official minor feature of karakeep (so that I don't have maintain a small long-lived fork 😅)

There are more changes I want to suggest for this workflow, but considering that this came out of nowhere, I wanted to make this PR and open the conversation of potentially adding this use-case.

Demo

https://github.com/user-attachments/assets/654e8db0-bce6-43a6-a89d-7b0cfcf0e41e

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/karakeep-app/karakeep/pull/1361 **Author:** [@xuatz](https://github.com/xuatz) **Created:** 5/5/2025 **Status:** ❌ Closed **Base:** `main` ← **Head:** `feat/infer-todo-tag` --- ### 📝 Commits (1) - [`d460405`](https://github.com/karakeep-app/karakeep/commit/d46040564f871e2744e5b46ba8084019df78cf0d) feat: infer todo tag from text content ### 📊 Changes **2 files changed** (+2 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `docker/docker-compose.dev.yml` (+0 -1) 📝 `packages/shared/prompts.ts` (+2 -0) </details> ### 📄 Description ## Summary Add extra prompt instruction, to infer text bookmarks as potential tasks, and give it an `#todo` tag ## Notes Firstly, thank you for this wonderful app! This is truly the bookmark app of my dreams. This is partially why I am making this PR to introduce a change that is catered specifically to my workflow. In my opinion, I'm coming from the same perspective as what you wrote in the recent changelog: > Karakeep was born because I don't want to spend time organizing what I hoard. I just throw stuff in there and karakeep's tagging and search will help me retrieve it later. I love the autotagging feature and all i need to make it perfect is to allow me to make "todos" without having to select a special input type, and have the LLM to infer it. I see that https://github.com/karakeep-app/karakeep/pull/505#issuecomment-2398016762 there is a consideration to allow users to insert their own custom prompts, but I have a selfish desire to make todo an official minor feature of karakeep (so that I don't have maintain a small long-lived fork 😅) There are more changes I want to suggest for this workflow, but considering that this came out of nowhere, I wanted to make this PR and open the conversation of potentially adding this use-case. ## Demo https://github.com/user-attachments/assets/654e8db0-bce6-43a6-a89d-7b0cfcf0e41e --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

kerem

2026-03-02 11:59:16 +03:00

closed this issue
added the
pull-request
label

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#1805

No description provided.

Rows
Columns