feat(threads): add title summary generation and settings

[maria-rcks]

What Changed

This PR adds title summaries for threads.

Titles are generated based on the first prompt, there is a manual "Generate title summary" action in the thread menu. I also added an option to fchoose which model is being used for this task.

Why

This is better because it makes threads easier to organize and recognize at a glance. When titles reflect what the thread is actually about, it is easier to scan a long list of threads and come back to older work later.

UI Changes

Added thread title summary controls in Settings > Threads and a manual title summary action in the thread context menu.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes

closes #990

Note

Add thread title summary generation via Codex CLI with automatic mode and settings controls

• Adds a generateThreadTitle RPC (server.generateThreadTitle over WebSocket) that aggregates recent user messages and attachments, calls Codex CLI, and returns a sanitized title (max 60 chars, stripped quotes/extra lines).
• Introduces a titleSummaryState field (missing | generated | manual) across orchestration events, commands, projections, and the DB schema (migration 016).
• On the first message of a new thread, ChatView automatically triggers title generation when titleSummaryMode is "automatic"; failures surface as an error toast.
• Adds a "Generate title summary" context menu item in the Sidebar and a new settings page section to configure titleSummaryModel and toggle automatic title summaries.
• Behavioral Change: manual thread renames now set titleSummaryState to "manual" and auto-title generation is deferred and async rather than immediate.

^{Macroscope summarized 267b38f.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: eb354229-bdc5-4ac1-bcac-fd353242dd03

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

Tip

CodeRabbit can generate a title for your PR based on the changes with custom instructions.

Set the reviews.auto_title_instructions setting to generate a title for your PR based on the changes in the PR with custom instructions.

[binbandit]

Great work, id propose that we occasionally re-trigger to update the title?
Such as if a pull request opens for the work etc

[maria-rcks]

Great work, id propose that we occasionally re-trigger to update the title? Such as if a pull request opens for the work etc

I thought about this but how do we measure when to re-trigger?
Like every ten prompts or when things are committed, or what is the threshold?

Would love Julius comments on this.

[maria-rcks]

also could be a separate pr

[binbandit]

Happy for it to be a separate PR