Fix conversation list UI issues #16
Merged
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.
Summary
This PR fixes several UI issues in the conversation list and conversation details sections:
Issues Fixed
agent_statusfieldagent.namebut the API schema usesagent.kindChanges Made
UI Fixes
max-h-96(384px) tomax-h-[600px]for better visibilitystatusfield toConversationInfointerface and mapping fromagent_statusgetAgentNamefunction to useagent.kindas primary field withagent.nameas fallbackAPI Schema Updates
AgentBaseinterface to usekind: stringas primary field (matching API schema) withname?: stringas optional fallbackAgentExecutionStatusenum to include missing status values:WAITING_FOR_CONFIRMATION = 'waiting_for_confirmation'STUCK = 'stuck'Component Updates
createConversationto usekind: 'Agent'instead ofname: 'CodeActAgent'AgentBaseinterface structureTesting
Files Changed
src/types/base.ts- UpdatedAgentBaseinterface andAgentExecutionStatusenumsrc/models/conversation.ts- Added status field mappingexample/src/components/ConversationManager.tsx- Fixed UI issues and updated agent handlingexample/src/utils/serverStatus.ts- Updated to use newAgentBaseinterfaceThese changes ensure the conversation list displays properly with correct status information and agent names, improving the overall user experience.
@rbren can click here to continue refining the PR