I built a markdown editor where your notes + skills.md + agents.md live together
introducing Glyph
1/3 lightning fast ⚡
no lag, instant switching, feels native
Introducing terminal-code: VS Code inside the terminal
- VS Code compatible CLI
- works over ssh
- syncs with your terminal theme
https://t.co/j3HThPdVPw
Introducing Grok Bot, now in early beta.
Bots are AI teammates that do real work for you. They sign in to your tools, use them just like you do, and come back with finished work.
Launching Copper, a Mac app for capturing things you want to keep and prompts you want to try next while working with AI.
The more I use AI, the more I find myself collecting little things I don't want to lose.
You're in ChatGPT and think, "I'll need this later," but you don't want to stop what you're doing. Then you're in Claude. Cursor. Chrome. Back to ChatGPT.
Before long, you've got little things scattered everywhere. An answer you want to keep. A link. An idea. Or three follow-up prompts before the current one has even finished generating.
I had this problem, so I built Copper.
Copper combines the useful parts of a to-do list, a clipboard, and a scratchpad. It's built specifically for AI-assisted work. It sits next to where you work and is always one shortcut away. It works with all your AI apps, terminals and browsers.
Whenever I find something worth keeping, I capture it. If I think of a few prompts while the AI is still responding, I type them into Copper. Then I send them back into ChatGPT, Claude, or Cursor and check them off as I go.
Copper is local and private. It doesn't sync anything, doesn't collect anything, and doesn't need an account.
I've used Copper every day for the past few months. It has completely changed how I work.
If this feels like something you'd use, it's $39. One-time purchase.
I've started a new company: @superlogical! We're going to begin by building a terminal multiplexer. The entire vision is much larger, but the multiplexer is the foundation. Sign up for the newsletter to get beta access and devlogs (product updates only I promise).
https://t.co/XJuqufkmCd
raycast + herdr = never losing an agent again
I run agents in @herdrdev all day. often 5+ at once
so I built a @raycast extension: shortcut -> herdr agents -> focus.
from anywhere.
We just beat the best frontier models at a quarter of the price. Now you can too, in one API call.
Today we're launching Merge Fusion.
Send one prompt to a panel of models, and a judge writes one answer better than any of them alone.
Fusion beats Fable 5 outright at 1/4th the cost. It also sets the highest score on the DRACO benchmark.
meet silk mulberry 1.5, a voice model built to outperform expectations.
- 162ms end-to-end latency - replies before you finish reading the message.
- matches elevenlabs v3 on the MOS benchmark while being 95% cheaper. (₹0.40/min vs ₹9.40/min)
⁃ you don't pick a voice, you design one - describe the age, accent, pitch, emotion, whatever you want, only limit is your imagination.
- mid-sentence language switching across 20+ languages with native accents, plus expressive range (whispers, singing and much more)
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.