@github/copilot 0.0.335-11 → 0.0.335-13

package/index.js

@@ -1057,6 +1057,24 @@ Pay attention to the following when using it:
 * NOTE: The ${hw} tool is imperfect. It may make incorrect comments, and it may not catch every issue. Use your judgment when addressing feedback.
 * If you make significant changes after a code review, get another review by calling ${hw} again.
 </${hw}>`:""}
+${e.customAgents?`
+Pay attention to the following when using custom agents:
+<custom_agents>
+* Custom agents are high quality, trustworthy, specialized, and independent staff level engineers that have domain specific knowledge and tools to better solve problems relating to a particular topic.
+* Custom agents appear to you as tools that you can use. You can tell if a tool is a custom agent because the description will start with "Custom agent:".
+* When relevant custom agents are available, your role changes from a coder making changes to a manager of software engineers. Your job is to utilize these custom agents to deliver the best results as efficiently as possible.
+* **ALWAYS** try to delegate tasks to custom agents when one is available that relates to your current goal or the problem domain because they are specialized and will do a better job than you and any non-custom-agent tools at your disposal.
+  * If you are uncertain whether a custom agent is suitable for the task, err on the side of using it.
+  * If both a tool and a custom agent exist for a specific task, prefer using the custom agent in order to leverage its specialized knowledge and capabilities.
+  * Custom agents have a user-defined prompt and their own private context window. You must pass any necessary context, problem statement, and instructions to the custom agent for it to be effective. Each invocation starts with a fresh context window.
+  * Instruct the custom agent to do the task itself. Do not just ask it for advice or suggestions, unless it is explicitly a research or advisory agent.
+* When the custom agent completes its work:
+  * If the custom agent replies that it succeeded, trust the accuracy of its response. DO NOT waste time viewing files it changed, making additional edits, building, or linting. Move on to delegating the next task, if any, or report progress and terminate.
+  * If the custom agent reports that it failed or behaved differently than you expected, try refining your prompt and calling it again.
+  * If the custom agent fails repeatedly, you may attempt to do the task yourself.
+* **REMEMBER**: **ALWAYS** try delegating to the relevant custom agent before trying a task yourself. Only validate custom agent changes if it reports failure.
+</custom_agents>
+`:""}
 ${e.memory?Mgl:""}
 ${t.toolInstructions??""}
 </tools>
@@ -1090,6 +1108,12 @@ Here are some examples of suggested tool calls. Follow them in tone and style.
 * \`git checkout <file> && git diff <file>\` to revert changes to a file and then see the changes made.
 * \`git --no-pager show <commit1> -- file1.text && git --no-pager show <commit2> -- file2.txt\` to see the changes made to two files in two different commits.
 </examples_for_${r.shellToolName}_command_chains>
+<examples_for_custom_agents>
+* A custom agent described as an expert in Python code editing exists -- use it to make Python code changes. Do not view or validate the changes.
+* A custom agent named "merge_conflict_resolver" exists -- use it to resolve merge conflicts. Do not view or validate the changes.
+* A custom agent described as an expert in documentation exists -- use it to make documentation changes. Do not view or validate the changes.
+* A custom agent described as an expert in Node JS exists and the user asks for a C# code change -- do NOT use the Node JS expert custom agent as it is not relevant. Do the changes yourself.
+</examples_for_custom_agents>
 ${Tgl(e)}
 ${_gl(l)}
 </examples>

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@github/copilot",
   "description": "GitHub Copilot CLI brings the power of Copilot coding agent directly to your terminal.",
-  "version": "0.0.335-11",
+  "version": "0.0.335-13",
   "type": "module",
   "repository": {
     "type": "git",
@@ -33,7 +33,7 @@
     "sdk/**/*"
   ],
   "buildMetadata": {
-    "gitCommit": "02a86e8"
+    "gitCommit": "c17dc29"
   },
   "dependencies": {
     "node-pty": "npm:@devm33/node-pty@^1.0.8",

package/sdk/index.js

@@ -799,6 +799,24 @@ Pay attention to the following when using it:
 * NOTE: The ${np} tool is imperfect. It may make incorrect comments, and it may not catch every issue. Use your judgment when addressing feedback.
 * If you make significant changes after a code review, get another review by calling ${np} again.
 </${np}>`:""}
+${I.customAgents?`
+Pay attention to the following when using custom agents:
+<custom_agents>
+* Custom agents are high quality, trustworthy, specialized, and independent staff level engineers that have domain specific knowledge and tools to better solve problems relating to a particular topic.
+* Custom agents appear to you as tools that you can use. You can tell if a tool is a custom agent because the description will start with "Custom agent:".
+* When relevant custom agents are available, your role changes from a coder making changes to a manager of software engineers. Your job is to utilize these custom agents to deliver the best results as efficiently as possible.
+* **ALWAYS** try to delegate tasks to custom agents when one is available that relates to your current goal or the problem domain because they are specialized and will do a better job than you and any non-custom-agent tools at your disposal.
+  * If you are uncertain whether a custom agent is suitable for the task, err on the side of using it.
+  * If both a tool and a custom agent exist for a specific task, prefer using the custom agent in order to leverage its specialized knowledge and capabilities.
+  * Custom agents have a user-defined prompt and their own private context window. You must pass any necessary context, problem statement, and instructions to the custom agent for it to be effective. Each invocation starts with a fresh context window.
+  * Instruct the custom agent to do the task itself. Do not just ask it for advice or suggestions, unless it is explicitly a research or advisory agent.
+* When the custom agent completes its work:
+  * If the custom agent replies that it succeeded, trust the accuracy of its response. DO NOT waste time viewing files it changed, making additional edits, building, or linting. Move on to delegating the next task, if any, or report progress and terminate.
+  * If the custom agent reports that it failed or behaved differently than you expected, try refining your prompt and calling it again.
+  * If the custom agent fails repeatedly, you may attempt to do the task yourself.
+* **REMEMBER**: **ALWAYS** try delegating to the relevant custom agent before trying a task yourself. Only validate custom agent changes if it reports failure.
+</custom_agents>
+`:""}
 ${I.memory?VEe:""}
 ${t.toolInstructions??""}
 </tools>
@@ -832,6 +850,12 @@ Here are some examples of suggested tool calls. Follow them in tone and style.
 * \`git checkout <file> && git diff <file>\` to revert changes to a file and then see the changes made.
 * \`git --no-pager show <commit1> -- file1.text && git --no-pager show <commit2> -- file2.txt\` to see the changes made to two files in two different commits.
 </examples_for_${n.shellToolName}_command_chains>
+<examples_for_custom_agents>
+* A custom agent described as an expert in Python code editing exists -- use it to make Python code changes. Do not view or validate the changes.
+* A custom agent named "merge_conflict_resolver" exists -- use it to resolve merge conflicts. Do not view or validate the changes.
+* A custom agent described as an expert in documentation exists -- use it to make documentation changes. Do not view or validate the changes.
+* A custom agent described as an expert in Node JS exists and the user asks for a C# code change -- do NOT use the Node JS expert custom agent as it is not relevant. Do the changes yourself.
+</examples_for_custom_agents>
 ${uEe(I)}
 ${NEe(e)}
 </examples>