ECHO-676 Show auto-generated title tooltip when using title field

[ussaama]

Summary by CodeRabbit

• Bug Fixes
  • Tooltip behavior for conversation titles improved: the tooltip now appears whenever a title exists. Its label shows the participant name when available, otherwise it displays "Title auto-generated". The tooltip remains anchored to the info icon for consistent discoverability.

[linear]

ECHO-676 Show auto-generated title tooltip when using `title` field

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Disabled knowledge base sources:

• Linear integration is disabled

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 48ef4de and 4b5d69c.

📒 Files selected for processing (1)

• echo/frontend/src/components/conversation/ConversationAccordion.tsx

---

Walkthrough

Tooltip visibility in ConversationAccordion was changed: it now appears whenever conversation.title exists; the tooltip label shows conversation.title if conversation.participant_name exists, otherwise "Title auto-generated".

Changes

Cohort / File(s)	Summary
Tooltip Conditional Logic echo/frontend/src/components/conversation/ConversationAccordion.tsx	Tooltip visibility decoupled from participant presence — visibility depends solely on title; label text conditionally set to title or "Title auto-generated" based on participant_name.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

LGTM.

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The PR title accurately describes the main change: enabling tooltip display for auto-generated titles when using the title field.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

• 📝 Generate docstrings (stacked PR)
• 📝 Generate docstrings (commit on current branch)

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch auto-generated-title-tooltip

Tip

Try Coding Plans. Let us write the prompt for your AI agent so you can ship faster (with fewer bugs).
Share your feedback on Discord.

---

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.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@echo/frontend/src/components/conversation/ConversationAccordion.tsx`:
- Line 566: The new translation string t`Title auto-generated` in
ConversationAccordion.tsx is not yet extracted; run the extraction and commit
the updated .po files: execute `pnpm messages:extract` (from the repo root) to
update the locale catalogs, verify the new key from the t template literal in
the generated messages, and include the changed .po/.json files in your commit
alongside the ConversationAccordion.tsx change so translations are available at
runtime.

---

ℹ️ Review info

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Disabled knowledge base sources:

• Linear integration is disabled

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between e138301 and 48ef4de.

📒 Files selected for processing (1)

• echo/frontend/src/components/conversation/ConversationAccordion.tsx

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Run pnpm messages:extract to capture the new Lingui string.

t\Title auto-generated`is a net-new translation key that won't land in the.po` files until extraction is run.

As per coding guidelines: "Use Trans component or t template literal for translations in frontend code, then run pnpm messages:extract to extract strings to .po files."

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@echo/frontend/src/components/conversation/ConversationAccordion.tsx` at line
566, The new translation string t`Title auto-generated` in
ConversationAccordion.tsx is not yet extracted; run the extraction and commit
the updated .po files: execute `pnpm messages:extract` (from the repo root) to
update the locale catalogs, verify the new key from the t template literal in
the generated messages, and include the changed .po/.json files in your commit
alongside the ConversationAccordion.tsx change so translations are available at
runtime.