feat: add feedback tracking for assistant messages#1597
Conversation
WalkthroughAdds a like/dislike feedback UI and analytics for assistant messages, introduces INITIAL_ASSISTANT_MESSAGE with a Date timestamp, adopts that constant across chat pages and context, suppresses feedback during onboarding, and changes TypeScript JSX to "preserve". ChangesMessage Feedback Tracking and Initial Assistant Constant
🎯 3 (Moderate) | ⏱️ ~20 minutes 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Tip 💬 Introducing Slack Agent: The best way for teams to turn conversations into code.Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.
Built for teams:
One agent for your entire SDLC. Right inside Slack. 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. Comment |
…to response-feedback
github-actions
Bot
added
community
enhancement
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@frontend/app/chat/_components/assistant-message.tsx`:
- Around line 170-172: The feedback actions are currently rendered while the
assistant message is still streaming; update the render guard for MessageActions
(currently using isInitialGreeting and showFeedback) to also require the message
to be fully delivered (e.g., check a streaming/completion flag such as
!isStreaming, message.isStreaming === false, or message.isFinished) so
MessageActions only appears when streaming has finished; modify the conditional
around <MessageActions trackFeedback={trackFeedback} /> accordingly.
In `@frontend/app/chat/_components/message-actions.tsx`:
- Around line 22-49: The two icon-only Button controls rendering ThumbsUp and
ThumbsDown lack accessible names and toggle semantics; update the Buttons (the
ones using feedbackSelected and onClick={() => handleFeedback(...)}) to include
an accessible label (e.g., aria-label="Like" and aria-label="Dislike" or a
visually-hidden text child) and expose the selected state with
aria-pressed={feedbackSelected === "like"} / aria-pressed={feedbackSelected ===
"dislike"} so assistive tech sees the toggle state; keep existing onClick
handlers (handleFeedback) and maintain visual styling while adding these
attributes.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: c61c38c6-f445-4d10-a910-ff136b6700b1
📒 Files selected for processing (7)
frontend/app/chat/_components/assistant-message.tsxfrontend/app/chat/_components/message-actions.tsxfrontend/app/chat/_types/types.tsfrontend/app/chat/page.tsxfrontend/app/onboarding/_components/onboarding-content.tsxfrontend/contexts/chat-context.tsxfrontend/tsconfig.json
github-actions
Bot
added
enhancement
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@frontend/app/chat/page.tsx`:
- Line 56: INITIAL_ASSISTANT_MESSAGE is created at module load and reusing it
causes stale timestamps; when resetting the conversation in the page component
(initial state where INITIAL_ASSISTANT_MESSAGE is used, inside the
handleNewConversation effect, and inside the placeholderConversation effect),
unpack only the message content from INITIAL_ASSISTANT_MESSAGE and build a new
message object with the same content but a fresh timestamp using new
Date().toISOString(); update the places that reference INITIAL_ASSISTANT_MESSAGE
to create a new object (e.g., { ...INITIAL_ASSISTANT_MESSAGE, timestamp: new
Date().toISOString() } or extract content and set timestamp) so each reset gets
a current timestamp.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 06232c40-8787-45d3-b847-c9e58858e63b
📒 Files selected for processing (4)
frontend/app/chat/_components/assistant-message.tsxfrontend/app/chat/_components/message-actions.tsxfrontend/app/chat/page.tsxfrontend/contexts/chat-context.tsx
🚧 Files skipped from review as they are similar to previous changes (2)
- frontend/app/chat/_components/assistant-message.tsx
- frontend/app/chat/_components/message-actions.tsx
| content: "How can I assist?", | ||
| timestamp: new Date(), | ||
| }, | ||
| INITIAL_ASSISTANT_MESSAGE, |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Check the INITIAL_ASSISTANT_MESSAGE definition to see if timestamp is static or dynamic
rg -A 5 -B 2 'INITIAL_ASSISTANT_MESSAGE\s*=' frontend/app/chat/_types/types.tsRepository: langflow-ai/openrag
Length of output: 45
🏁 Script executed:
#!/bin/bash
# Search for INITIAL_ASSISTANT_MESSAGE definition across the frontend
rg 'INITIAL_ASSISTANT_MESSAGE\s*=' frontend/ --type ts --type tsx -A 8Repository: langflow-ai/openrag
Length of output: 91
🏁 Script executed:
#!/bin/bash
# Also search for where it's imported from in page.tsx
rg 'import.*INITIAL_ASSISTANT_MESSAGE' frontend/app/chat/page.tsx -B 2 -A 2Repository: langflow-ai/openrag
Length of output: 189
🏁 Script executed:
#!/bin/bash
# Check the structure of the page.tsx file at the mentioned lines
sed -n '50,70p' frontend/app/chat/page.tsx
sed -n '320,335p' frontend/app/chat/page.tsx
sed -n '560,575p' frontend/app/chat/page.tsxRepository: langflow-ai/openrag
Length of output: 2087
🏁 Script executed:
#!/bin/bash
# Read the types.ts file to find INITIAL_ASSISTANT_MESSAGE definition
cat frontend/app/chat/_types/types.tsRepository: langflow-ai/openrag
Length of output: 1728
🏁 Script executed:
#!/bin/bash
# Also check the chat-context.tsx implementation mentioned in the review
rg -B 5 -A 5 'new Date().toISOString()' frontend/app/chat/Repository: langflow-ai/openrag
Length of output: 45
🏁 Script executed:
#!/bin/bash
# Find chat-context.tsx
fd 'chat-context' frontend/ --type fRepository: langflow-ai/openrag
Length of output: 98
🏁 Script executed:
#!/bin/bash
# Check line 347 area and message initialization in chat-context
rg 'const createMessage|content.*timestamp|new Date' frontend/app/chat/chat-context.tsx -B 3 -A 3Repository: langflow-ai/openrag
Length of output: 138
🏁 Script executed:
#!/bin/bash
# Check the correct chat-context.tsx location
rg 'INITIAL_ASSISTANT_MESSAGE|new Date' frontend/contexts/chat-context.tsx -B 3 -A 3Repository: langflow-ai/openrag
Length of output: 809
🏁 Script executed:
#!/bin/bash
# Also search for any message creation patterns around line 347 or nearby
sed -n '340,360p' frontend/contexts/chat-context.tsxRepository: langflow-ai/openrag
Length of output: 719
Create fresh timestamps when resetting to INITIAL_ASSISTANT_MESSAGE instead of reusing the stale module-level timestamp.
The INITIAL_ASSISTANT_MESSAGE constant is defined with timestamp: new Date() at module load time, meaning all three reset locations (initial state at line 56, handleNewConversation effect at line 328, and placeholderConversation effect at line 566) share the same static timestamp rather than reflecting the actual start time of each conversation.
The pattern in frontend/contexts/chat-context.tsx demonstrates the correct approach: extract only the content from INITIAL_ASSISTANT_MESSAGE and create a fresh timestamp with new Date().toISOString(). Apply the same pattern here:
Proposed fix
-const [messages, setMessages] = useState<Message[]>([
- INITIAL_ASSISTANT_MESSAGE,
-]);
+const [messages, setMessages] = useState<Message[]>([
+ { ...INITIAL_ASSISTANT_MESSAGE, timestamp: new Date() },
+]);And similarly for lines 328 and 566:
-setMessages([INITIAL_ASSISTANT_MESSAGE]);
+setMessages([{ ...INITIAL_ASSISTANT_MESSAGE, timestamp: new Date() }]);Also applies to: 328-328, 566-566
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@frontend/app/chat/page.tsx` at line 56, INITIAL_ASSISTANT_MESSAGE is created
at module load and reusing it causes stale timestamps; when resetting the
conversation in the page component (initial state where
INITIAL_ASSISTANT_MESSAGE is used, inside the handleNewConversation effect, and
inside the placeholderConversation effect), unpack only the message content from
INITIAL_ASSISTANT_MESSAGE and build a new message object with the same content
but a fresh timestamp using new Date().toISOString(); update the places that
reference INITIAL_ASSISTANT_MESSAGE to create a new object (e.g., {
...INITIAL_ASSISTANT_MESSAGE, timestamp: new Date().toISOString() } or extract
content and set timestamp) so each reset gets a current timestamp.
* add feedback tracking for assistant messages * style: apply biome auto-fixes [skip ci] * don't show during onboarding * coderabbit suggestions --------- Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
2 participants
Adds a new like/dislike option for tracking purposes on assistant messages.
Adds a
INITIAL_ASSISTANT_MESSAGEoption now used when creating new chats and the newMessageActionsshouldn't be shown there.it also won't show during onboarding
Summary by CodeRabbit
New Features
Improvements