Prevent unneed LM calls during /run - #67
ErichBSchulz wants to merge 11 commits into
Conversation
Co-authored-by: aider (gemini/gemini-2.5-pro) <aider@aider.chat>
Co-authored-by: aider (gemini/gemini-2.5-pro) <aider@aider.chat>
Co-authored-by: aider (gemini/gemini-2.5-pro) <aider@aider.chat>
Co-authored-by: aider (gemini/gemini-2.5-pro) <aider@aider.chat>
Co-authored-by: aider (gemini/gemini-2.5-pro) <aider@aider.chat>
Co-authored-by: aider (gemini/gemini-2.5-pro) <aider@aider.chat>
…task Co-authored-by: aider (gemini/gemini-2.5-pro) <aider@aider.chat>
Co-authored-by: aider (gemini/gemini-2.5-pro) <aider@aider.chat>
Co-authored-by: aider (gemini/gemini-2.5-pro) <aider@aider.chat>
|
ie relating to #65 |
|
Very nice, always appreciate contribution! I think I will adapt this to detect the run command specifically so it doesn't trigger a new processing task immediately since that's what ultimately calls the LLM. This current logic would actually detect all of the slash commands and output the running message for them |
|
Thanks Dustin! yes this is bit rough - I wasn't even sure how this new async approach's goals are so glad you can tweak this. I won't be offended if reject this PR! |
|
Arg and actually this is only a partial fix. My Gemini API still getting hammered by unwanted lm calls when it asks to add files. |
|
The 0.88.4 PR should address this, the gist of it is that to prevent confirmations from being treated as prompt inputs, I added acknowledgement logic so that we simply skip propagating the message for the turn of the main loop immediately after a confirmation |
Hi Dustin,
me and gemini had a go at this. Its not perfect but it is better!
let me know what you think.