2 ms·
So it's looking like it's only running in the cloud, that is it will push commits to my remote repo before I have a chance to see if it works? When I'm using a
by yanis_t 1y ago
So it's looking like it's only running in the cloud, that is it will push commits to my remote repo before I have a chance to see if it works?
When I'm using aider, after it make a commit what I do, I then immediately run git reset HEAD^ and then git diff (actually I use github desktop client to see the diff) to evaluate what exactly it did, and if I like it or not. Then I usually make some adjustments and only after that commit and push.
- flakiness 1y agoYou can think of this as a managed (cloud) version of their codex command line tool, which runs locally on your laptop. The secret sauce here seems like their new model, but I expect it to come to API at some point.
- codemac 1y agowatch the live stream, it shows you the diff as the completed task, you decide whether or not to generate a github pr when you see the diff.
- danielbln 1y agoYou may want to pass --no-auto-commits to Aider if you peel them off HEAD afterwards anyway.
- TechDebtDevin 1y agoThis takes all the soul out of programming, not sure why anyone likes to use llms like this.
- sumedh 1y agoBecause from a business point of view, they just want a feature to be built, they really care about the code if it works.
- sagarpatil 1y agoIt generates a PR. You decide if you want to merge, clone it locally, test, edit and then merge the code.