Live data from Hacker News

Ex-GitHub CEO launches a new developer platform for AI agents

entire.io

171–180 of 625 posts

Re: Ex-GitHub CEO launches a new developer platform for AI agents

#171

> Spec-driven development is becoming the primary driver of code generation. This sounds like my current "phase" of AI coding. I have had so many project ideas for years that I can just spec out, everything I've thought about, all the little ideas and details, things I only had time to think about, never implement. I then feed it to Claude, and watch it meet my every specification, I can then test it, note any bugs,…

Task management is fundamentally straightforward and yet workflow specific enough that I recommend everyone just spend a few hours building their own tools at this point.

Beads is a nightmare.

Re: Ex-GitHub CEO launches a new developer platform for AI agents

#173
post #167

[flagged]

Are people doing this thing now where they can't even judge a product, website by themselves? Or read and analyze anything without asking an LLM to do it for them.

2026: The year everyone fried their brain with Think for Me SaaS.

Re: Ex-GitHub CEO launches a new developer platform for AI agents

#174

Earlier quoted context omitted.

You know the only effective way to do that, right?

Claude create a clone of Hacker News, no mistakes. Must compile.

Just give me your bank account, claude API, Mother's maiden name, your zip code, your 3 digit security code, and anything else you think I might need to live as malfist the magnificant. Can I call you that?

Re: Ex-GitHub CEO launches a new developer platform for AI agents

#175

Agents can save their reasoning into markdown files, and commit those files to Git. Are "Checkpoints" just a marketing term for that, or there's more to it?

Claude Code already does this, you can access it with /resume, /rewind and /fork. I'd imagine building a version that saves in the repo instead of in the home folder would take very minimal effort.

Re: Ex-GitHub CEO launches a new developer platform for AI agents

#176
post #167

[flagged]

Are people doing this thing now where they can't even judge a product, website by themselves? Or read and analyze anything without asking an LLM to do it for them. 2026: The year everyone fried their brain with Think for Me SaaS.

Try driving without google maps. Its a slippery slope we common folks we are in and there is no coming back - except for few purists..

Re: Ex-GitHub CEO launches a new developer platform for AI agents

#177
post #167

[flagged]

This is what Claude had to say about your comment if we're doing this now:

Imagine being so intellectually lazy that you can't even be bothered to form your own opinion about a product. You just copy-paste it into Claude with "roast this" and then post the output like you're contributing something. That's not criticism, that's outsourcing your personality to an API call. You didn't engage with the architecture, the docs, the use case, or even the pricing page — you just wanted a sick burn you didn't have to think of yourself.

Re: Ex-GitHub CEO launches a new developer platform for AI agents

#179

>CLI to tie agent context into Git on every push. Is this the product? I don't want to jump on the detractor wagon, but I read the post and watched the video, and all I gathered is that it dumps the context into the commit. I already do this.

I have it (claude, codex) summarise what we've discussed about a design, big change, put it in an MD file and then I correct it, have it re-read it and then do the change. Then later if it goes off piste in another session tell it to re-read the ADDs for x, y and z. If someone could make that process less clunky, that would be great. However it's very much not just funnel every turd uttered in the prompt onto a git b…

[dead]

Re: Ex-GitHub CEO launches a new developer platform for AI agents

#180

Earlier quoted context omitted.

Isnt this overloading git commits too much ? Like 50kb per commit message

Git is totally fine keeping a few extra text files. These are ephemeral anyway. The working sessions just get squashed down and eliminated by the time I've got something worth saving anyway. At that point, I might keep a overview file around describing what the change does and how it was implemented. (I will give the agent boom a bit of credit: I write a lot more documentation now, because it's essentially instructio…

the git commits message description never go away though, unless you're editing the git with BFG cleaner
Post reply on HN