Provide more options for "Thread saving" retention length in Kagi Assistant (e.g. 48 hours)

Anonymous22

That would just be a more 'limited' way of doing it by creating a special 30 day tag and that in turn also raises questions about privacy (threads expected to be gone in a day are still not deleted) unless there is also an option of not using the bin. And that in turn brings one back to, "there's no 'one-week retention' tag".

salvadore1

24 Hrs is too short. Forever is "too long".

Seven days would be perfect. That way, I wouldn't have to re-enter the same prompt from the day before because it was deleted. Kagi would actually save money with these longer thread-saving options.

bln

Personally I would also like to use a longer time, without a need for custom times or rules depending on tags. Just whatever between 1 week and 1 year would work for me basically.

k19b1

I like many suggestions already made and want to add my voice and five cents to this.

Making everything customizable to the n-th degree would be cool of course but I think the quick and easy way would solve 80% of user needs here.

Therefore I suggest and request that (for now) you only add more options to the Thread Saving drop down.

Sensible additions would be:

1 week
1 month

armandf

I run into this problem often. I create a lot of throw away threads that clutter things up too much to use 'forever', so I use '24h'. Most of the time, 24h keeps things nice and tidy. But frequently I will have a long conversation about something and don't know ahead of time that it's going to be long, nor do I know that I'm going to want to keep it. I start in the evening, work on it for a while, go to bed, then to work, then dinner, chores, blah blah, and then finally get back to it and I've just missed it.

I'm going to echo the last couple replies here. Please just add a few options to the default lifetime menu and ship it. Things like a recycle bin might also work, but it's not here yet and is slightly orthogonal to the problem. You've already got the plumbing in place to allow 24 hours, just allow a few other sensible options call it a day.

The more elegant or complete solutions can ship when they ship. Perhaps we users should just be better at knowing when to preserve our chats, but the evidence clearly shows that we aren't. At the end of the day, this is two years of posts pontificating about how best to add two lines to a dropdown menu... please just fix it :-)

badgal

Like others have said, if you add the below options, most of us would be able to sleep at night knowing that we can resume the conversation the next day and the thread wouldn’t be lost.

7 days (please add this ASAP)
30 days (would be nice to add this too to offer a little more retention period if I can ask for another option)

ZJaume

Drizzt321 default retention for a particular Agent

I really like this to have, for example, complex queries and long answers made with flagship models saved during more time because those are expensive. A quick answer I think is fine if it gets lost after 24h.

JosephT

Pls this again , just the 48 hours one would be great. I try to understand why companies would be reluctant or find it hard to implement some features from their position but i can't come up with a reason for this. i'd say not providing the option makes people turn on forever increasing storage.

natkarmios

I'd like this too; a week would be the sweet spot for me.

JosephT

You people are funny you got it . 48/36 hours would've been best to prevent a crowded workspace while still temporary and giving you chances to look over your threads. But thank you, 1 week is much better .

« Previous Page