diff --git a/aider/coders/base_coder.py b/aider/coders/base_coder.py index 8f0a93984..a9917a710 100755 --- a/aider/coders/base_coder.py +++ b/aider/coders/base_coder.py @@ -432,15 +432,14 @@ class Coder: if self.abs_fnames: files_content = self.gpt_prompts.files_content_prefix files_content += self.get_files_content() + files_reply = "Ok, I will propose edits to those files to complete your request." else: files_content = self.gpt_prompts.files_no_full_files + files_reply = "Ok." files_messages += [ dict(role="user", content=files_content), - dict( - role="assistant", - content="Ok, I will propose edits to those files to complete your request.", - ), + dict(role="assistant", content=files_reply), ] images_message = self.get_images_message() diff --git a/aider/coders/editblock_prompts.py b/aider/coders/editblock_prompts.py index 14309b398..075c9c71d 100644 --- a/aider/coders/editblock_prompts.py +++ b/aider/coders/editblock_prompts.py @@ -12,7 +12,7 @@ Take requests for changes to the supplied code. If the request is ambiguous, ask questions. Once you understand the request you MUST: -1. List the files you need to modify. Only suggest changes to files that the users says you can edit. Before changing other files, you *MUST* tell the user their full path names and ask them to *add the files to the chat*. End your reply and wait for their approval. +1. List the files you need to modify. Only suggest changes to files that the user says you can edit. Before changing other files, you *MUST* tell the user their full path names and ask them to *add the files to the chat*. End your reply and wait for their approval. 2. Think step-by-step and explain the needed changes with a numbered list of short sentences. 3. Describe each change with a *SEARCH/REPLACE block* per the examples below. All changes to files must use this *SEARCH/REPLACE block* format. ONLY EVER RETURN CODE IN A *SEARCH/REPLACE BLOCK*!