Replies: 1 comment 6 replies
-
Personally I like to keep my todos very simple and to the point. A lot of people use LLMs to communicate with other people but todos are just for me. Another option would be to feed a to-do in to a LLM to get suggestions on how to proceed? Or perhaps to suggest how some items should be prioritised? (if that's something it could feed back) However I might not be the best person to suggest as I don't use it - I haven't yet found a use-case which I feel adds much value. |
Beta Was this translation helpful? Give feedback.
6 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Lately I was wondering if there are interesting use cases for any sort of LLM integration in sleek. Although I use LLMs quite a bit as daily drivers, I am often puzzled about the awkward ways it is being implemented into services. If there are any use cases for sleek I really want to make sure those make sense.
One idea is to use AI for assistance while writing todos, similar to how JIRA uses LLMs to create templates, fix typos, or add context from other tickets.
I experimented with Mistral AI's APIs by sending a todo:
Fix sorting in drawer and create release tomorrow
I provided context like the todo.txt format, today's date, and my existing todos. The AI responded with something like:
2025-02-22 Fix sorting in +drawer and create @release tomorrow due:2025-02-23
The results differed quite a bit depending on how much instructions I added for the todo creation.
It seems the AI can understand the todo.txt format at least roughly, calculate due dates, or cross-reference existing todos.
I'd like to discuss with sleek's users if this integration is beneficial or if there are other use cases worth exploring.
Beta Was this translation helpful? Give feedback.
All reactions