Skip to content

Fix assistant UI state selectors #106

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.

Sign up for GitHub

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

Draft
amirgholipour wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

Fix assistant UI state selectors #106

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 7 additions & 4 deletions ui/src/components/Chat.jsx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -101,10 +101,13 @@ function UserMessage() {
}

function AssistantMessage() {
const message = useAuiState()
const isRunning = message.status?.type === 'running'
const hasText = message.content?.some(c => c.type === 'text' && c.text?.trim())
const reasoningParts = message.content?.filter(c => c.type === 'reasoning') || []
// Current assistant-ui versions require an explicit state selector.
// Subscribe only to the fields this message renderer uses so streaming
// updates remain stable and do not try to read the entire store.
const isRunning = useAuiState(s => s.message.status?.type === 'running')
const content = useAuiState(s => s.message.content)
const hasText = content?.some(c => c.type === 'text' && c.text?.trim())
const reasoningParts = content?.filter(c => c.type === 'reasoning') || []

if (!hasText && isRunning) {
return (
Expand Down