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

Oct 4, San Francisco luma.com/build-agents

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.

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.

Introducing Prism, a free workspace for scientists to write and collaborate on research, powered by GPT-5.2. Available today to anyone with a ChatGPT personal account: prism.openai.com/