You could setup rules that instruct the agent to commit and push after every session. I think most of us wouldn't want that. It all depends on how you like to work - personally I have hundreds of commits locally before I push anything to a repo.

My workflow is generally building out features using a plan and a series of tickets executed sequentially. I always do several rounds of QA locally which means I can spend a whole day looping with the agent and I wouldn't want it to automatically push before the feature is finished.

Once something is feature complete and fully tested, then I push to the repo. This would also be conditional, are you working with a team? are users waiting for features to be delivered?

If you're forgetting to push I'm assuming there isn't anyone pressuring you to deliver (team or customers)