I want to bring this issue from upstream to your attention: Aider-AI#3085
And, more specifically this comment here: Aider-AI#3085 (comment)
In case of the current aider-ce, that request is partially outdated because here the user can still reject a proposed edit change, but I would push it further to letting the user surgically edit the proposal before moving on, and do that both in architect and code modes.
I would propose this workflow:
- user makes a request
- architect makes a high level proposal
- user can either accept the proposal, or request a change, or (this!!) edit the proposal themselves in the CLI editor of choice.
- once the proposal is final, editor makes a code change proposal
- user can either accept it, or request a change, or (this!!) edit the code diff themselves (the replace blocks only) in the CLI editor of choice
- once the user accepts, the diffs are applied
This would prevent a lot of back and forth, and also alleviate a lot of token usage when proposals cannot be immediately accepted.
Let me know if something like this is already possible here and I just missed it.
I want to bring this issue from upstream to your attention: Aider-AI#3085
And, more specifically this comment here: Aider-AI#3085 (comment)
In case of the current aider-ce, that request is partially outdated because here the user can still reject a proposed edit change, but I would push it further to letting the user surgically edit the proposal before moving on, and do that both in architect and code modes.
I would propose this workflow:
This would prevent a lot of back and forth, and also alleviate a lot of token usage when proposals cannot be immediately accepted.
Let me know if something like this is already possible here and I just missed it.