4 ms·

Thanks for mentioning aider! I haven't had a chance to look closely at plandex, but have read the author's description of differences wrt aider. I'd add a few c

Thanks for mentioning aider! I haven't had a chance to look closely at plandex, but have read the author's description of differences wrt aider. I'd add a few comments: I think the plandex UX is novel and interesting. The idea of a git-like CLI with various stateful commands is a new one in this space of ai coding tools. In contrast, aider uses a chat based "pair programming" UX, where you collaborate with the AI and ask for a sequence of changes to your local git repo. The plandex author highlights that it makes changes in a "version-controlled sandbox" and can "rewind" unwanted changes. These capabilities are all available "for free" in aider, because it is tightly integrated with git. Each AI change is automatically git committed with a sensible commit message. You can type “/diff” to check the diff, or "/undo" to undo any AI commit that you don't like. Or you can use "/git checkout -b <branch-name>" to start working on a branch to explore a longer sequence of changes, etc. All your favorite git workflows are supported by invoking familiar git commands with "/git ..." inside the aider chat, or using any external git tooling that you prefer. Aider notices any changes in the underlying repo, however they occur.

bjornsing 3y ago
> These capabilities are all available "for free" in aider, because it is tightly integrated with git. Sounds like the right approach to me. Some quick questions: 1. Is it easy to customize the system prompt with aider? 2. Does aider save a record of all OpenAI API calls? I’m thinking I may e.g. want to experiment with fine tuning an open source model using these one day. 3. What would you say are aider’s closest “competitors”?
- danenania 3y ago
  Just to note, Plandex also has integration with git on the client-side and can automatically commit its changes (or not--you can decide when applying changes). One of the reasons I think it's good to have the plan version-controlled separately from the repo is it avoids intermingling your changes and the model's changes in a way that's difficult to disentangle. It's also resilient to a "dirty" git state where you have a mix of staged, unstaged, and untracked changes. One more benefit is that Plandex can be used in directories that aren't git repos, while still retaining version control for the plan itself. This can be useful for more one-off tasks where you're not working in an established project.

bjornsing 3y ago

> These capabilities are all available "for free" in aider, because it is tightly integrated with git. Sounds like the right approach to me. Some quick questions: 1. Is it easy to customize the system prompt with aider? 2. Does aider save a record of all OpenAI API calls? I’m thinking I may e.g. want to experiment with fine tuning an open source model using these one day. 3. What would you say are aider’s closest “competitors”?

danenania 3y ago
Just to note, Plandex also has integration with git on the client-side and can automatically commit its changes (or not--you can decide when applying changes). One of the reasons I think it's good to have the plan version-controlled separately from the repo is it avoids intermingling your changes and the model's changes in a way that's difficult to disentangle. It's also resilient to a "dirty" git state where you have a mix of staged, unstaged, and untracked changes. One more benefit is that Plandex can be used in directories that aren't git repos, while still retaining version control for the plan itself. This can be useful for more one-off tasks where you're not working in an established project.