i made a clone of beads in rust that uses CRDTs for real time sync to coordinate a bunch of coding agents at the same time! if running locally, it's instant, for git it takes around .6s after your last action. lives entirely in git, and is like... an actual distributed database/issue system, just works, and u never gotta think about it.

https://github.com/delightful-ai/beads-rs/tree/main

it doesnt control for skill using models/experience using models. this looks VERY different at hour 1000 and hour 5000 than hour 100.

Lazy from me to not check if I remember well or not, but the dev that got productivity gains was a regular user of cursor.

unfair characterization.

think about how this thing is interacting with your codebase. it can read one file at a time. sections of files.

in this UX, is it ergonomic to go hunting for patterns and conventions? if u have to linearly process every single thing u look at every time you do something, how are you supposed to have “peripheral vision”? if you have amnesia, how do you continue to do good work in a codebase given you’re a skilled engineer?

it is different from you. that is OK. it doesn’t mean its stupid. it means it needs different accomodations to perform as well as you do. accomodations IRL exist for a reason, different people work differently and have different strengths and weaknesses. just like humans, you get the most out of them if you meet and work with them from where they’re at.

could u share some more intuition as to why you started believing that? are there ANY comments that are useful?

for the love of the mf game. most fun i’ve had with computers in my whole life

very very cool .

yes but ud ideally want ur own high uptime mac mini

Got it. But you could just use it on your MacBook on those occasions where you want to "talk" to your computer remotely to check on some progress it made on a specific job. My use case would involve switching desktops, activating specific windows, and reading their content and taking some action. But depends more specifically on the MCP that exposes that functionality, and not your app. I was asking because you're probably more familiar on how reliable such an approach might be.

heya, building this. been used in prod for a month now, has saved my customer’s ass while building general workflow automation agents. happy to chat if ur interested.

darin@mcptesting.com

(gist: evals as a service)

writing an essay on this if you'd be interested in reading a rough draft. i believe this very strongly and i think it's the UX that got us here and it's UX that'll take us out.

quintessential hacker news comment. thanks for this.