Skip to content
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

Improve chat initial experience #889

Closed
3 of 4 tasks
josancamon19 opened this issue Sep 19, 2024 · 3 comments
Closed
3 of 4 tasks

Improve chat initial experience #889

josancamon19 opened this issue Sep 19, 2024 · 3 comments
Assignees

Comments

@josancamon19
Copy link
Contributor

josancamon19 commented Sep 19, 2024

The initial message is much better.

  • Initial message should include the initial default questions for the user to try, make them exciting to try.
  • Uses the name, to make it more user focused.
  • Clear chat option
  • Chat smoothness, scrolling it's natural, and doesn't feel laggy

Image

@josancamon19
Copy link
Contributor Author

josancamon19 commented Sep 19, 2024

  • Lets make the progress when loading chat messages for the first time better
  • Let's also try loading chat once the app opens, instead of after a user press on chat and has to wait, do some caching too I guess

@josancamon19
Copy link
Contributor Author

josancamon19 commented Sep 19, 2024

  • Chat memory detail navigation is better, + errors are handled

beastoin added a commit that referenced this issue Sep 22, 2024
Related to #889 
- [x] Initial message should include the initial default questions for
the user to try, make them exciting to try.
- [x] Uses the name, to make it more user focused.
- [x] Clear chat option (where to show it?)
- [x] Lets make the progress when loading chat messages for the first
time better
- [x] Let's also try loading chat once the app opens, instead of after a
user press on chat and has to wait, do some caching too I guess
- [x] Chat memory detail navigation is better, + errors are handled
(could not find any errors except for incorrect memory details showing
up due to how the new approach has been structured which is fixed as
well. Also made improvements, the memory only gets downloaded if it
doesn't exist in the memory_provider. So the navigation should be quick
in most cases)

<img
src="https://github.com/user-attachments/assets/d18b7d8f-516f-49f4-a3c4-b908796b4d11"
width="350">


https://github.com/user-attachments/assets/5967181a-1220-4bfd-b5b0-d3f8e915993f





https://github.com/user-attachments/assets/c9b8a3d6-8c8e-440c-9018-90f82af0ee30






https://github.com/user-attachments/assets/a1f25006-9a71-41a5-a74f-c53dd9d42020





<!-- This is an auto-generated comment: release notes by OSS
Entelligence.AI -->
### Summary by Entelligence.AI

Release Notes:

- New Feature: Added the ability for users to clear their chat history,
improving user control over data.
- New Feature: Introduced an animated mini banner widget that enhances
the UI experience.
- Refactor: Optimized memory detail navigation and initial chat options
for better performance and user interaction.
- Refactor: Improved message loading and chat clearing behavior in the
`MessageProvider` class.
- Bug Fix: Adjusted logic in `addMemoryWithDate` method to correctly
handle memory insertion based on date comparison.
- Chore: Added a new backend endpoint to clear chat history and return
initial message, enhancing server-side functionality.
<!-- end of auto-generated comment: release notes by OSS Entelligence.AI
-->
@josancamon19
Copy link
Contributor Author

Finalizing a couple few things, but lgtm for closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

2 participants