fix: thread sorting issue

[cmppoon]

Describe Your Changes

Hello maintainers,

I came across #5923 and I would like to contribute by fixing this issue.

• I noticed that the local updated field is not updated when performing actions, which causes the sorting logic not to trigger as expected.

I hope this fix is correct and helpful. Let me know if there is any changes required from my end. Thanks!

Fixes Issues

• Closes bug: Thread sorting order issue #5923
• Closes #

Self Checklist

• Added relevant comments, esp in complex areas
• Updated docs (for bug fixes / features)
• Created issues for follow-up changes or refactoring needed

---

Important

Fixes thread sorting issue by updating updated timestamp in useThreads.ts functions.

• Behavior:
  • Fixes thread sorting issue by updating updated timestamp in toggleFavorite, updateCurrentThreadAssistant, and renameThread in useThreads.ts.
  • Ensures sorting logic triggers correctly when threads are modified.
• Fixes:
  • Closes bug: Thread sorting order issue #5923.

^{This description was created by for 1b330ef. You can customize this summary. It will automatically update as commits are pushed.}

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed everything up to 1b330ef in 56 seconds. Click for details.

• Reviewed 28 lines of code in 1 files
• Skipped 0 files when reviewing.
• Skipped posting 3 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. web-app/src/hooks/useThreads.ts:91

• Draft comment:
  Good: 'updated' field is now set in toggleFavorite. Consider using Math.floor(Date.now() / 1000) if an integer timestamp is preferred.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

2. web-app/src/hooks/useThreads.ts:190

• Draft comment:
  Nice update: refreshing the timestamp in updateCurrentThreadAssistant to aid immediate sorting.
• Reason this comment was not posted:
  Confidence changes required: 10% <= threshold 50% None

3. web-app/src/hooks/useThreads.ts:219

• Draft comment:
  Setting 'updated' in renameThread ensures threads reorder immediately on title change. This fixes the reported issue.
• Reason this comment was not posted:
  Confidence changes required: 10% <= threshold 50% None

Workflow ID: wflow_fdx4u0S0fVexUV78

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}

[urmauur]

Hi @cmppoon, Thank you for contributing. I really appreciate it. we’re going to release version 0.6.6 this week, I think this will be included in version 0.6.7. I’ll try it out first.

[urmauur]

Tested and LGTM