-
Notifications
You must be signed in to change notification settings - Fork 343
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG]Chat continuity breaks when sending new message after AI response #639
Comments
Thank you for reporting this behavior. This is actually working as designed. Please wait until the conversation title appears in the chat history before proceeding with your next message. This will ensure proper continuity of the conversation. Let our team consider UX improvement on another issue. thank you |
Could you check cloudwatch logs for websocket handler and api handler? |
Can you see any error messages on logs? Please check both websocket handler and api handler |
Description:
When interacting with Claude in Bedrock, the conversation flow is interrupted after receiving an AI response. Each new user message creates a new conversation instead of continuing the existing thread.
Steps to reproduce:
Start a new conversation with Claude
Send an initial message and receive Claude's response
Attempt to send a follow-up message
Observe that the new message starts a fresh conversation instead of continuing the previous one
Expected behavior:
The conversation should maintain continuity, allowing users to send multiple messages within the same chat thread after receiving responses from Claude.
Current behavior:
Each new user message after Claude's response creates a new conversation, losing the context and history of the previous interaction.
Impact:
This issue significantly impacts the user experience and the ability to maintain contextual conversations with the AI. Users cannot build upon previous exchanges or reference earlier parts of the conversation.
Environment:
Bedrock Claude chat: 2.3.0
Platform: Safary (ios) & Google Chrome (windows/linux)
Thank you
The text was updated successfully, but these errors were encountered: