A lot of people seem confused about how they raised the money, but it’s actually a pretty easy VC pitch.

- It’s from one of GitHub’s cofounders.

- GitHub had a $7.5B exit.

- And the story is: AI is completely changing how software gets built, with plenty of proof points already showing up in the billions in revenue being made from things like Claude Code, Cusor, Codex, etc.

So the pitch is basically: back the team that can build the universal infrastructure for AI and agentic coding.

▲

mohsen1 7 hours ago | parent | next [-]

I watched video to see where my prompts etc are stored in a way that makes sense. But no, this is just a nicer git. We need a solution to all these 10k loc PRs.

	▲	dirkc 6 hours ago \| parent \| next [-]
		Another comment [1] has a solution - a new tool called pit, it just throws the whole 10k loc PR in a pit and forgets about it :p [1] - https://news.ycombinator.com/item?id=47713650
	▲	oofbey an hour ago \| parent \| prev [-]
		Agreed. Although I’m not sure what’s nicer about it. It’s in color. But I failed to understand why I’d want any of those features.

▲

conartist6 an hour ago | parent | prev | next [-]

I think I have just as good a shot at building what comes after git as their team does, and perhaps quite a lot better.

I'm not famous though, I'm just a good engineer who is patient, inquisitive, and determined enough to spend the last five years of my life on nothing but this.

My question is: say the investor believes that some new platform will win out over Github. How do I make the case that it will be mine over a famous person's?

▲

jgauth 7 hours ago | parent | prev | next [-]

Makes sense to me. The new coding agents are drastically changing software development, and I think there's a lot of space for innovation in how version control tooling works in this new world.

▲

progx 7 hours ago | parent [-]

Why should ai need this? A linear backlog is enough, a cache, for everything else they can create it new in a short time.

▲

jcfrei 5 hours ago | parent [-]

Another commenter explained it: It's about working on multiple branches in parallel. You can only check out one branch at a time currently in git - but with "but" you have all the changes just in memory so different agents can work on different branches at the same time.

	▲	leadingthenet 4 hours ago \| parent \| next [-]
		git-worktree has been a thing for a decade+ and AI agents seem to be using them just fine in my experience. This is a solved problem.
	▲	dbbk 2 hours ago \| parent \| prev [-]
		That's not even true

▲

IshKebab 6 hours ago | parent | prev [-]

They actually started before the LLM craze. The original pitch was just better Git.