Comment by jjcm
20 hours ago
What I don't understand from the blog post is what's different in this offering than github - is it just the agentic tie ins where I can ask my agent to make changes while browsing the PR?
Are there any fundamental differences, ie ways of working that solve the worktrees problem?
Expect a lot more from us.
We wanted to release a beta so people could start experimenting with our scalability and extensibility themselves. Over the next few weeks, you can expect a handful of features starting to change source control to better understand and work with agents.
Are there any plans for compatibility with GitHub's APIs?
I have a lot of dev tooling which assumes code is stored on public GitHub and/or GitHubEnterprise. This produces some degree of lock-in, in that all that code would have to be rewritten to migrate to something else. (Yes, AIs can help, but they still don't make migration effortless.)
The major Git hosters tend to implement roughly the same concepts, albeit with lots of little variations. It would be great if there were some sort of standardised API everyone implemented. In the absence of that, it makes sense for people to emulate the incumbent's APIs as a de facto standard, just like how other vendors copy OpenAI's APIs for talking to LLMs.
There seems to be basically nothing new here
The idea is that it's like Github but it stays up even as your commit/CI frequency increases. As a customer I'm stoked and looking forward to fully switching over as that's exactly what I want.
Calling it a GitHub that works is just preposterous. Cursor/spacetwitterai have no experience keeping a system like that up.