feat: add agent selection, router and sidebar layout in React client #536
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This comment was marked as abuse.
This comment was marked as abuse.
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Risks
Low. Changes are isolated to the new React client with no impact on existing functionality. New API endpoints are additive only.
What does this PR do?
What kind of change is this?
Improvement
Why are we doing this? Any context or related work?
I think agent selection was needed because everyone using different agents instead of hardcoded default Eliza.
We also needed proper routing for the app, and a sidebar makes the most sense since we'll have lots of features to navigate between. I added TanStack Query since it handles all the loading states and caching automatically - way less boilerplate code to write