Ex-GitHub CEO Launches a New Developer Platform for AI Agents

Oh man I'm tired. This reminds me of the docker era. It's all moving fast. Everyone's raising money. And 24 months from now it's all consolidating. It's all a nice hype game when you raise the funding but the execution depends on people finding value in your products and tools. I would argue yes many of these things are useful but I'd also argue there's far too much overlap, too many unknowns and too many people trying to reinvent the whole process. And just like the container era I think we're going to see a real race to zero. Where most of the dev tools get open sourced and only a handful of product companies survive, if that. I want to wish everyone the best of luck because I myself have raised money and spent countless years building Dev tools. This is no easy task especially as the landscape is changing. I just think when you raise $60m and announce a cli. You're already dead, you just don't know it. I'm sorry.

> The game has changed. The system is cracking.

Just say what your thing does. Or, better yet, show it to me in under 60 seconds.

Web sites are the new banner ads and headings like that are the new `<blink>`.

Think of all of the habit tracker and to do list apps we'll be able to make now!

A lot of frustration in this thread. It's okay to not jump on new technology. You can wait it out and let other marvelous people, like Simon Willison, jump on it first and condense it in a blog post.

We went from having new JavaScript frameworks every week to having new AI frameworks every week. I'm thinking I should build a HN clone that filters out all posts about AI topics...

> 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, recompile and re-test. I can review the code, as you would a Junior you're mentoring, and have it rewrite it in a specific pattern.

Funnily enough, I love Beads, but did not like that it uses git hooks for the DB, and I can't tie tickets back to ticketing systems, so I've been building my own alternative, mine just syncs to and from github issues. I think this is probably overkill for whats been a solved thing: ticketing systems.

This is a good idea but I feel like you could get something similar by just adding an instruction for the agent to summarize the context for the commit into a .context/commit/<sha> file as a git hook.

Actually interesting, but how's that different from just putting your learning / decision context into the normal commit text (body) ? An LLM can search that too, and doesn't require a new cli tool.

EDIT: Or just keep a proper (technical) changelog.txt file in the repo. A lot of the "agentic/LLM engineering frameworks" boil down to best approaches and proper standards the industry should have been following decades ago.

The context preservation problem is genuinely painful - I've been using task.md files and CLAUDE.md conventions to maintain agent state across sessions, and it's duct tape at best. First-class "checkpoints" that capture reasoning alongside diffs is an appealing idea.

But I'm skeptical of building this as a separate platform rather than as tooling on top of git. The most useful AI dev workflow improvements I've seen (cursor rules, aider conventions, claude hooks) all succeeded precisely because they stayed close to existing tools. The moment you ask developers to switch their entire SDLC stack, adoption becomes the real engineering challenge - not the tech.

Curious whether the open source commitment means the checkpoint format itself will be an open spec that other tools can build on.

"$60M Seed round"

I guess when you are Ex-Github CEO, it is that easy raising a $60M seed. I wonder what the record for a seed round is. This is crazy.

There is also Git AI: https://github.com/git-ai-project/git-ai https://usegitai.com/

This feels a bit like when some Hubbers broke off to work on PlanetScale, except without the massively successful, proven-to-be-scalable open source tool to build off (Vitess).

If you're approaching this problem-space from the ground up, there are just so many fundamental problems to solve that it seems to me that no amount of money or quality of team can increase your likelihood of arriving at enough right answers to ensure success. Pulling off something like this vision in the current red-ocean market would require dozens of brilliant ideas and hundreds of correct bets.

The founder has only forked repositories on GitHub that are sort of light web development related.

His use of bombastic language in this announcement suggests that he has never personally worked on serious software. The deterioration of GitHub under his tenure is not confidence inspiring either, but that of course may have been dictated by Nadella.

If you are very generous, this is just another GitHub competitor dressed up in AI B.S. in order to get funding.

This guy was the ex-ceo of GitHub and can't bother to communicate his product in a single announcement post?

disclosure: i run a startup that will most likely be competitive in the future.

I welcome more innovation in the code forge space but if you’re looking for an oss alternative just for tracking agent sessions with your commits you should checkout agentblame

https://github.com/mesa-dot-dev/agentblame

Wait, since when is Dohmke out? I thought this was gonna be Nat.

Just have a data lake with annotated agent sessions and tool blobs (you should already be keeping this stuff for evals), then give your agent the ability to query it. No need for a special platform, or SaaS.

As for SDLC, you can do some good automations if you're very opinionated, but people have diverse tastes in the way they want to work, so it becomes a market selection thing.

Checkpoints sounds like an interesting idea, and one I think we'll benefit from if they can make it useful.

I tried a similar(-ish) thing last year at https://github.com/imjasonh/cnotes (a Claude hook to write conversations to git notes) but ended up not getting much out of it. Making it integrated into the experience would have helped, I had a chrome extension to display it in the GitHub UI but even then just stopped using it eventually.

For people trying to understand the product (so far), it seems that entire is essentially an implementation of the idea documented by http://agent-trace.dev.

I'm interested to see if they will try to tackle the segregation of human vs AI code. The downside of agents is that they make too much changes to review, I prefer being able to track which changes I wrote or validated from the code the AI wrote.

My first thought that it was made for companies which tie "AI usage" to performance evaluation.

> Cursor's Composer 2.0

There is no Composer 2.0. There is Cursor 2.0 and Composer 1.5.

Its a shame Pierre shut down. Wish they could have made it work. Github but made by Linear would be a dream.

New agent framework / platform every week now. It's crazy how fast things move...just when you get comfortable with an AI flow something new comes out...

I don't see how we need a brand new paradigm just because LLMs evidently suck at sharing context in their Git commits. The rules for good commits still apply in The New Age. Git is still good enough, LLMs (i.e. their developer handlers) just need to leverage it.

Personally, I don't let LLMs commit directly. I git add -p and write my own commit messages -- with additional context where required -- because at the end of the day, I'm responsible for the code. If something's unclear or lacks context, it's my fault, not the robot's.

But I would like to see a better GitHub, so maybe they will end up there.

There have been so many GitHub CEOs I was excited to find out which one.

I really hate this trend of naming companies using dictionary words just because they can afford to spend cash on the domain name instead of engineering. Render, fly, modal, entire and so on.

> ... to Cursor's Composer 2.0 and more, ...

I couldn't find any references of Composer 2.0 anywhere. When did that come out?

Really struggling to figure out what this is at a glance. Buried in the text is this line which I think is the tl;dr:

"As a result, every change can now be traced back not only to a diff, but to the reasoning that produced it."

This is a good idea, but I just don't see how you build an entire platform around this. This feels like a feature that should be added to GitHub. Something to see in the existing PR workflow. Why do I want to go to a separate developer platform to look at this information?

Not sure what it is or what it does.

[dead]

[dead]

[dead]