Grant

@robinebers @crsmoore @screenstudio @TellaHQ You should come try it out again. Lots of updates and hopefully better stability compared to your last experience (sorry about that).

@crsmoore @screenstudio @TellaHQ haven’t in recent months but they pissed me off early so hard that i never went back (they lost an entire project and multiple hours of work)

just re-subscribed to @screenstudio and I genuinely wish I didn't have to have lifetime licenses for multiple alternatives tested them all, but none is as polished yet screen studio is overpriced and ships way too slowly for 2026 but it's STILL the best screen recorder out there gave them one more year by then the competition will have beaten it, no doubt remember: time is more valuable than money if a tool saves you hours every week, just pay for it and move on

@raunofreiberg Man this is it

Conversation minimap for the new Vercel Support chat interface

.@happylinks and I are hosting our first @TellaHQ Community Office Hours next Tuesday! Drop in, ask questions, show what you're working on, or just chat. RSVP 👇 community.tella.tv/c/events/commu…

@thomaspaulmann This looks incredible. Amazing work guys.

Your computer, finally personal. Today we're launching Glaze, the second product in Raycast's history. It's a big moment for us, and I want to share the thinking behind it. Something is fundamentally changing about software. We see it every day inside our own team. People who never wrote a line of code are now contributing directly to our codebase. The barrier between "having an idea" and "making it real" is collapsing. And that changes everything. For six years, we've obsessed over what makes a great desktop app. The speed. The polish. The feeling of something that truly belongs on your computer. We've poured that into Raycast, and hundreds of thousands of people use it every day. But all that knowledge was locked inside our team. With Glaze, we're commoditizing it. Everything we've learned about building beautiful, capable desktop apps is now available to everyone. Tell Glaze what you want and it builds a real app that lives in your dock or taskbar. It launches instantly, works offline, and taps into the full power of your desktop. Beautiful by default and personal when you want it to be. It's fun for individuals and works just as well for teams. Our support team built a Glaze app connected to GitHub that runs their entire extension review workflow. Others have built dozens of internal tools. When you can shape software around how your team actually works, everything clicks. Here's what gets me most excited: we think Raycast becomes even more important in a world full of Glaze apps. Glaze apps will be deeply integrated with Raycast, connecting them all together in ways nobody else can do. The two products make each other better. A small team started building Glaze from scratch last summer. What they've shipped in that time still blows my mind. When we started Raycast, we set out to change how people use their computers. Glaze is the next chapter of that mission. We're opening the private beta today, March 4th. Mac only to start. Existing Raycast users will get priority access soon. We can't wait to see what you create and I’ll share some of my apps over the next couple of days. 💠

ICYMI: now live! you can file @linear issues directly from your @TellaHQ video record bug in Tella -> send to Linear to be fixed by an agent (or human!)

@grinich Congrats @grinich and team!

Make @linear issues for your agents, directly from a screen recording

@andupoto I stopped using React Grab and just ended up bashing out visual changes with prompts. You kinda get used to it after a while. Would like to try Agentation tho!

@9ranty It looks like you're in need of agentation.dev. React Grab probably is a version of this same thing.

I'm rebuilding the Tella marketing site with Claude Code. The site is currently built with Framer. It's very work-in-progress, but I thought I'd write down how I'm finding the process. Because it's not all "Build this website. Don't make mistakes." Right now I'm at the point where I'm taking fairly hi-fi Figma designs and getting Claude to code them. I use Figma's MCP so that Claude can look at the design and try to recreate it. Claude is still not great at interpreting Figma files. It gets lots of seemingly obvious things wrong. Either that, or Figma's frame structure doesn't convert well to divs in some places. Also, unless your Figma file is super polished - i.e. you've got auto layout frames that mirror the correct relationships and behaviour as you'd find on the web, then you'll end up with strange implementations that you have to fix later via Claude (or in the code). I forgot auto layout on a few deeply nested layers and Claude just chucked on some fixed widths. This broke basic responsiveness in parts of the site. Overall, Claude Code + Figma MCP can give you a solid site layout very fast. Just be prepared to tweak a lot of stuff afterwards. So onto tweaking. Tweaking a design via command line prompt is hard. It feels weird. You have to convert a visual idea into words. On top of this is the annoying process of knowing what to call certain parts of the site. "on this div", "for this container", "in the parent div of the other div we were talking about earlier" - maybe I just don't know enough about code to know a better way of doing this, but it doesn't feel right. Anyway, some smart people are working on this problem. I've been using React Grab for Claude Code to help with this. It's neat. Add it to your codebase and then you get an inline pointer on localhost to select elements and prompt your change right there. No need to guess what div or container or element you're talking about. React Grab has been handy for small changes. It's still not fast enough for it to feel great yet (I'm even using the smaller Haiku model for this), but you can stack a bunch of changes. "Make this smaller", "Change the colour of this", "Remove this". But React Grab is very new and I've run into some issues. The main thing is that it's not integrated with my Claude Code terminal session. I'm doing all the big stuff there. All my context is there. All Claude's context is there. React Grab is using some separate instance of Claude. It feels like asking two people on your team to work on the same project without them knowing the other person is working on it. The other thing is that selecting elements still feels clunky and inaccurate. I've found some elements that I can't even select. I've also asked it to change something on one element and then in it's little thinking log I can see it say "I don't see this element here, let me look elsewhere!" and then it goes and changes the wrong element. Anyway. It's a neat tool that does the job most of the time, and it'll get better. I'm mostly making this as a point about how early everything is. Occasionally I'll open Cursor to actually look at the code when things get too tricky inside the browser inspector. But if I'm running Claude in the terminal then it feels overkill to use Cursor as text viewer/editor. I kinda want a lightweight AI IDE that's connected to Claude Code and I can occasionally use to edit or prompt. I'm sure this exists already. But then again, why not just do this on the live site via future-version-of-React-Grab. Once I figured out when to ask Claude and when to use React Grab. And once I prompted the layout to death to match my original design, then I was finally able to do some crazy shit. Claude can rebuild mocks of Tella's actual UI and embed them on the site as interactive demos. Iterating on animated sections and interactive elements is so fast. "Try this order", "Try that order", "When I click on this transition to that". Feels great. Anyway. I'm still on the first page of the site and there are a lot of pages to go. And I haven't even thought about the CMS yet. Will let you know how it goes.

@okuiux @johnnylinsf @grant x.com/9ranty/status/…

@johnnylinsf I thought Tella was a video creation tool @grant ?

wow so i just read Loom’s pricing changes and it’s quite a dramatic increase for most orgs tldr: they’re getting rid of creator lite seats and automatically upgrading all of those seats to a full paid seat with a grace period if you don’t take any action the breakdown of that is: let’s say you have 100 users, you’re now gonna pay $24k/year for all your users. so if you only had 10 video creators and 90 other team members who rarely record or just view videos internal to your workspace you’ll go from $240/year to $24,000/year after your “first billing date after your integration with Atlassian” 🤯 ✌️ support.atlassian.com/loom/docs/loom…

Send me or Johnny a DM if you want help moving to @TellaHQ

The team (and agents) went to town on this one. Get YouTube-level analytics on every product announcement, help doc, sales video etc.

best headline i've seen in a while

@peer_rich sometimes you want a late night coke without wrecking your sleep

people drinking this purely for the love of the game

this sounds like a shreds

@swyx the comparison is weird tho vogue and newspapers are consumer media the willingness of consumers to pay for media went to zero but arguably the willingness of consumers to pay for software has also been zero for a while

The End of Software (2024)

this is what lunch break at most NZ schools looks like

this is what it should be... but it's all just wood

that friday feeling

perfection

we're entering the "hi I'm a Mac... and I'm a PC" stage