Live data from Hacker News

How version control will evolve for the agent boom

entire.io

71–72 of 72 posts

Re: How version control will evolve for the agent boom

#71
post #22

Earlier quoted context omitted.

Hi! I work at Entire. We actually have another feature that we announced called Trails which indicates Confidence, Risk, Drift of code changes to give the maintainer more confidence that the code is high quality. Each of those signals -- confidence, risk, drift are determined by a workflow file that the maintainer can create. And trails continuously evaluate every time a change is made. So that's exactly what we're d…

Who would trust the classifiers, though? I would not. A team of professionals will trust a gateway they built themselves -- by an AI, most likely, as that is boring work -- that works for their organisation and whatever weird quirks and house styles they have. In a year or two when things are a bit more stabilised that'll be dozens of subagents each testing a little thing each in isolation plus a bevvy of software th…

classifiers are determined by the team that's working on the repo. Not by us! They're configuration files..like how in CI/CD you write a workflow file that needs to have passing tests. Same thing.

Re: How version control will evolve for the agent boom

#72

We need to store CHOICES with the commit or branch. Not the whole session. Conscious, summarized choices

we store the whole session but with tools to query the summarized choices. It's not intended for the user to sit there and read through the whole session. The session acts as metadata.
Post reply on HN