[dead]
Ex-GitHub CEO launches a new developer platform for AI agents
351–360 of 625 posts
Re: Ex-GitHub CEO launches a new developer platform for AI agents
#352> Checkpoints are a new primitive that automatically captures agent context as first-class, versioned data in Git. When you commit code generated by an agent, Checkpoints capture the full session alongside the commit: the transcript, prompts, files touched, token usage, tool calls and more. This thread is extremely negative - if you can't see the value in this, I don't know what to tell you.
[flagged]
Re: Ex-GitHub CEO launches a new developer platform for AI agents
#353[dead]
Agent memory can sometimes be handled with prompts, state output on completion, etc. Managing that can get messy if you aren't on the same system.
I think "provenance gap" or temporal history can be helped by understanding what you have asked agentic systems to write, understand things written, and verified them.
We aren't yet at a point where something large or extended is easily pushed to agentic coding management - your point of provenance and memory is key here.
Re: Ex-GitHub CEO launches a new developer platform for AI agents
#354The thread is missing the forest for the trees. The interesting bet here isn't git checkpoints—it's that someone is finally building the observability layer for agent-generated code. Most agent frameworks (LangChain, Swarm, etc.) obsessed over orchestration. But the actual pain point isn't "how do I chain prompts"—it's "what did the agent do, why, and how do I audit/reproduce it?" The markdown-files-in-git crowd is r…
I thought everyone was just using open telemetry traces for this? This is just a classic observability problem that isn’t unique with agents. More important yes, but not unique functionally.
Can you explain more how otel traces solve this problem? I don't understand how it's related.
Re: Ex-GitHub CEO launches a new developer platform for AI agents
#355Earlier quoted context omitted.
Sure... you `git add` the context text generated by AI and `git commit` it, could be useful. Is that worth 60 million?
They raised 60 million. The investors think it’s worth 600M+
That's not impressive. That's an incredible amount concentrated in the hands of a few looking for a place to live. It has to end up somewhere. Some of it goes everywhere.
Re: Ex-GitHub CEO launches a new developer platform for AI agents
#356Earlier quoted context omitted.
This is literally what claude code already does minus the commit attachment. It’s just very fancy marketing speak for the exact same thing. I’m happy to believe maybe they’ll make something useful with 60M (quite a lot for a seed round though), but Maybe not get all lyrical about what they have now.
Claude Code captures this locally, not in version control alongside commits.
I wonder how difficult it would be for Claude Code to have such a feature in a future release.
Re: Ex-GitHub CEO launches a new developer platform for AI agents
#357> Checkpoints run as a Git-aware CLI. On every commit generated by an agent, it writes a structured checkpoint object and associates it with the commit SHA. The code stays exactly the same, we just add context as first-class metadata. When you push your commit, Checkpoints also pushes this metadata to a separate branch (entire/checkpoints/v1), giving you a complete, append-only audit log inside your repository. As a…
To add to your comment, I think the next logical question is, “then what?” Surely one can’t build a sustainable business storing these records alone.
Re: Ex-GitHub CEO launches a new developer platform for AI agents
#358[dead]
> The problem is that agent-written code has a provenance gap. When a human writes code, the reasoning lives in their head, in Slack threads, in PR descriptions. When an agent writes code, the reasoning evaporates the moment the context window closes.
The described situation for human-written code isn't much better. What actually works is putting a ticket (or project) number in the commit message, and making sure everything relevant gets written up and saved to that centralized repository.
And once you have that, the level of detail you'd get from saving agent chats won't add much. Maybe unless you're doing deliberate study of how to prompt more effectively (but even then, the next iteration of models is just a couple months away)?
Re: Ex-GitHub CEO launches a new developer platform for AI agents
#359> Checkpoints are a new primitive that automatically captures agent context as first-class, versioned data in Git. When you commit code generated by an agent, Checkpoints capture the full session alongside the commit: the transcript, prompts, files touched, token usage, tool calls and more. This thread is extremely negative - if you can't see the value in this, I don't know what to tell you.
I see the utility in this as an extension to git / source control. But how do VCs make money of it?
[deleted]
Re: Ex-GitHub CEO launches a new developer platform for AI agents
#360> Checkpoints are a new primitive that automatically captures agent context as first-class, versioned data in Git. When you commit code generated by an agent, Checkpoints capture the full session alongside the commit: the transcript, prompts, files touched, token usage, tool calls and more. This thread is extremely negative - if you can't see the value in this, I don't know what to tell you.
[flagged]
Look it’s obvious at this point to anyone who is actually using the tools.
We can articulate it but why should we bother when it’s so obvious.
We are at an inflection point where discussion about this, even on HN, is useless until the people in the conversation are on a similar level again. Until then we have a very large gap in a bimodal distribution, and it’s fruitless to talk to the other population.