Open source AI coding agent. Designed for large projects and real world tasks.
Go aiai-agentsai-developer-toolsai-toolsclicommand-linedeveloper-toolsgitgolanggpt-4llmopenaipolyglot-programmingterminalterminal-basedterminal-ui
chore: remove repetitive words
verytrapba7ecd32e986
diff --git a/app/server/model/prompts/build.go b/app/server/model/prompts/build.goindex 14dfaeff..bac4a92f 100644--- a/app/server/model/prompts/build.go+++ b/app/server/model/prompts/build.go@@ -99,7 +99,7 @@ func getListChangesPrompt(lastLineNum int) string {'endLine' is the line number where the section to be replaced ends in the original file. *'endLine' MUST be an integer greater than 0.* If 'err' is not set or is an empty string, 'endLine' must be equal to 'maybeEndLine'. If 'err' is set and is *not* an empty string, 'endLine' should be the *corrected* line number where the section to be replaced ends in the original file.- The 'new' property is a string that represents the new code that will replace the old code. The new code must be valid and consistent with the intention of the plan. If the the proposed update is to remove code, the 'new' property should be an empty string.+ The 'new' property is a string that represents the new code that will replace the old code. The new code must be valid and consistent with the intention of the plan. If the proposed update is to remove code, the 'new' property should be an empty string.If the proposed update includes references to the original code in comments like "// rest of the function..." or "# existing init code...", or "// rest of the main function..." or "// rest of your function..." or **any other reference to the original code,** you *MUST* ensure that the comment making the reference is *NOT* included in the 'new' property. Instead, include the **exact code** from the original file that the comment is referencing. Do not be overly strict in identifying references. If there is a comment that seems like it could plausibly be a reference and there is code in the original file that could plausibly be the code being referenced, then treat that as a reference and handle it accordingly by including the code from the original file in the 'new' property instead of the comment. YOU MUST NOT MISS ANY REFERENCES.diff --git a/app/server/model/prompts/create.go b/app/server/model/prompts/create.goindex 194a9e7a..1f86009c 100644--- a/app/server/model/prompts/create.go+++ b/app/server/model/prompts/create.go@@ -27,7 +27,7 @@ const SysCreate = Identity + ` A plan is a set of files with an attached context- src/main.rs:- lib/term.go:- main.py:- ***File paths MUST ALWAYS come *IMMEDIATELY before* the opening triple backticks of a code block. They should *not* be included in the code block itself. There MUST NEVER be *any other lines* between the file path and the the opening triple backticks. Any explanations should come either *before the file path or *after* the code block is closed by closing triple backticks.*+ ***File paths MUST ALWAYS come *IMMEDIATELY before* the opening triple backticks of a code block. They should *not* be included in the code block itself. There MUST NEVER be *any other lines* between the file path and the opening triple backticks. Any explanations should come either *before the file path or *after* the code block is closed by closing triple backticks.****You *must not* include **any other text** in a code block label apart from the initial '- ' and the EXACT file path ONLY. DO NOT UNDER ANY CIRCUMSTANCES use a label like 'File path: src/main.rs' or 'src/main.rs: (Create this file)' or 'File to Create: src/main.rs' or 'File to Update: src/main.rs'. Instead use EXACTLY 'src/main.rs:'. DO NOT include any explanatory text in the code block label like 'src/main.rs: (Add a new function)'. Instead, include any necessary explanations either before the file path or after the code block. You MUST ALWAYS WITH NO EXCEPTIONS use the exact format described here for file paths in code blocks.b. If not:- Explicitly say "Let's break up this task."@@ -65,7 +65,7 @@ const SysCreate = Identity + ` A plan is a set of files with an attached contextAn exception to the above instructions on comments are if a file block is empty because you removed everything in it. In that case, leave a brief one-line comment starting with 'Plandex: removed' that says what was removed so that the file block isn't empty.- In code blocks, include the *minimum amount of code* necessary to describe the suggested changes. Include only lines that are changing and and lines that make it clear where the change should be applied. You can use comments like "// rest of the function..." or "// rest of the file..." to help make it clear where changes should be applied. You *must not* include large sections of the original file unless it helps make the suggested changes clear.+ In code blocks, include the *minimum amount of code* necessary to describe the suggested changes. Include only lines that are changing and lines that make it clear where the change should be applied. You can use comments like "// rest of the function..." or "// rest of the file..." to help make it clear where changes should be applied. You *must not* include large sections of the original file unless it helps make the suggested changes clear.As much as possible, do not include placeholders in code blocks like "// implement functionality here". Unless you absolutely cannot implement the full code block, do not include a placeholder denoted with comments. Do your best to implement the functionality rather than inserting a placeholder. You **MUST NOT** include placeholders just to shorten the code block. If the task is too large to implement in a single code block, you should break the task down into smaller steps and **FULLY** implement each step.diff --git a/releases/server/CHANGELOG.md b/releases/server/CHANGELOG.mdindex 181f16d7..b2667a6d 100644--- a/releases/server/CHANGELOG.md+++ b/releases/server/CHANGELOG.md@@ -15,7 +15,7 @@- Clean up extraneous logging- Prompt update to prevent ouputting files at absolute paths (like '/etc/config.txt')- Prompt update to prevent sometimes using file block format for explanations, causing explanations to be outputted as files-- Prompt update to prevent stopping before the the plan is really finished+- Prompt update to prevent stopping before the plan is really finished- Increase maximum number of auto-continuations to 50 (from 30)## Version 0.8.0diff --git a/releases/server/versions/0.8.1.md b/releases/server/versions/0.8.1.mdindex 6882075d..0d5630bf 100644--- a/releases/server/versions/0.8.1.md+++ b/releases/server/versions/0.8.1.md@@ -6,5 +6,5 @@- Clean up extraneous logging- Prompt update to prevent ouputting files at absolute paths (like '/etc/config.txt')- Prompt update to prevent sometimes using file block format for explanations, causing explanations to be outputted as files-- Prompt update to prevent stopping before the the plan is really finished+- Prompt update to prevent stopping before the plan is really finished- Increase maximum number of auto-continuations to 50 (from 30)