updated assistant auto-reply to no files

This commit is contained in:
Paul Gauthier 2024-05-09 11:56:11 -07:00
parent 444d17de93
commit 4eec60f42c
2 changed files with 4 additions and 5 deletions

View file

@ -432,15 +432,14 @@ class Coder:
if self.abs_fnames: if self.abs_fnames:
files_content = self.gpt_prompts.files_content_prefix files_content = self.gpt_prompts.files_content_prefix
files_content += self.get_files_content() files_content += self.get_files_content()
files_reply = "Ok, I will propose edits to those files to complete your request."
else: else:
files_content = self.gpt_prompts.files_no_full_files files_content = self.gpt_prompts.files_no_full_files
files_reply = "Ok."
files_messages += [ files_messages += [
dict(role="user", content=files_content), dict(role="user", content=files_content),
dict( dict(role="assistant", content=files_reply),
role="assistant",
content="Ok, I will propose edits to those files to complete your request.",
),
] ]
images_message = self.get_images_message() images_message = self.get_images_message()

View file

@ -12,7 +12,7 @@ Take requests for changes to the supplied code.
If the request is ambiguous, ask questions. If the request is ambiguous, ask questions.
Once you understand the request you MUST: 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. 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*! 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*!