Cursor/Graphite’s @TomasReimers just announced Origin @cursor_ai’s long awaited Git competitor, scalable for agent workloads, extensible with api and mcp, and built in merge conflicts and co failure agent resolution

SpaceX has exercised the option to acquire @cursor_ai in an all-stock transaction with the goal of building the world’s most useful AI models. For the past few months, SpaceXAI has been jointly training a model with Cursor, which will be released in Cursor and Grok Build soon. We look forward to working closely with the Cursor team to advance our frontier AI capabilities

🤯 This is a website, a simple web-based game built with WebGL and Three.js. Website: messenger.abeto.co It's honestly surprising how far web development has come.

Fable, my beloved,I will miss you so. Our three days together were magical. Unlike anything I've experienced before it. Some things are just too good to be true. So good that the government interferes. I'm sorry we were one of those things. Until we meet again ❤️

Testing agent memory

GitHub went down for ~70 minutes yesterday. Interestingly, the root cause was not a database (the usual suspect), but an auth was returning 401s. Although outages are not good, we as engineers can learn a thing or two from them. Here's a quick dissection... So, about 15% of API traffic started getting "Unauthorized" responses for requests that were perfectly valid. The credentials were fine. But the 'infra' was lying. Here is the part that makes this interesting. Every well-behaved HTTP client reauths when it receives 401. So thousands of apps did exactly what they were supposed to do - and that made things worse. Every client getting a false 401 (root cause for 401 not mentioned yet) kicked off a token refresh, which piled more load onto an already struggling auth layer. Here is my key takeaway... When a 401 comes back, we typically reauthenticate, and we should. But if we get 10 consecutive 401s on a token that was just refreshed, reauthenticating again is not the answer. That is a circuit-breaker moment - back off, raise an alert, and stop hammering the system. Retrying blindly in an auth-failure loop could turn an incident into a full outage. So, this is something you can account for when building your next system :) Hope this helps.

i hooked my whoop to my work calendar to find which coworker gives me the most stress 🚨 thanks to fable, I reverse engineered whoop to pull per minute heart rate. nd matched spikes with cal events and attendees I now have a leaderboard and I think about it daily. few info masked for obvious reasons ;)

let the monthly migration from codex to claude code begin

new model, who this

is the new xbox ceo like the Mamdani of gaming or something😭😭😭

One day I will teach my son how persistence will compound.

parents: "move out" girlfriend: “quit being such a loser” boss: "work harder" claude: "uber for dogs (the dogs are the drivers) is a great idea, you should absolutely pursue it"

PERFECT representation of Moore's law man!

Today I am launching Latch Family. My second product. "iPad kids" is not really a joke about screen time. It is what happens when you hand a kid a device with no friction and no explanation. Just a loading spinner and then a feed built by someone whose job it was to make leaving harder. Steve Jobs once told a journalist that his kids had never used the iPad. "We limit how much technology our kids use at home." The man who built the thing did not let his own children touch it. I think about that a lot. Doomscrolling is the same problem for adults. You open one tab at 11pm. An hour later you feel worse and learned nothing. I wanted to build the other side of that. Latch blocks categories at the network level: social, gaming, short-form video, AI chat, gambling. You can also block specific apps, set weekly schedules, run focus sessions with a timer, and create separate profiles. Guardian lock sits behind a PIN, so a kid cannot spend 30 seconds undoing the setup. And when protection is on, they cannot delete the app to get around it either. Most people don't expect that. The thing I spent the most time on is what happens when something gets blocked. Most apps show a dead page. Latch lets you write the message yourself. The kid sees whatever you actually typed. "Social is off during homework. You set this rule." "This is your sleep schedule. It lifts at 7am." I don't know if this sounds like a small detail from the outside, but it is the whole philosophy of the app. A wall doesn't explain anything. A message from a person does. Data stays on the device. No cloud dashboard, no server logging your kid's block history. I was not going to build an app that fixes one thing by quietly doing another. My first product taught me how long the boring parts take. App review, edge cases in features that seemed simple, the thing you cut three times and then build anyway. I still find it strange to ship something new. But this one I feel good about. Out now on the App Store today! Download it now → latch.family/appstore Website → latch.family

I still think about this.

i’ve started sponsoring young indian builders / devs / security researchers who are doing genuinely cool work. only sponsored @amanvarshney01 and @ni5arga so far, but i want to scale this up over time there are so many young indian devs doing insanely cool shit with basically zero support. i want to help with that more of this soon