ECHO-372 Fix conversation summary

[ussaama]

Summary by CodeRabbit

• Improvements
  • Enhanced control over when the summary section is displayed in conversations.
  • Adjusted layout spacing for a more compact and visually appealing interface.
  • Upgraded the summary title to a larger heading for better visibility.
  • Refined conditions for showing dividers and summary-related UI elements for improved clarity.

[linear]

ECHO-372 Bug UI : summary of transcript is duplicated

[coderabbitai]

Walkthrough

This change refines the logic and layout for displaying the summary section in the project conversation overview. It introduces a new variable to control summary visibility, adjusts rendering conditions, reduces vertical spacing between components, changes heading levels, and updates divider rendering logic for a more precise and consistent UI.

Changes

Cohort / File(s)	Change Summary
Summary Section Logic & Layout Adjustments echo/frontend/src/routes/project/conversation/ProjectConversationOverview.tsx	Introduced showSummarySection boolean, updated summary rendering conditions, reduced vertical gaps, changed heading level for summary title, adjusted button margin, and refined divider rendering logic.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant UI
    participant ConversationData

    User->>UI: Loads Project Conversation Overview
    UI->>ConversationData: Fetch conversation details
    ConversationData-->>UI: Returns summary, source, chunks, status
    UI->>UI: Evaluate showSummarySection
    alt showSummarySection && chunks.length > 0
        UI->>UI: Render Summary Section (h2 heading)
        alt summary exists && conversation finished
            UI->>UI: Render Divider below summary
        end
    end
    UI->>UI: Render other sections with updated spacing

Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~7 minutes

Assessment against linked issues

Objective	Addressed	Explanation
Prevent duplicated summary of transcript in UI (ECHO-372)	✅

Assessment against linked issues: Out-of-scope changes

No out-of-scope changes found.

Suggested labels

bug

Suggested reviewers

• spashii

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between cb2eafd and 46f2414.

📒 Files selected for processing (1)

• echo/frontend/src/routes/project/conversation/ProjectConversationOverview.tsx (4 hunks)

🧰 Additional context used

🧠 Learnings (2)

📓 Common learnings

Learnt from: ussaama
PR: Dembrane/echo#224
File: echo/frontend/src/components/report/CreateReportForm.tsx:97-155
Timestamp: 2025-07-17T15:57:51.321Z
Learning: In echo/frontend/src/components/report/CreateReportForm.tsx, the conversation status section should only be displayed when there are pending conversations (conversationCounts.pending !== 0). When all conversations are processed, no status information should be shown to keep the UI minimal and clean.

Learnt from: ussaama
PR: Dembrane/echo#205
File: echo/frontend/src/lib/query.ts:1444-1506
Timestamp: 2025-07-10T12:48:20.683Z
Learning: ussaama prefers string concatenation over template literals for simple cases where readability is clearer, even when linting tools suggest template literals. Human readability takes precedence over strict linting rules in straightforward concatenation scenarios.

echo/frontend/src/routes/project/conversation/ProjectConversationOverview.tsx (1)

Learnt from: ussaama
PR: #224
File: echo/frontend/src/components/report/CreateReportForm.tsx:97-155
Timestamp: 2025-07-17T15:57:51.321Z
Learning: In echo/frontend/src/components/report/CreateReportForm.tsx, the conversation status section should only be displayed when there are pending conversations (conversationCounts.pending !== 0). When all conversations are processed, no status information should be shown to keep the UI minimal and clean.

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: Cursor Bugbot
• GitHub Check: ci-check-server

🔇 Additional comments (6)

echo/frontend/src/routes/project/conversation/ProjectConversationOverview.tsx (6)

58-62: LGTM! Clean extraction of summary visibility logic.

This refactoring centralizes the decision logic for showing the summary section, which should help eliminate the duplication bug described in ECHO-372. The condition is well-structured and handles both existing summaries and potential summary generation scenarios.

---

65-70: Solid improvements to rendering logic and spacing.

The updated condition (length > 0 + showSummarySection) is more permissive for chunk count but adds the centralized visibility control, which should prevent the summary duplication. The tighter gap spacing (3rem and 1.5rem) will create a more compact, professional layout.

---

73-73: Nice semantic improvement.

Promoting the summary title from h3 to h2 gives it appropriate hierarchical weight in the conversation overview structure.

---

127-127: Good visual balance adjustment.

Reducing the negative margin from -3rem to -2rem maintains proper spacing relationships with the tighter overall layout.

---

138-139: More precise divider logic - good refinement.

Changing from OR to AND logic makes the divider more selective, appearing only when there's both a summary and a finished conversation. This should reduce visual clutter and is likely part of the duplication fix.

---

146-146: Consistent spacing refinement across all sections.

The uniform reduction to 1.5rem gap maintains visual consistency throughout the conversation overview layout.

Also applies to: 181-181

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix-conversation-summary

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai generate unit tests to generate unit tests for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.