@assistantuii
iAccount based inUnited States
About this account
- Account based in
- United States
- Connected via
- Web
Account-level information from X, not a live location or the device used for a specific post.
Open Source React Library for AI Chat (YC W25)
Joined August 2024
- Tweets121
- Following39
- Followers938
- Likes237
learn more
- Website and docs: jevia.dev
- Github: github.com/assistant-ui/jevi…
you should check this out!!.
jevia.dev
try it out ;)
This will be epic. Can't miss.
The Multiplayer Coding Hackathon with @coshellhq and @assistantui @freestyle_dev @Wefunder
Sat Oct 3, SF. Free.
Teams of 2 to 5 build in one shared drive, steering live agent sessions together.
Sign up at:
luma.com/hacs1uig
real worktrees. 87% less disk. nothing to configure. native COW ( copy on write ) sharing.
Introducing riftri (riftri.dev)
- real Git worktrees ( native COW ) that don't each cost you a full checkout.
Spin up 10 worktrees for parallel agents or branches, and the unchanged files are shared at the filesystem level instead of copied.
assistant-ui retweeted
“AI coding gives everyone 80% of the result for 10% of the effort.
That 80% is no longer your edge. It’s the commodity.
The remaining 20% - taste, judgment, edge cases, review - is where all the alpha lives.”
Truth be spoken: The best engineers don't work less. In fact, we’re all suffering from AI psychosis right now, but we also ship 10x more.
Really enjoyed my conversation with @simonfarshid, Founder & CEO of @assistantui, on our latest convo of @coderabbitai 's The Merge.
This video is larger than Cloudflare's 512 MB cache, so it can't be played through. More donations are needed to cover a larger cache. Donate
assistant-ui retweeted
Building with @assistantui? OpenUI now has a dedicated integration.
Your agent can stream OpenUI Lang interfaces directly inside the conversation, from cards, tables, and charts to forms and choices that return structured input and continue the thread.
OpenUI generates the interface; assistant-ui provides the chat shell.
assistant-ui.com/docs/tools/…
assistant-ui retweeted
OpenUI now renders within @assistantui
Your agent can now generate interfaces or take structured input via real forms - all inside the most loved Agent UI framework. @KashyapVisharad cooked with this one!
assistant-ui.com/docs/tools/…
assistant-ui retweeted
15 reasons why you should just use @assistantui
What Makes a Great Streaming Chat Experience
Start here: Never move the reader against their intent.
1. Move only when the reader asked to move.
If someone is reading, don’t pull them somewhere else. Auto-scroll should never be the default.
2. Follow only while they’re following.
If they’re at the live edge, keep the stream in view. If they scroll away, leave them there.
3. Every interaction is intent.
Scrolling is not the only signal. Selecting text, using the keyboard, opening a link, searching should all stop the interface from moving.
4. Start a new turn near the top of the viewport.
This gives the new turn somewhere it can be read from the beginning.
5. Then stream in the answer.
The streaming answer can then grow into the available space.
6. Keep part of the previous conversation in context.
Enough of the previous turn should remain visible so the reader knows where they are. Context.
7. Let new content arrive offscreen.
The conversation can keep streaming without changing what the reader is looking at.
8. Show what’s happening out of view.
Make it clear when a response is still streaming or when new messages have arrived.
9. Make it easy to return to the latest reply.
A "Jump to latest" action should bring the reader back and resume following.
10. Let people jump anywhere in the conversation.
Long threads need message links, search, unread markers, and direct navigation.
11. Reopen where the reader left off.
A saved conversation should open at the last meaningful turn. This is usually the last user message. Not the absolute bottom.
12. Keep the reader’s place when layout changes.
Images load. Markdown expands. Code blocks render. Older messages appear above. None of that should make the reader lose their place.
13. Handle interruptions without stealing position.
Stopping, retrying, regenerating, branching, or errors should not unexpectedly move the conversation.
14. Stay responsive in long threads.
Streaming text, markdown, code, images, and long history should still feel responsive.
15. Be accessible without the noise.
Keep the transcript navigable, preserve keyboard focus, and announce important events at a comfortable pace.
It’s all about the scroll. Scroll Engineering.
assistant-ui retweeted
Here is the easiest way to implement your own harness for any vertical; it's so easy it feels like cheating :
- Typescript backend with mastra.ai/docs/harness/overv… from @mastra
- Typescript frontend with assistant-ui.com/docs from @assistantui
assistant-ui retweeted
most AI apps still don't use the full multimodal stack.
vision, audio, real-time processing. all largely untapped
we got you access to the latest @GoogleDeepMind models. if you've been wanting to build multimodal agents, this one's for you
🏆 $45K+ in prizes (up to $25K in credits alone)
📅 saturday march 28 · san francisco
apply below 👇
assistant-ui retweeted
Today, we are launching the redesigned assistant cloud Dashboard, with improved analytics and thread management
assistant-ui retweeted
We just shipped new docs showing how to wire @langchain/react's #useStream hook to any React UI library 🎉
Two ready-to-go integrations:
🧩 AI Elements: composable, @shadcn - ui-style components for chat
🤖 @assistantui: headless runtime with a full thread UI out of the box
📚 docs.langchain.com/oss/pytho…