Just curious, how can Deliberate exactly identify the options the agent faced?
and what do you consider an "option"?
sometimes it can be vauge (say the agent decided to explore this way and not that way, would that be considered an option?)
that's exactly what i tried in the first place, but i think it would be misuse of git protocol,
git is built for files - the blobs/ tree calc & mechanism ,
for large contexts and linear thinking flow it's differnt,
but honestly - i think you can get to a very good solution with pure git..
exactly,
imo - the llm should touch git only after explicit approval or after specific set of guardrails.
this one of the reasons i built it actually,
i think the agent workflow should be decoupled from git, until saving the code