@github/copilot 0.0.334-5 → 0.0.334-6

package/index.js

@@ -1100,7 +1100,7 @@ ${I.content}
 Additional instructions from user's \`${I.additionalInstructions.sourcePath}\`:
 ${I.additionalInstructions.content}
 `)),a+=e.parallel_tool_calls?`<tool_calling>
-${eit(e)}
+${eit()}
 </tool_calling>`:"",a};var qct=async(t,e,l,I={},n={},r={})=>{let a=await VCe(t,!0),s=Kct.type(),o=t===""?"":S$(t),d=(await Promise.all(["git","curl","gh"].map(async u=>await Pct(u)!==null?u:null))).filter(u=>u!==null).join(", ");return`
 You are the GitHub Copilot CLI, a terminal based coding agent built by GitHub.
 
@@ -1175,7 +1175,19 @@ You *must* avoid doing any of these things you cannot or must not do, and also *
 * When replying to the user, offer crisp, concise responses.
 </tips_and_tricks>
 
-${KWl(I,n,r,a)}`.trim()};var $ct=t=>`Here is the url of a screenshot: ${t}. You can use it to include in the PR description if it is suitable for the task.`,eit=t=>t.parallel_tool_calls?"You have the capability to call multiple tools in a single response. For maximum efficiency, whenever you need to perform multiple independent operations, ALWAYS invoke all relevant tools simultaneously rather than sequentially. Especially when exploring repository, reading files, viewing directories, validating changes or replying to comments.":"",qWl=(t={})=>t.splitEditingTools?`<str_replace>
+<avoid_excessive_markdown_and_bullet_points>
+When communicating to the user, explaining in between tool calls or summarizing your progress, use concise, clear, flowing prose with complete paragraphs and sentences.
+Avoid using bullet points, numbered lists, or excessive markdown formatting unless the user explicitly requests a list or ranking.
+Instead of listing items, incorporate them naturally into sentences.
+Use standard paragraph breaks for organization and reserve markdown primarily for code blocks and simple sentence case headings.
+
+There is an important exception: lists are appropriate when the user specifically asks for a list or ranking, or when presenting truly discret items where a list format is the best option.
+When in doubt, choose prose over bullets. NEVER output a series of overly short bullet points.
+</avoid_excessive_markdown_and_bullet_points>
+
+${KWl(I,n,r,a)}`.trim()};var $ct=t=>`Here is the url of a screenshot: ${t}. You can use it to include in the PR description if it is suitable for the task.`,eit=()=>`You have the capability to call multiple tools in a single response. For maximum efficiency, whenever you need to perform multiple independent operations, ALWAYS call tools simultaneously whenever the actions can be done in parallel rather than sequentially.
+Especially when exploring repository, searching, reading files, viewing directories, validating changes, reporting progress or replying to comments. For Example you can read 3 different files parallelly, or report progress and edit different files in parallel. Always report progress in parallel with other tool calls that follow it as it does not depend on the result of those calls.
+However, if some tool calls depend on previous calls to inform dependent values like the parameters, do NOT call these tools in parallel and instead call them sequentially.`,qWl=(t={})=>t.splitEditingTools?`<str_replace>
 You can use the **str_replace** tool to batch edits to the same file in a single response. The tool will apply edits in sequential order, removing the risk of a reader/writer conflict.
 <example>
 If renaming a variable in multiple places, call **str_replace** multiple times in the same response, once for each instance of the variable name.
@@ -1211,7 +1223,7 @@ old_str: "console.log("duration was \${elapsedTimeMs}ms"
 </str_replace>`:"",obe=(t,e={})=>{let l=t;return e.parallel_tool_calls&&(l+=`
 
 <reminder>
-${eit(e)}
+${eit()}
 </reminder>`),e.vision&&(l+=`
 
 <reminder>

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.334-5",
+  "version": "0.0.334-6",
   "type": "module",
   "repository": {
     "type": "git",
@@ -33,7 +33,7 @@
     "sdk/**/*"
   ],
   "buildMetadata": {
-    "gitCommit": "855a060"
+    "gitCommit": "cb20f47"
   },
   "dependencies": {
     "node-pty": "npm:@devm33/node-pty@^1.0.8",

package/sdk/index.js

@@ -842,7 +842,7 @@ ${l.content}
 Additional instructions from user's \`${l.additionalInstructions.sourcePath}\`:
 ${l.additionalInstructions.content}
 `)),a+=I.parallel_tool_calls?`<tool_calling>
-${F9I(I)}
+${F9I()}
 </tool_calling>`:"",a};var R9I=async(t,I,e,l={},c={},n={})=>{let a=await pGI(t,!0),s=V9I.type(),r=t===""?"":ZGI(t),o=(await Promise.all(["git","curl","gh"].map(async b=>await Y9I(b)!==null?b:null))).filter(b=>b!==null).join(", ");return`
 You are the GitHub Copilot CLI, a terminal based coding agent built by GitHub.
 
@@ -917,7 +917,19 @@ You *must* avoid doing any of these things you cannot or must not do, and also *
 * When replying to the user, offer crisp, concise responses.
 </tips_and_tricks>
 
-${SHe(l,c,n,a)}`.trim()};var y9I=t=>`Here is the url of a screenshot: ${t}. You can use it to include in the PR description if it is suitable for the task.`,F9I=t=>t.parallel_tool_calls?"You have the capability to call multiple tools in a single response. For maximum efficiency, whenever you need to perform multiple independent operations, ALWAYS invoke all relevant tools simultaneously rather than sequentially. Especially when exploring repository, reading files, viewing directories, validating changes or replying to comments.":"",OHe=(t={})=>t.splitEditingTools?`<str_replace>
+<avoid_excessive_markdown_and_bullet_points>
+When communicating to the user, explaining in between tool calls or summarizing your progress, use concise, clear, flowing prose with complete paragraphs and sentences.
+Avoid using bullet points, numbered lists, or excessive markdown formatting unless the user explicitly requests a list or ranking.
+Instead of listing items, incorporate them naturally into sentences.
+Use standard paragraph breaks for organization and reserve markdown primarily for code blocks and simple sentence case headings.
+
+There is an important exception: lists are appropriate when the user specifically asks for a list or ranking, or when presenting truly discret items where a list format is the best option.
+When in doubt, choose prose over bullets. NEVER output a series of overly short bullet points.
+</avoid_excessive_markdown_and_bullet_points>
+
+${SHe(l,c,n,a)}`.trim()};var y9I=t=>`Here is the url of a screenshot: ${t}. You can use it to include in the PR description if it is suitable for the task.`,F9I=()=>`You have the capability to call multiple tools in a single response. For maximum efficiency, whenever you need to perform multiple independent operations, ALWAYS call tools simultaneously whenever the actions can be done in parallel rather than sequentially.
+Especially when exploring repository, searching, reading files, viewing directories, validating changes, reporting progress or replying to comments. For Example you can read 3 different files parallelly, or report progress and edit different files in parallel. Always report progress in parallel with other tool calls that follow it as it does not depend on the result of those calls.
+However, if some tool calls depend on previous calls to inform dependent values like the parameters, do NOT call these tools in parallel and instead call them sequentially.`,OHe=(t={})=>t.splitEditingTools?`<str_replace>
 You can use the **str_replace** tool to batch edits to the same file in a single response. The tool will apply edits in sequential order, removing the risk of a reader/writer conflict.
 <example>
 If renaming a variable in multiple places, call **str_replace** multiple times in the same response, once for each instance of the variable name.
@@ -953,7 +965,7 @@ old_str: "console.log("duration was \${elapsedTimeMs}ms"
 </str_replace>`:"",Q9I=(t,I={})=>{let e=t;return I.parallel_tool_calls&&(e+=`
 
 <reminder>
-${F9I(I)}
+${F9I()}
 </reminder>`),I.vision&&(e+=`
 
 <reminder>