new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

shadcn/ui · Components · all subjects

message-scroller/best-practices

1 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

MessageScroller best practices for streaming chat

A great streaming chat should: 1) Move only when the reader asked to move - never auto-scroll by default. 2) Follow only while they're following - if at live edge keep stream in view, if scrolled away leave them. 3) Every interaction is a signal - scrolling, selecting text, keyboard, opening links, searching should all stop interface movement. 4) Start new turn near top of viewport. 5) Then stream in the answer - answer grows into screen, not immediately push everything. 6) Keep previous conversation context visible - prompt and reply stay visually connected. 7) Let new content arrive offscreen. 8) Show what's happening out of view - indicate when response streams or new messages arrive. 9) Make it easy to return to latest reply - "Jump to latest" should bring reader back and resume following. 10) Let people jump anywhere - long threads need message links, search, unread markers, direct navigation. 11) Reopen where reader left off - saved conversation opens at last meaningful turn, often last user message, not absolute bottom. 12) Keep reader's place when layout changes - images load, markdown expands, code renders, older messages appear. 13) Handle interruptions without stealing position - stopping, retrying, regenerating, branching, errors should not unexpectedly move. 14) Stay responsive in long threads. 15) Be accessible without noise - keep transcript navigable, preserve keyboard focus, announce important events at comfortable pace. Never move the reader against their intent.

Give your agent this brain