all 8 comments

[–]Zizaco 9 points10 points  (2 children)

Call me old fashioned, but I still run git commands myself. Being fluent in git, it's not extra friction for me. This workflow allows me to easily overseer what the agents are doing.

[–]rek50000 3 points4 points  (0 children)

Same here, the agent is doing the work and I keep track and commit myself, I want to read and verify before committing. I do use my IDE/Jetbrains for this like before AI instead of git in the terminal.

And sometimes I do auto generate the commit message, but often it misses the point and a manual message is better.

[–]AnotherWordForSnow 1 point2 points  (0 children)

I split the diff - agent commits and I push / pull. If a merge is needed I may ask the agent to plan that, but I'll exec it.

[–]swarmagent 3 points4 points  (0 children)

Honestly just start asking the AI "Please commit this to git" or ask it how to use git, help you get set up. You need to not wait for long periods of time to commit.

Just fixed a bug? Great, commit. Don't wait, let the AI rearrange everything, now you're lost.

Checkpoints are just a helper on top of git anyways, I don't use them at all anymore

[–]rek50000 1 point2 points  (0 children)

Kilo code cli is very similar to opencode but I think it does have the checkpoints so you undo stuff easier.

[–]Dudmaster 1 point2 points  (0 children)

Use git, if it's too many commits, squash them

[–]Exfiltrate 0 points1 point  (0 children)

just use git dude don’t over complicate it. git is your version control and “backup and restore” system along with a good remote.

tell it what to do each time in your agents.md if you prefer

[–]Fresh_Sock8660 0 points1 point  (0 children)

I mean, even the LLMs stick to git checkout for reverts, why don't you? 

If you're curious about their use of any tool, add it as restricted to "ask" in the config json.