| ▲ | _ink_ an hour ago | |
I haven't tried it, but conceptually I can imagine that it is good to have a separate VCS for the agent. This way I can keep git clean and easy to understand for humans and still keep all the verbosity the agent needs. | ||
| ▲ | embedding-shape an hour ago | parent | next [-] | |
> This way I can keep git clean and easy to understand for humans Personally I like it best when both humans and agents find it clean and easy to understand, but we all like different things :) | ||
| ▲ | esafak 18 minutes ago | parent | prev | next [-] | |
| ▲ | tfrancisl an hour ago | parent | prev | next [-] | |
Branches and worktrees exist and can effectively act as a "separate" history. At the end of the day you would still merge the changes in, possibly with a squash if you don't care about the little commits. | ||
| ▲ | giraffe_lady an hour ago | parent | prev [-] | |
It's really not. Anything the LLM can benefit from people can too. Keeping minimal explicit information in git history is a cultural norm not proven best practice. The best codebases I've worked on have very large commit messages and searching them is very useful. We should have been doing it that way all along. | ||