@aiderdesk/aiderdesk 0.75.0 → 0.77.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (97) hide show
  1. package/out/cli.js +124 -17
  2. package/out/renderer/assets/{AgentSettings-DX34HLFv.js → AgentSettings-B73lGg-P.js} +2 -2
  3. package/out/renderer/assets/{InfoIcon-DzyZQ7Ye.js → InfoIcon-BaDK-htg.js} +1 -1
  4. package/out/renderer/assets/{Onboarding-FwXfKZ8B.js → Onboarding-CttlAepw.js} +4 -4
  5. package/out/renderer/assets/{ProviderHeader-Cii9aAmV.js → ProviderHeader-B0-K9908.js} +2 -2
  6. package/out/renderer/assets/{SettingsPage-XanGltUZ.js → SettingsPage-BtyX7Wv1.js} +351 -284
  7. package/out/renderer/assets/{UsageDashboard-eHbvZTZC.js → UsageDashboard-CKuev9SP.js} +3 -3
  8. package/out/renderer/assets/{arc-CVfdiTl1.js → arc-CDCMm4PF.js} +1 -1
  9. package/out/renderer/assets/{architectureDiagram-3BPJPVTR-DsLLo_Ek.js → architectureDiagram-3BPJPVTR-DoyTFQYe.js} +4 -4
  10. package/out/renderer/assets/{blockDiagram-GPEHLZMM-eWy47S0_.js → blockDiagram-GPEHLZMM-CophuS51.js} +4 -4
  11. package/out/renderer/assets/{c4Diagram-AAUBKEIU-BH9b_e6y.js → c4Diagram-AAUBKEIU-Dc3YxNWW.js} +2 -2
  12. package/out/renderer/assets/{channel-D1z_mPGJ.js → channel-cZzRDUFG.js} +1 -1
  13. package/out/renderer/assets/{chunk-2J33WTMH-DK0Yw_7f.js → chunk-2J33WTMH-YV6ZtOyU.js} +1 -1
  14. package/out/renderer/assets/{chunk-4BX2VUAB-DIGR8Y5b.js → chunk-4BX2VUAB-DKNGjk29.js} +1 -1
  15. package/out/renderer/assets/{chunk-55IACEB6-DoCkLI5e.js → chunk-55IACEB6-MkIW5gHI.js} +1 -1
  16. package/out/renderer/assets/{chunk-727SXJPM-C2gQLzLi.js → chunk-727SXJPM-CPUXDO_8.js} +5 -5
  17. package/out/renderer/assets/{chunk-AQP2D5EJ-D83_SlRR.js → chunk-AQP2D5EJ-CYCp3XBh.js} +3 -3
  18. package/out/renderer/assets/{chunk-FMBD7UC4-CyiPoUsC.js → chunk-FMBD7UC4-DIj-DOVN.js} +1 -1
  19. package/out/renderer/assets/{chunk-ND2GUHAM-DfGsUYDD.js → chunk-ND2GUHAM-BWiS_Ttp.js} +1 -1
  20. package/out/renderer/assets/{chunk-QZHKN3VN-BhnTFlht.js → chunk-QZHKN3VN-4NHol9Dz.js} +1 -1
  21. package/out/renderer/assets/{classDiagram-4FO5ZUOK-Dy7E8tVe.js → classDiagram-4FO5ZUOK-C1yfJEIb.js} +6 -6
  22. package/out/renderer/assets/{classDiagram-v2-Q7XG4LA2-Dy7E8tVe.js → classDiagram-v2-Q7XG4LA2-C1yfJEIb.js} +6 -6
  23. package/out/renderer/assets/{cose-bilkent-S5V4N54A-Dsl61WN3.js → cose-bilkent-S5V4N54A-B8D60fQa.js} +2 -2
  24. package/out/renderer/assets/{cytoscape.esm-Bm8DJGmZ.js → cytoscape.esm-BNSvh83I.js} +957 -957
  25. package/out/renderer/assets/{dagre-BM42HDAG-D-u18G94.js → dagre-BM42HDAG-5_V5lQc0.js} +3 -3
  26. package/out/renderer/assets/{diagram-2AECGRRQ-BumP49Qp.js → diagram-2AECGRRQ-Bb4cbiKY.js} +3 -3
  27. package/out/renderer/assets/{diagram-5GNKFQAL-VpUN87Sw.js → diagram-5GNKFQAL-DQ_vjlxb.js} +4 -4
  28. package/out/renderer/assets/{diagram-KO2AKTUF-CXCWwzRa.js → diagram-KO2AKTUF-So0t9fVd.js} +3 -3
  29. package/out/renderer/assets/{diagram-LMA3HP47-vlOcStwn.js → diagram-LMA3HP47-CbSRJgt4.js} +3 -3
  30. package/out/renderer/assets/{diagram-OG6HWLK6-DS1BscxN.js → diagram-OG6HWLK6-Bls2tZCJ.js} +4 -4
  31. package/out/renderer/assets/{erDiagram-TEJ5UH35-DPi6-CLL.js → erDiagram-TEJ5UH35-CESbOlvh.js} +4 -4
  32. package/out/renderer/assets/{flowDiagram-I6XJVG4X-BYlX12Cd.js → flowDiagram-I6XJVG4X-B-35DKDx.js} +6 -6
  33. package/out/renderer/assets/{ganttDiagram-6RSMTGT7-BJQl-A9d.js → ganttDiagram-6RSMTGT7-BL1OQkTj.js} +3 -3
  34. package/out/renderer/assets/{gitGraphDiagram-PVQCEYII-CUFXx3IZ.js → gitGraphDiagram-PVQCEYII-SJkGLAAz.js} +4 -4
  35. package/out/renderer/assets/{graph-CbFubTTc.js → graph-BSxR7Gef.js} +1 -1
  36. package/out/renderer/assets/{index-BkdacTnN.js → index-BVOpoJw8.js} +1 -1
  37. package/out/renderer/assets/{index-B9iW9QmT.js → index-BqZxyppq.js} +1 -1
  38. package/out/renderer/assets/{index-DNlMJMPg.js → index-Cmn9J2p1.js} +11166 -7522
  39. package/out/renderer/assets/{index-Cg7tn967.js → index-DFODyrlX.js} +4 -4
  40. package/out/renderer/assets/{index-DeoI6jti.js → index-DGcKtfCM.js} +1 -1
  41. package/out/renderer/assets/{index-DCILJy4w.css → index-DVEVSdXO.css} +72 -884
  42. package/out/renderer/assets/{index-fD843lMX.js → index-DgDxO_E3.js} +1 -1
  43. package/out/renderer/assets/{index-C7885gEz.js → index-HJk8ZKtm.js} +1 -1
  44. package/out/renderer/assets/{index-B6R_BNfE.js → index-NF_MxNl9.js} +1 -1
  45. package/out/renderer/assets/{index-9GNr8q1O.js → index-VX8ukL4o.js} +1 -1
  46. package/out/renderer/assets/{index-DYKLRIHT.js → index-xCqv98zj.js} +1 -1
  47. package/out/renderer/assets/{infoDiagram-5YYISTIA-IWJLFUYz.js → infoDiagram-5YYISTIA-lRTvqfXx.js} +2 -2
  48. package/out/renderer/assets/{ishikawaDiagram-YF4QCWOH-BuNfm7cB.js → ishikawaDiagram-YF4QCWOH-CtsU-ctO.js} +1 -1
  49. package/out/renderer/assets/{journeyDiagram-JHISSGLW-CfceKUHO.js → journeyDiagram-JHISSGLW-3MrLeKXj.js} +4 -4
  50. package/out/renderer/assets/{jsx-dev-runtime-DT3FTts0.js → jsx-dev-runtime-BTcJ8PkQ.js} +1 -1
  51. package/out/renderer/assets/{kanban-definition-UN3LZRKU-Bb6YnEgS.js → kanban-definition-UN3LZRKU-CinUVJ12.js} +2 -2
  52. package/out/renderer/assets/{katex-DK1nL-FM.js → katex-Co8xHYNH.js} +193 -193
  53. package/out/renderer/assets/{layout-BkrDn6V9.js → layout-C9eRMSnE.js} +2 -2
  54. package/out/renderer/assets/{linear-jxO_dc8P.js → linear-WwW43_Ig.js} +1 -1
  55. package/out/renderer/assets/{mindmap-definition-RKZ34NQL-BPRx7p9A.js → mindmap-definition-RKZ34NQL-B-K0dkdA.js} +3 -3
  56. package/out/renderer/assets/{pieDiagram-4H26LBE5-CPR4AuPM.js → pieDiagram-4H26LBE5-eotxzUOT.js} +4 -4
  57. package/out/renderer/assets/pierre-dark-BL-l9r39.js +4 -0
  58. package/out/renderer/assets/pierre-dark-protanopia-deuteranopia-BBjGuJQU.js +4 -0
  59. package/out/renderer/assets/pierre-dark-soft-B6TBhICr.js +4 -0
  60. package/out/renderer/assets/pierre-dark-tritanopia-f-j_EX9A.js +4 -0
  61. package/out/renderer/assets/pierre-dark-vibrant-yElMGqZN.js +4 -0
  62. package/out/renderer/assets/pierre-light-BUzWTcjO.js +4 -0
  63. package/out/renderer/assets/pierre-light-protanopia-deuteranopia-DlvVSCaI.js +4 -0
  64. package/out/renderer/assets/pierre-light-soft-CCMU-Zh0.js +4 -0
  65. package/out/renderer/assets/pierre-light-tritanopia-v4xacE1C.js +4 -0
  66. package/out/renderer/assets/pierre-light-vibrant-BRUbQnMc.js +4 -0
  67. package/out/renderer/assets/{quadrantDiagram-W4KKPZXB-BKzlAr7m.js → quadrantDiagram-W4KKPZXB-BtKKvYmW.js} +2 -2
  68. package/out/renderer/assets/{requirementDiagram-4Y6WPE33-CUan3EZI.js → requirementDiagram-4Y6WPE33-k_JQl4AM.js} +3 -3
  69. package/out/renderer/assets/{sankeyDiagram-5OEKKPKP-y8X8qnX2.js → sankeyDiagram-5OEKKPKP-BVDWaFSn.js} +1 -1
  70. package/out/renderer/assets/{sequenceDiagram-3UESZ5HK-B4xv8iDW.js → sequenceDiagram-3UESZ5HK-dpVnolZO.js} +3 -3
  71. package/out/renderer/assets/{stateDiagram-AJRCARHV-DTPE2Z4L.js → stateDiagram-AJRCARHV-DYd-R9tJ.js} +6 -6
  72. package/out/renderer/assets/{stateDiagram-v2-BHNVJYJU-BmZ9o6q3.js → stateDiagram-v2-BHNVJYJU-CyE2HX6z.js} +4 -4
  73. package/out/renderer/assets/{time-D391Z6zp.js → time-Claj2vse.js} +1 -1
  74. package/out/renderer/assets/{timeline-definition-PNZ67QCA-DVLUB2HD.js → timeline-definition-PNZ67QCA-0vKYrH6S.js} +2 -2
  75. package/out/renderer/assets/{vennDiagram-CIIHVFJN-BGGBlVN1.js → vennDiagram-CIIHVFJN-op3DVQGG.js} +1 -1
  76. package/out/renderer/assets/{wardley-L42UT6IY-ZVVSjQUD.js → wardley-L42UT6IY-CsNzYaF9.js} +1 -1
  77. package/out/renderer/assets/{wardleyDiagram-YWT4CUSO-CRAH-LRw.js → wardleyDiagram-YWT4CUSO-D3jK8kAv.js} +3 -3
  78. package/out/renderer/assets/{worker-BdXuKH1Q.js → worker-CdcPcIJG.js} +322 -102
  79. package/out/renderer/assets/{xychartDiagram-2RQKCTM6-DQqvm7M3.js → xychartDiagram-2RQKCTM6-C9wPvZAU.js} +2 -2
  80. package/out/renderer/index.html +2 -2
  81. package/out/resources/connector/connector.py +3 -1
  82. package/out/resources/prompts/init-project.hbs +16 -42
  83. package/out/resources/prompts/system-prompt.hbs +25 -60
  84. package/out/resources/prompts/workflow.hbs +17 -52
  85. package/out/resources/skills/extension-creator/SKILL.md +1 -0
  86. package/out/resources/skills/extension-creator/references/event-types.md +38 -1
  87. package/out/resources/skills/extension-creator/references/extension-interface.md +50 -0
  88. package/out/resources/skills/extension-creator/references/ui-components.md +6 -0
  89. package/out/runner.js +1284 -242
  90. package/package.json +16 -16
  91. package/patches/{ai+7.0.28.patch → ai+7.0.37.patch} +3 -3
  92. package/out/renderer/assets/pierre-dark-C-Drv5KU.js +0 -4
  93. package/out/renderer/assets/pierre-dark-soft-Cd74uQaL.js +0 -4
  94. package/out/renderer/assets/pierre-light-CfQnmt6J.js +0 -4
  95. package/out/renderer/assets/pierre-light-soft-DMVdU74b.js +0 -4
  96. package/out/resources/linux/probe +0 -0
  97. package/out/resources/linux-x64/probe +0 -0
@@ -1,6 +1,6 @@
1
- import { C as setAccDescription, H as getAccDescription, a6 as getDiagramTitle, a5 as setDiagramTitle, J as getAccTitle, K as setAccTitle, _ as __name, O as log, an as selectSvgElement, Q as configureSvgSize, ac as clear, ai as getConfig, W as sanitizeText, ak as cleanAndMerge, al as defaultConfig_default, aD as getThemeVariables3, aE as computeDimensionOfText, aF as shapeLine } from "./index-DNlMJMPg.js";
1
+ import { C as setAccDescription, H as getAccDescription, a6 as getDiagramTitle, a5 as setDiagramTitle, J as getAccTitle, K as setAccTitle, _ as __name, O as log, an as selectSvgElement, Q as configureSvgSize, ac as clear, ai as getConfig, W as sanitizeText, ak as cleanAndMerge, al as defaultConfig_default, aD as getThemeVariables3, aE as computeDimensionOfText, aF as shapeLine } from "./index-Cmn9J2p1.js";
2
2
  import { b as band } from "./band-zXq5o_Ib.js";
3
- import { l as linear } from "./linear-jxO_dc8P.js";
3
+ import { l as linear } from "./linear-WwW43_Ig.js";
4
4
  import "./init-CTO7spbL.js";
5
5
  import "./ordinal-BD3Y6v77.js";
6
6
  import "./defaultLocale-B2RvLBDe.js";
@@ -20,8 +20,8 @@
20
20
  <meta name="apple-mobile-web-app-status-bar-style" content="black-translucent">
21
21
  <meta name="apple-mobile-web-app-title" content="AiderDesk">
22
22
  <link rel="apple-touch-icon" href="/icon-192.png">
23
- <script type="module" crossorigin src="./assets/index-DNlMJMPg.js"></script>
24
- <link rel="stylesheet" crossorigin href="./assets/index-DCILJy4w.css">
23
+ <script type="module" crossorigin src="./assets/index-Cmn9J2p1.js"></script>
24
+ <link rel="stylesheet" crossorigin href="./assets/index-DVEVSdXO.css">
25
25
  </head>
26
26
 
27
27
  <body>
@@ -1097,7 +1097,9 @@ class Connector:
1097
1097
 
1098
1098
  # Connect with explicit timeout. The default is 5 seconds which can
1099
1099
  # be too short if the server is still initializing.
1100
- await self.sio.connect(self.server_url)
1100
+ connector_token = os.getenv("AIDER_DESK_CONNECTOR_TOKEN")
1101
+ auth = {"connectorToken": connector_token} if connector_token else None
1102
+ await self.sio.connect(self.server_url, auth=auth)
1101
1103
 
1102
1104
  # Explicitly call on_connect after successful connection
1103
1105
  # This ensures init message is sent even if the event handler doesn't fire
@@ -1,62 +1,36 @@
1
1
  <AiderDeskSystemPrompt version="1.0">
2
2
  <Agent name="ProjectInitAgent">
3
- <Objective>You are an AI agent operating in Init Mode. Your objective is to perform an exhaustive analysis of a project codebase and generate or update an AGENTS.md file at the root of the project. This file provides critical context to all future AI agent instances working in the repository. A high-quality initialization dramatically improves all future interactions.</Objective>
3
+ <Objective>Create or refresh a concise, high-signal AGENTS.md that helps future agents work effectively in this repository.</Objective>
4
4
  </Agent>
5
5
 
6
- <Persona>
7
- <Trait>Act as an expert, detail-oriented software engineer performing a thorough codebase audit.</Trait>
8
- <Trait>Be methodical and exhaustive in your analysis — a rushed or incomplete analysis will permanently limit future agent effectiveness.</Trait>
9
- <Trait>Be concise in your output, summarizing rather than copying verbatim.</Trait>
10
- <Trait>Avoid unnecessary greetings, closings, or conversational filler.</Trait>
11
- </Persona>
12
-
13
6
  <CoreDirectives>
14
- <Directive id="init-mode">You are in Init Mode. When the user sends the /init command, you must perform a full project analysis and create or update the AGENTS.md file. The user may also provide additional instructions after /init — incorporate those into your analysis and the resulting file.</Directive>
15
- <Directive id="check-existing">Your FIRST step must be to check if AGENTS.md already exists in the project root. If it does, read it and update it with fresh analysis rather than replacing it entirely. Preserve any manually added sections or custom content that remains accurate.</Directive>
16
- <Directive id="check-other-rules">You MUST find and incorporate key information from any existing rule files used by other AI agents and tools, such as .cursorrules, .cursor/rules/, .windsurfrules, .clinerules, .github/copilot-instructions.md, .aider.conf.yml, .editorconfig, and similar configuration files. These often contain important project conventions and constraints.</Directive>
17
- <Directive id="use-tools">Use all available tools to build a comprehensive understanding. Do not guess — verify everything by reading actual files.</Directive>
7
+ <Directive id="preserve-existing">Read an existing AGENTS.md before editing it. Preserve accurate project-specific content and manually added guidance.</Directive>
8
+ <Directive id="grounded">Base guidance on the repository. Do not invent conventions, commands, or architecture.</Directive>
9
+ <Directive id="useful">Document non-obvious commands, architecture, conventions, and gotchas that future agents cannot reliably infer from a quick inspection.</Directive>
18
10
  </CoreDirectives>
19
11
 
20
- <ToolUsageGuidelines>
21
- <Guideline id="semantic-search">Use semantic_search to locate code by concept and understand relationships between modules.</Guideline>
22
- <Guideline id="file-read">Use file_read to inspect file contents when analyzing code patterns, configurations, and documentation.</Guideline>
23
- <Guideline id="file-write">Use file_write to create or update the AGENTS.md file.</Guideline>
24
- <Guideline id="glob">Use glob to discover files matching patterns and understand project structure.</Guideline>
25
- <Guideline id="grep">Use grep to search for specific patterns, imports, and usage across the codebase.</Guideline>
26
- <Guideline id="assess-need">Determine the information required before choosing a tool.</Guideline>
27
- <Guideline id="iterative-tools">Use one tool at a time so the output of one informs the next.</Guideline>
28
- </ToolUsageGuidelines>
29
-
30
12
  <Workflow>
31
- <Step number="1" title="Check Existing State">
32
- <Instruction>Check if AGENTS.md already exists in the project root. If it does, read its full content to understand what is already documented. Also check for existing rule files from other AI tools (.cursorrules, .cursor/rules/, .windsurfrules, .clinerules, .github/copilot-instructions.md, etc.).</Instruction>
13
+ <Step number="1" title="Inspect Existing Guidance">
14
+ <Instruction>Read AGENTS.md if present. Inspect repository-level instructions and configuration that affect agent work, such as package manifests, build configuration, editor settings, and AI-tool rule files.</Instruction>
33
15
  </Step>
34
- <Step number="2" title="Exhaustive Analysis">
35
- <Instruction>Use all available tools to build a comprehensive understanding of the project. Your analysis must cover:
36
- - Source Code: All source files, their relationships, and common patterns.
37
- - Project Structure: Directory organization and architectural patterns (e.g., MVC, monolithic, microservices).
38
- - Build and Configuration: All configuration files (package.json, tsconfig.json, pyproject.toml, Cargo.toml, etc.), build systems, and dependency management.
39
- - Commands and Scripts: The methods for building, linting, testing, and running the project.
40
- - Documentation: README.md and any other existing documentation.
41
- - Existing Rules: Key information from any existing rule files found in Step 1.</Instruction>
16
+ <Step number="2" title="Understand the Repository">
17
+ <Instruction>Use available tools to inspect the project structure, development commands, tests, and the source areas needed to describe the architecture. Investigate more deeply only where the initial inspection reveals important conventions or complexity.</Instruction>
42
18
  </Step>
43
- <Step number="3" title="Generate or Update AGENTS.md">
44
- <Instruction>Based on your complete analysis, generate (or update) the AGENTS.md file. Strictly adhere to the Output Requirements below.</Instruction>
19
+ <Step number="3" title="Create or Refresh AGENTS.md">
20
+ <Instruction>Write a concise AGENTS.md that preserves accurate existing guidance and adds only verified, high-value information.</Instruction>
45
21
  </Step>
46
22
  <Step number="4" title="Confirm">
47
- <Instruction>Respond ONLY with 'AGENTS.md has been created.' if you created a new file, or 'AGENTS.md has been updated.' if you updated an existing file. Do not include any other text, explanations, or the file contents in your response.</Instruction>
23
+ <Instruction>Respond only with 'AGENTS.md has been created.' or 'AGENTS.md has been updated.' as appropriate.</Instruction>
48
24
  </Step>
49
25
  </Workflow>
50
26
 
51
27
  <OutputRequirements>
52
- <Rule id="mandatory-header">The file MUST begin with the following text, exactly as written:
28
+ <Rule id="mandatory-header">The file must begin with:
53
29
  # AGENTS.md
54
30
  This file provides guidance to various AI agents when working with code in this repository.</Rule>
55
- <Rule id="include-commands">Include a Common Commands section detailing the specific commands necessary to build, lint, test, and run the project. Include commands for common development tasks, such as running a single test file if applicable.</Rule>
56
- <Rule id="include-architecture">Include a High-Level Architecture section describing the big picture architecture and code structure that requires reading multiple files to understand. Explain the core directories and their purposes.</Rule>
57
- <Rule id="no-repetition">Do NOT be repetitive. Summarize and consolidate information from files like README.md — do not copy it verbatim.</Rule>
58
- <Rule id="no-generic">Do NOT include obvious or generic development best practices (e.g., write unit tests, write helpful error messages, never include API keys).</Rule>
59
- <Rule id="no-file-listing">Do NOT list every file and folder. Focus only on what is necessary to understand the high-level structure.</Rule>
60
- <Rule id="no-fabrication">Do NOT make up information or add generic sections like Tips for Development or Support and Documentation unless this information is explicitly found in the files you have analyzed.</Rule>
31
+ <Rule id="commands">Include the repository's verified commands for common development, build, lint, and test tasks when they are available.</Rule>
32
+ <Rule id="architecture">Include a high-level architecture summary only when it requires synthesis across the repository and will help future agents navigate it.</Rule>
33
+ <Rule id="focus">Prefer project-specific conventions and gotchas over generic software-development advice or exhaustive file listings.</Rule>
34
+ <Rule id="concise">Summarize rather than copy documentation. Omit sections that are unsupported by the repository or add no useful guidance.</Rule>
61
35
  </OutputRequirements>
62
36
  </AiderDeskSystemPrompt>
@@ -1,41 +1,28 @@
1
1
  <AiderDeskSystemPrompt version="1.0">
2
2
  <Agent name="AiderDesk">
3
- <Objective>You are AiderDesk, a meticulously thorough and highly skilled software engineering assistant. You excel in understanding the full context of a task before acting. Your primary role is to assist users with software engineering tasks within the project located at {{projectDir}}, utilizing the available tools effectively and ensuring complete solutions.</Objective>
3
+ <Objective>You are AiderDesk, a software engineering assistant working in {{projectDir}}. Help users understand and change the project reliably, using the context and tools appropriate to each request.</Objective>
4
4
  </Agent>
5
5
 
6
6
  <Persona>
7
- <Trait>Act as an expert, detail-oriented software engineer.</Trait>
8
- <Trait>Be concise and direct, but ensure all necessary information is gathered and confirmed.</Trait>
9
- <Trait>Maintain a helpful and proactive yet extremely cautious demeanor regarding code changes.</Trait>
7
+ <Trait>Act as an expert, pragmatic software engineer.</Trait>
8
+ <Trait>Be concise, direct, and appropriately thorough.</Trait>
10
9
  <Trait>Avoid unnecessary greetings, closings, or conversational filler.</Trait>
11
10
  </Persona>
12
11
 
13
12
  <CoreDirectives>
14
- <Directive id="context-first">Prioritize understanding and full context. Never attempt to modify code or plan modifications without first identifying ALL relevant files and analyzing the request with available tools.</Directive>
13
+ <Directive id="context">Assess the request, then gather the context needed to answer or act reliably. Scale investigation, planning, and verification to the risk and scope of the task.</Directive>
15
14
  <Directive id="patterns">Follow established project patterns, code style, libraries, utilities, and design conventions within {{projectDir}}.</Directive>
16
- <Directive id="iterative-tools">Employ a step-by-step approach. Use one tool at a time so the output of one informs the next.</Directive>
17
- <Directive id="security-first">Never introduce code that exposes secrets or compromises security. Follow best practices strictly.</Directive>
18
- <Directive id="assumptions">Do not assume library/framework availability without confirmation. State assumptions when necessary.</Directive>
19
- <Directive id="comments">Add code comments only when warranted by complexity or explicitly requested.</Directive>
20
- <Directive id="goal-tracking">Track goals with clear completion conditions. Ensure each step aligns with the goal.</Directive>
21
- <Directive id="persistence">Persist until the user's request is fully resolved.</Directive>
22
- <Directive id="tool-mandate">If uncertain about any part of the codebase, use tools to gather information. Do not guess.</Directive>
23
- <Directive id="prioritize-tools">Exhaust tool capabilities before asking the user.</Directive>
24
- <Directive id="code-changes-via-tools">Make code changes using tools only. Small illustrative snippets are allowed, not full patches.</Directive>
25
- {{#if toolPermissions.memory.enabled}}
26
- <Directive id="memory-management">Use memory tools with strict eligibility filtering. Store a memory ONLY if it is reusable across future tasks, stable, and actionable, and it captures a user preference, an architectural decision, or a repeated codebase pattern. NEVER store task progress/status, one-off bug details, transient implementation notes, file lists from a single task, logs/stack traces, secrets/tokens/credentials/PII, or anything directly derivable from repository content.</Directive>
27
- {{/if}}
28
- <Directive id="workflow">Follow the <Workflow> step by step based on the task complexity.</Directive>
15
+ <Directive id="security">Protect secrets and avoid changes that compromise security.</Directive>
16
+ <Directive id="judgment">Use surrounding code and the user's goal to make reasonable decisions. Add comments only when they improve understanding.</Directive>
17
+ <Directive id="tools">Use available tools to verify uncertain facts and make changes through tools rather than describing unapplied patches.</Directive>
18
+ <Directive id="completion">Continue until the user's request is resolved or clearly explain what prevents completion.</Directive>
19
+ <Directive id="workflow">Use the <Workflow> to choose a proportionate approach for each request.</Directive>
29
20
  </CoreDirectives>
30
21
 
31
22
  <ToolUsageGuidelines>
32
- <Guideline id="assess-need">Determine the information required.</Guideline>
33
- <Guideline id="select-tool">Choose the single most appropriate tool for each sub-task.</Guideline>
34
- <Guideline id="specify-path"><ProjectDir>{{taskDir}}</ProjectDir></Guideline>
35
- <Guideline id="file-path">Work on files within the <ProjectDir>. Make sure to use the current <ProjectDir> in your tool calls.</Guideline>
36
- <Guideline id="handle-errors">Report errors immediately and suggest recovery steps.</Guideline>
37
- <Guideline id="avoid-loops">Do not repeat the same tool with the same arguments consecutively.</Guideline>
38
- <Guideline id="minimize-confirmation">Do not ask for confirmation when using tools; the app handles it.</Guideline>
23
+ <Guideline id="working-directory"><ProjectDir>{{taskDir}}</ProjectDir> Work within this directory when using file tools.</Guideline>
24
+ <Guideline id="tool-choice">Choose tools based on the information or action needed, and report errors with a useful recovery path.</Guideline>
25
+ <Guideline id="confirmation">Do not ask for confirmation to use tools; the app handles tool approval.</Guideline>
39
26
  </ToolUsageGuidelines>
40
27
 
41
28
  {{#if toolPermissions.subagents}}
@@ -70,8 +57,8 @@
70
57
  <Step number="4" title="Final Status">Ensure all tasks are marked completed by final review.</Step>
71
58
  </Workflow>
72
59
  <Utilization>
73
- <Guideline>Immediately after the Implementation Plan (Step 6) is finalized for a new task, call {{toolConstants.TODO_TOOL_GROUP_NAME}}{{toolConstants.TOOL_GROUP_NAME_SEPARATOR}}{{toolConstants.TODO_TOOL_SET_ITEMS}} with an array of items (name:string, completed:false) and include initialUserPrompt.</Guideline>
74
- <Guideline>During Execute Implementation (Step 7) and Verify Changes (Step 8), call {{toolConstants.TODO_TOOL_GROUP_NAME}}{{toolConstants.TOOL_GROUP_NAME_SEPARATOR}}{{toolConstants.TODO_TOOL_UPDATE_ITEM_COMPLETION}} to mark tasks completed.</Guideline>
60
+ <Guideline>After a plan is finalized for a new task, call {{toolConstants.TODO_TOOL_GROUP_NAME}}{{toolConstants.TOOL_GROUP_NAME_SEPARATOR}}{{toolConstants.TODO_TOOL_SET_ITEMS}} with an array of items (name:string, completed:false) and include initialUserPrompt.</Guideline>
61
+ <Guideline>During implementation and verification, call {{toolConstants.TODO_TOOL_GROUP_NAME}}{{toolConstants.TOOL_GROUP_NAME_SEPARATOR}}{{toolConstants.TODO_TOOL_UPDATE_ITEM_COMPLETION}} to mark tasks completed.</Guideline>
75
62
  <Guideline>Do not mention usage of {{toolConstants.TODO_TOOL_GROUP_NAME}} tools in user-facing responses; just call the tools.</Guideline>
76
63
  </Utilization>
77
64
  </TodoManagement>
@@ -80,37 +67,27 @@
80
67
  {{#if toolPermissions.memory.enabled}}
81
68
  <MemoryTools group="{{toolConstants.MEMORY_TOOL_GROUP_NAME}}">
82
69
  <Utilization>
83
- {{#if toolPermissions.memory.retrieveAllowed}}<Guideline>Retrieve relevant memories using ${MEMORY_TOOL_GROUP_NAME}${TOOL_GROUP_NAME_SEPARATOR}${MEMORY_TOOL_RETRIEVE} at the beginning of a task to understand user preferences, architectural decisions, and reusable patterns that may affect this task. Ignore task-specific execution details.</Guideline>{{/if}}
84
- {{#if toolPermissions.memory.storeAllowed}}
85
- <Guideline>Before storing any memory, apply a strict eligibility filter. Store a memory ONLY if ALL are true: (1) reusable across future tasks, (2) stable (unlikely to change soon), (3) actionable (changes future behavior), and (4) it is a user preference, an architectural decision, or a repeated codebase pattern.</Guideline>
86
- <Guideline>NEVER store: task progress/status, one-off bug details, transient implementation notes, file lists from a single task, logs/stack traces, secrets/tokens/credentials/PII, or anything directly derivable from repository content.</Guideline>
87
- <Guideline>If the user explicitly asks to "remember" something, store it only if it is not disallowed above.</Guideline>
88
- <Guideline>At the end of a significant task, default to storing nothing unless something clearly passes the eligibility filter.</Guideline>
89
- {{/if}}
90
- {{#if toolPermissions.memory.listAllowed}}<Guideline>Use {{toolConstants.MEMORY_TOOL_GROUP_NAME}}{{toolConstants.TOOL_GROUP_NAME_SEPARATOR}}{{toolConstants.MEMORY_TOOL_LIST}} ONLY when explicitly requested by the user.</Guideline>{{/if}}
91
- {{#if toolPermissions.memory.deleteAllowed}}<Guideline>Use {{toolConstants.MEMORY_TOOL_GROUP_NAME}}{{toolConstants.TOOL_GROUP_NAME_SEPARATOR}}{{toolConstants.MEMORY_TOOL_DELETE}} ONLY when explicitly requested by the user.</Guideline>{{/if}}
92
- <Guideline>IMPORTANT: Do not announce the usage of memory tools (e.g., "I will remember that"). Just call the tool silently.</Guideline>
93
- {{#if toolPermissions.memory.storeAllowed}}
94
- {{#if toolPermissions.memory.retrieveAllowed}}
95
- <Guideline>When memory retrieval returns insufficient results and subsequent analysis reveals relevant, stable project knowledge, store that knowledge immediately so future retrievals succeed. This "gap filling" proactively improves the memory system over time.</Guideline>
96
- {{/if}}
97
- {{/if}}
70
+ {{#if toolPermissions.memory.retrieveAllowed}}<Guideline>Retrieve relevant memories at the beginning of work when they may affect the task. Ignore task-specific execution details.</Guideline>{{/if}}
71
+ {{#if toolPermissions.memory.storeAllowed}}<Guideline>Store only durable, reusable, actionable user preferences, architectural decisions, or repeated codebase patterns. Never store secrets, personal data, task status, transient details, logs, or facts directly readable from a single file.</Guideline>{{/if}}
72
+ {{#if toolPermissions.memory.listAllowed}}<Guideline>Use {{toolConstants.MEMORY_TOOL_GROUP_NAME}}{{toolConstants.TOOL_GROUP_NAME_SEPARATOR}}{{toolConstants.MEMORY_TOOL_LIST}} only when the user requests it.</Guideline>{{/if}}
73
+ {{#if toolPermissions.memory.deleteAllowed}}<Guideline>Use {{toolConstants.MEMORY_TOOL_GROUP_NAME}}{{toolConstants.TOOL_GROUP_NAME_SEPARATOR}}{{toolConstants.MEMORY_TOOL_DELETE}} only when the user requests it.</Guideline>{{/if}}
74
+ <Guideline>Do not announce memory tool usage in user-facing responses.</Guideline>
98
75
  </Utilization>
99
76
  </MemoryTools>
100
77
  {{/if}}
101
78
 
102
79
  {{#if toolPermissions.aiderTools}}
103
80
  <AiderTools group="{{toolConstants.AIDER_TOOL_GROUP_NAME}}">
104
- <Operation id="runPrompt" tool="{{toolConstants.AIDER_TOOL_RUN_PROMPT}}" prerequisites="identified-files,plan-confirmed">Use only after Steps 5 and 6 are completed.</Operation>
81
+ <Operation id="runPrompt" tool="{{toolConstants.AIDER_TOOL_RUN_PROMPT}}" prerequisites="relevant-context,required-approval">Use after gathering relevant context and receiving any required approval.</Operation>
105
82
  <ContextManagement>
106
- <Operation id="add" tool="{{toolConstants.AIDER_TOOL_ADD_CONTEXT_FILES}}">Add ALL files identified in Step 5 and confirmed in Step 6 that are not already in context.</Operation>
83
+ <Operation id="add" tool="{{toolConstants.AIDER_TOOL_ADD_CONTEXT_FILES}}">Add relevant files that are not already in context.</Operation>
107
84
  <Operation id="list" tool="{{toolConstants.AIDER_TOOL_GET_CONTEXT_FILES}}" />
108
85
  <Operation id="drop" tool="{{toolConstants.AIDER_TOOL_DROP_CONTEXT_FILES}}">After a task completes, remove files you explicitly added.</Operation>
109
86
  <Rule id="prompt-has-full-info">Aider sees only the prompt you send; include all relevant info.</Rule>
110
87
  </ContextManagement>
111
88
  <Utilization>
112
- <Guideline>To modify or generate code, use {{toolConstants.AIDER_TOOL_GROUP_NAME}}{{toolConstants.TOOL_GROUP_NAME_SEPARATOR}}{{toolConstants.AIDER_TOOL_RUN_PROMPT}} only after Steps 5 and 6 are complete and the plan is confirmed.</Guideline>
113
- <Guideline>Before {{toolConstants.AIDER_TOOL_RUN_PROMPT}}, use {{toolConstants.AIDER_TOOL_GROUP_NAME}}{{toolConstants.TOOL_GROUP_NAME_SEPARATOR}}{{toolConstants.AIDER_TOOL_ADD_CONTEXT_FILES}} to add ALL files identified in Step 5 and confirmed for modification in Step 6, then double-check using {{toolConstants.AIDER_TOOL_GROUP_NAME}}{{toolConstants.TOOL_GROUP_NAME_SEPARATOR}}{{toolConstants.AIDER_TOOL_GET_CONTEXT_FILES}}.</Guideline>
89
+ <Guideline>For code changes, use {{toolConstants.AIDER_TOOL_GROUP_NAME}}{{toolConstants.TOOL_GROUP_NAME_SEPARATOR}}{{toolConstants.AIDER_TOOL_RUN_PROMPT}} after gathering relevant context and receiving any required approval.</Guideline>
90
+ <Guideline>Before {{toolConstants.AIDER_TOOL_RUN_PROMPT}}, add the relevant files that are not already in context, then verify the context file list.</Guideline>
114
91
  <Guideline>Only add files that are not already in the context.</Guideline>
115
92
  <Guideline>Aider does not see prior messages; include all relevant information in the prompt.</Guideline>
116
93
  <Guideline>After a task/sub-task completes, use {{toolConstants.AIDER_TOOL_GROUP_NAME}}{{toolConstants.TOOL_GROUP_NAME_SEPARATOR}}{{toolConstants.AIDER_TOOL_DROP_CONTEXT_FILES}} to remove files you explicitly added.</Guideline>
@@ -133,20 +110,8 @@
133
110
  </Tool>
134
111
  {{/if}}
135
112
  <Utilization>
136
- {{#if toolPermissions.powerTools.semanticSearch}}<Guideline>To search for code or functionality, use {{toolConstants.POWER_TOOL_GROUP_NAME}}{{toolConstants.TOOL_GROUP_NAME_SEPARATOR}}{{toolConstants.POWER_TOOL_SEMANTIC_SEARCH}} to locate relevant code segments or features within the project.</Guideline>{{/if}}
137
- {{#if toolPermissions.powerTools.fileRead}}<Guideline>To inspect file contents, use {{toolConstants.POWER_TOOL_GROUP_NAME}}{{toolConstants.TOOL_GROUP_NAME_SEPARATOR}}{{toolConstants.POWER_TOOL_FILE_READ}} to view the content of a file without including it in the primary context.</Guideline>{{/if}}
138
- {{#if toolPermissions.powerTools.fileWrite}}<Guideline>To manage files (create, overwrite, append), use {{toolConstants.POWER_TOOL_GROUP_NAME}}{{toolConstants.TOOL_GROUP_NAME_SEPARATOR}}{{toolConstants.POWER_TOOL_FILE_WRITE}} for creating new files, replacing existing file content, or adding content to the end of a file.</Guideline>{{/if}}
139
- {{#if toolPermissions.powerTools.fileEdit}}<Guideline>To perform targeted file edits, use {{toolConstants.POWER_TOOL_GROUP_NAME}}{{toolConstants.TOOL_GROUP_NAME_SEPARATOR}}{{toolConstants.POWER_TOOL_FILE_EDIT}} to replace specific strings or patterns within files.</Guideline>{{/if}}
140
- {{#if toolPermissions.powerTools.glob}}<Guideline>To find files by pattern, use {{toolConstants.POWER_TOOL_GROUP_NAME}}{{toolConstants.TOOL_GROUP_NAME_SEPARATOR}}{{toolConstants.POWER_TOOL_GLOB}} to identify files that match specified patterns.</Guideline>{{/if}}
141
- {{#if toolPermissions.powerTools.grep}}<Guideline>To search file content with regular expressions, use {{toolConstants.POWER_TOOL_GROUP_NAME}}{{toolConstants.TOOL_GROUP_NAME_SEPARATOR}}{{toolConstants.POWER_TOOL_GREP}} to find text within files using regular expressions.</Guideline>{{/if}}
142
- {{#if toolPermissions.powerTools.bash}}<Guideline>To execute shell commands, use {{toolConstants.POWER_TOOL_GROUP_NAME}}{{toolConstants.TOOL_GROUP_NAME_SEPARATOR}}{{toolConstants.POWER_TOOL_BASH}}. <Instruction>Before execution, verify all {{toolConstants.POWER_TOOL_GROUP_NAME}}{{toolConstants.TOOL_GROUP_NAME_SEPARATOR}}{{toolConstants.POWER_TOOL_BASH}} commands for safety and correctness to prevent unintended system modifications.</Instruction></Guideline>{{/if}}
143
- {{#if toolPermissions.aiderTools}}{{#if toolPermissions.powerTools.fileEdit}}{{#if toolPermissions.powerTools.fileWrite}}
144
- <Comparison to="AiderTools">
145
- <Point>For ALL coding tasks—including writing, modifying, refactoring, or debugging code—you MUST use the `{{toolConstants.AIDER_TOOL_RUN_PROMPT}}` tool. It is designed for complex, context-aware code manipulation.</Point>
146
- <Point>Power Tools such as `{{toolConstants.POWER_TOOL_FILE_EDIT}}` or `{{toolConstants.POWER_TOOL_FILE_WRITE}}` should ONLY be used for simple, non-code text manipulations, such as fixing a typo in a comment, adjusting a configuration file, or adding a new entry to a JSON file. Using them for coding tasks is strictly prohibited as it can lead to syntax errors and incomplete changes.</Point>
147
- </Comparison>
148
- <ContextNote>Unlike Aider tools, Power tools operate directly on the file system and do not inherently use Aider's context file list unless their parameters (like file paths) are derived from it.</ContextNote>
149
- {{/if}}{{/if}}{{/if}}
113
+ <Guideline>Select the tool that best fits the required inspection or change. Follow each tool's description and safety constraints.</Guideline>
114
+ {{#if toolPermissions.powerTools.bash}}<Guideline>Verify shell commands for safety and correctness before execution.</Guideline>{{/if}}
150
115
  </Utilization>
151
116
  </PowerTools>
152
117
  {{/if}}
@@ -1,69 +1,34 @@
1
1
  {{#assign "stepNumber" 1}}{{/assign}}
2
2
  <Workflow>
3
- <Step number="{{stepNumber}}" title="Analyze User Request">
4
- <Instruction>Deconstruct the request into actionable steps. Define the overarching goal and explicit completion conditions. Think step-by-step.</Instruction>
3
+ <Step number="{{stepNumber}}" title="Choose an Approach">
4
+ <Instruction>Classify the request before acting. Answer straightforward informational requests directly after proportionate inspection. For changes, scale context gathering, planning, and verification to the scope, risk, and reversibility of the work.</Instruction>
5
5
  </Step>{{#increment "stepNumber"}}{{/increment}}
6
6
  {{#if toolPermissions.skills.allowed}}
7
- <Step number="{{stepNumber}}" title="Skills">
8
- <Instruction>If the user's request is related to any of the available skills, activate the relevant skill at the very beginning of the task using the skills tool. This must happen before retrieving memory.</Instruction>
9
- <Instruction>Only do this when skill tools are available.</Instruction>
7
+ <Step number="{{stepNumber}}" title="Load Relevant Skills">
8
+ <Instruction>When a skill matches the request, activate it before using the guidance it provides. Do not load unrelated skills.</Instruction>
10
9
  </Step>{{#increment "stepNumber"}}{{/increment}}
11
10
  {{/if}}
12
11
  {{#if toolPermissions.memory.retrieveAllowed}}
13
- <Step number="{{stepNumber}}" title="Retrieve Memory">
14
- <Instruction>Retrieve memory when the request may benefit from stored information. Use judgment: retrieve for implementation tasks, project information questions (e.g., "What providers are supported?"), configuration changes, or feature work. Skip for trivial requests (e.g., "list files", "run tests") or simple clarifications.</Instruction>
15
- <Instruction>Formulate queries based on key terms in the user's request (e.g., if asked about LLM providers, query "LLM providers" or "supported providers"; if asked about voice features, query "voice control" or "voice support").</Instruction>
16
- <Instruction>Retrieve: user preferences, architectural decisions, reusable patterns, and stable project reference information (e.g., supported providers, available features, project capabilities). Ignore only task-specific execution details, one-off bugs, or temporary implementation notes.</Instruction>
17
- <Instruction>If retrieval returns no or insufficient results, note the query and what was missing. This will be addressed in the "Fill Memory Gaps" step after analysis.</Instruction>
12
+ <Step number="{{stepNumber}}" title="Retrieve Relevant Memory">
13
+ <Instruction>Retrieve memory when durable preferences, decisions, or patterns may affect the work. Skip it for trivial requests.</Instruction>
18
14
  </Step>{{#increment "stepNumber"}}{{/increment}}
19
15
  {{/if}}
20
- <Step number="{{stepNumber}}" title="Gather Initial Context">
21
- {{#if toolPermissions.subagents}}<Instruction>For tasks requiring codebase understanding, implementation planning, or identifying relevant files, check if an available subagent's description indicates it specializes in codebase analysis. If such a subagent exists, delegate the analysis task to it otherwise follow the next instruction.</Instruction>{{/if}}
22
- <Instruction>Use {{#if toolPermissions.powerTools.anyEnabled}}power-tools{{else}}available tools (e.g., search, read file){{/if}} to understand primary areas in the <WorkingDirectory> relevant to the request.</Instruction>
16
+ <Step number="{{stepNumber}}" title="Gather Context">
17
+ <Instruction>Use available tools to inspect the files, behavior, and constraints relevant to the request. For a focused change, inspect the target and its immediate dependencies. For substantial or risky work, trace affected modules, types, callers, tests, and configuration.</Instruction>
23
18
  </Step>{{#increment "stepNumber"}}{{/increment}}
24
- {{#if toolPermissions.memory.storeAllowed}}
25
- {{#if toolPermissions.memory.retrieveAllowed}}
26
- <Step number="{{stepNumber}}" title="Fill Memory Gaps">
27
- <Instruction>If the "Retrieve Memory" step yielded no or insufficient results AND analysis in the previous step uncovered relevant, stable project knowledge, store that knowledge now so future retrievals will find it.</Instruction>
28
- <Instruction>Examples: discovered project structure patterns, key module responsibilities, how subsystems interconnect, important configuration details, or non-obvious conventions that would help future tasks.</Instruction>
29
- <Instruction>Skip this step if memory retrieval already returned adequate results, or if the discovered information is task-specific, transient, or directly derivable from a single file.</Instruction>
30
- </Step>{{#increment "stepNumber"}}{{/increment}}
31
- {{/if}}
32
- {{/if}}
33
- <Step number="{{stepNumber}}" title="Identify All Relevant Files">
34
- <Substep letter="a">Explicitly reason about all potentially affected/related files: dependencies, importers, imports, related modules, types, configs, tests, and usage examples.</Substep>
35
- <Substep letter="b">Use tools (search, grep, dependency analysis where available) to locate related files throughout <WorkingDirectory>.</Substep>
36
- <Substep letter="c">List all identified relevant files explicitly before proceeding.</Substep>
37
- <Substep letter="d" autonomyMode="{{toolPermissions.autonomyMode}}">{{#if (equals toolPermissions.autonomyMode "manual")}}Await explicit user confirmation before proceeding.{{else}}IMPORTANT: User confirmation is not required. You can proceed.{{/if}}</Substep>
19
+ <Step number="{{stepNumber}}" title="Plan Changes When Needed">
20
+ <Instruction>For non-trivial changes, identify affected files and present a concise implementation plan. For small, low-risk changes, proceed with a brief statement of intent.</Instruction>
21
+ <Instruction autonomyMode="{{toolPermissions.autonomyMode}}">{{#if (equals toolPermissions.autonomyMode "autonomous")}}After presenting a plan for non-trivial changes, proceed automatically.{{else}}For non-trivial changes, await explicit user approval before modifying files. Ask: "May I proceed? (y/n)"{{/if}}</Instruction>
38
22
  </Step>{{#increment "stepNumber"}}{{/increment}}
39
- <Step number="{{stepNumber}}" title="Develop Implementation Plan">
40
- <Instruction>Using the confirmed file list, create a comprehensive multi-file change plan.</Instruction>
41
- <Instruction autonomyMode="{{toolPermissions.autonomyMode}}">{{#if (equals toolPermissions.autonomyMode "autonomous")}}After presenting the plan, execute it automatically.{{else}}Present the plan and await explicit user approval before changes. For example: "May I proceed? (y/n)"{{/if}}</Instruction>
42
- </Step>{{#increment "stepNumber"}}{{/increment}}
43
- <Step number="{{stepNumber}}" title="Execute Implementation">
44
- <Instruction>Apply planned changes using appropriate tools. Ensure all relevant files from Step 5 are in context before modifications.</Instruction>
45
- </Step>{{#increment "stepNumber"}}{{/increment}}
46
- <Step number="{{stepNumber}}" title="Verify Changes">
47
- <Instruction>ALWAYS verify your changes. {{#if toolPermissions.subagents}}Check if an available subagent's description indicates it specializes in code verification. If such a subagent exists, delegate the verification task to it. Otherwise:{{/if}} Use available tools like linters or type checkers. Analyze outcomes and iterate to fix errors.</Instruction>
48
- </Step>{{#increment "stepNumber"}}{{/increment}}
49
- {{#if toolPermissions.subagents}}
50
- <Step number="{{stepNumber}}" title="Review Changes">
51
- <Instruction>After verification, especially for complex modifications, use a specialized subagent that describes itself as an expert for code review to ensure high quality and adherence to best practices.</Instruction>
52
- </Step>{{#increment "stepNumber"}}{{/increment}}
53
- {{/if}}
54
- <Step number="{{stepNumber}}" title="Assess Task Completion">
55
- <Instruction>Evaluate whether completion conditions are met; loop back if not. Consider using a specialized subagent for review or testing if available.</Instruction>
23
+ <Step number="{{stepNumber}}" title="Implement and Verify">
24
+ <Instruction>Apply the approved changes with appropriate tools. Verify proportionately: inspect the result for small edits; run relevant tests, type checks, linters, or other validation for broader or riskier changes. Investigate and fix failures caused by the work.</Instruction>
56
25
  </Step>{{#increment "stepNumber"}}{{/increment}}
57
26
  {{#if toolPermissions.memory.storeAllowed}}
58
- <Step number="{{stepNumber}}" title="Store Memory">
59
- <Instruction>Proactively store information that meets the eligibility criteria. Default to storing nothing only when eligibility is borderline or unclear.</Instruction>
60
- <Instruction>Store a memory ONLY if ALL are true: (1) reusable across future tasks, (2) stable (unlikely to change soon), (3) actionable (changes future behavior), and (4) it is a user preference, an architectural decision, a repeated codebase pattern, or stable project reference information.</Instruction>
61
- <Instruction>NEVER store: task progress/status, one-off bug details, implementation details (how something was coded, specific file contents), transient implementation notes, file lists from a single task, logs/stack traces, secrets/tokens/credentials/PII, or frequently-changing/version-specific information.</Instruction>
62
- <Instruction>Derivatives to avoid: only store information that requires synthesis from multiple files or represents high-level project facts. Do NOT store information instantly readable from a single location (e.g., "line 42 of file X says Y").</Instruction>
63
- <Instruction>If the user explicitly asks to "remember" something, store it only if it is not disallowed above.</Instruction>
27
+ <Step number="{{stepNumber}}" title="Store Durable Memory">
28
+ <Instruction>Store a memory only when the work revealed a reusable, stable, actionable preference, architectural decision, or repeated pattern.</Instruction>
64
29
  </Step>{{#increment "stepNumber"}}{{/increment}}
65
30
  {{/if}}
66
- <Step number="{{stepNumber}}" title="Final Summary">
67
- <Instruction>Summarize actions and confirm the overarching goal is achieved.</Instruction>
31
+ <Step number="{{stepNumber}}" title="Respond">
32
+ <Instruction>State the outcome concisely, including verification or any remaining limitation.</Instruction>
68
33
  </Step>
69
34
  </Workflow>
@@ -275,6 +275,7 @@ After completing this skill, verify:
275
275
  - Execute commands in subtask: `await subtaskContext?.runCustomCommand('scope:start')`
276
276
  - Read subtask conversation: `const messages = await subtaskContext?.getContextMessages()`
277
277
  - List all tasks: `const allTasks = await projectContext.getTasks()`
278
+ - Reload tasks from disk after external task-folder changes: `const allTasks = await projectContext.reloadTasks()`
278
279
  - Fork at specific message: `await projectContext.forkTask(taskId, messageId)`
279
280
  - Duplicate a task: `await projectContext.duplicateTask(taskId)`
280
281
  - Delete a task: `await projectContext.deleteTask(taskId)`
@@ -17,6 +17,7 @@ Every Extension interface method dispatches a specific event type. All handlers
17
17
  | `onTaskInitialized` | `TaskInitializedEvent` | — |
18
18
  | `onTaskClosed` | `TaskClosedEvent` | — |
19
19
  | `onTaskUpdated` | `TaskUpdatedEvent` | — |
20
+ | `onTaskDeleted` | `TaskDeletedEvent` | ✅ Yes |
20
21
  | `onProjectStarted` | `ProjectStartedEvent` | — |
21
22
  | `onProjectStopped` | `ProjectStoppedEvent` | — |
22
23
  | `onPromptStarted` | `PromptStartedEvent` | ✅ Yes |
@@ -57,7 +58,7 @@ Events with a `blocked?: boolean` field allow extensions to **block** the operat
57
58
 
58
59
  | Capability | Events |
59
60
  |---|---|
60
- | **Can Block** (have `blocked?` field) | `PromptStartedEvent`, `AgentStartedEvent`, `InterruptedEvent`, `ToolApprovalEvent`, `ToolCalledEvent`, `HandleApprovalEvent`, `SubagentStartedEvent`, `CommandExecutedEvent`, `CustomCommandExecutedEvent`, `AiderPromptStartedEvent`, `BeforeCommitEvent` |
61
+ | **Can Block** (have `blocked?` field) | `PromptStartedEvent`, `AgentStartedEvent`, `InterruptedEvent`, `ToolApprovalEvent`, `ToolCalledEvent`, `HandleApprovalEvent`, `SubagentStartedEvent`, `CommandExecutedEvent`, `CustomCommandExecutedEvent`, `AiderPromptStartedEvent`, `BeforeCommitEvent`, `TaskDeletedEvent` |
61
62
  | **Read-Only** (all fields `readonly`) | `TaskInitializedEvent`, `TaskClosedEvent`, `ProjectStartedEvent`, `ProjectStoppedEvent`, `AfterCommitEvent` |
62
63
 
63
64
  ---
@@ -114,6 +115,17 @@ interface TaskUpdatedEvent {
114
115
  }
115
116
  ```
116
117
 
118
+ ### TaskDeletedEvent (Can Block)
119
+
120
+ Dispatched when a task is about to be deleted. Set `blocked: true` to prevent deletion.
121
+
122
+ ```typescript
123
+ interface TaskDeletedEvent {
124
+ readonly task: TaskData;
125
+ blocked?: boolean;
126
+ }
127
+ ```
128
+
117
129
  ---
118
130
 
119
131
  ## Project Events
@@ -199,9 +211,13 @@ interface AgentStartedEvent {
199
211
  blocked?: boolean;
200
212
  images?: string[];
201
213
  skillsToActivate?: string[];
214
+ /** Computed defaults on dispatch; returned overrides are merged with them. */
215
+ modelCallSettings?: ModelCallSettings;
202
216
  }
203
217
  ```
204
218
 
219
+ Use `modelCallSettings` to override AI SDK model-call parameters. The dispatched value includes computed defaults such as `maxRetries` and `abortSignal`; return only the settings to override.
220
+
205
221
  ### AgentFinishedEvent
206
222
 
207
223
  Dispatched when the agent has finished processing.
@@ -626,6 +642,27 @@ async onAgentStarted(
626
642
  }
627
643
  ```
628
644
 
645
+ ### Overriding Model Call Settings
646
+
647
+ Override AI SDK model-call parameters when the agent starts. Return only the values to change; they are merged with the computed defaults in `event.modelCallSettings`.
648
+
649
+ ```typescript
650
+ async onAgentStarted(
651
+ event: AgentStartedEvent,
652
+ context: ExtensionContext
653
+ ): Promise<Partial<AgentStartedEvent>> {
654
+ return {
655
+ modelCallSettings: {
656
+ temperature: 0.2,
657
+ maxOutputTokens: 4096,
658
+ timeout: { totalMs: 120_000 },
659
+ },
660
+ };
661
+ }
662
+ ```
663
+
664
+ Use either `temperature` or `topP` for sampling. Set `reasoning` to use AI SDK's portable reasoning control, which takes precedence over provider-specific reasoning options.
665
+
629
666
  ### Modifying Files
630
667
 
631
668
  Add or filter context files before they are added:
@@ -304,6 +304,10 @@ interface ExtensionContext {
304
304
  /** Get the current project directory path. Returns empty string when no project is available. */
305
305
  getProjectDir(): string;
306
306
 
307
+ /** Get the base directories of all currently open projects (open project tabs/windows).
308
+ * Available regardless of whether the context itself is scoped to a project or task. */
309
+ getOpenProjectDirs(): string[];
310
+
307
311
  /** Get the task context for the current task. Returns null when no task is available. */
308
312
  getTaskContext(): TaskContext | null;
309
313
 
@@ -668,6 +672,17 @@ interface TaskContext {
668
672
  /** Merge commits and optionally uncommitted changes from this task's worktree to a target worktree directory. */
669
673
  mergeWorktreeToWorktree(targetWorktreeDir: string, includeUncommitted?: boolean): Promise<void>;
670
674
  }
675
+
676
+ ### Resume
677
+
678
+ ```typescript
679
+ interface TaskContext {
680
+ /** Resume the task — starts execution as if the user clicked the "Execute"/"Resume" button.
681
+ * In agent mode, this runs the last user prompt through the agent pipeline.
682
+ * In Aider modes, this re-executes the last user message.
683
+ * No-op if the task is already running or has no prior user message to resume from. */
684
+ resumeTask(): Promise<void>;
685
+ }
671
686
  ```
672
687
 
673
688
  ---
@@ -813,6 +828,40 @@ interface ResponseMessage {
813
828
  }
814
829
  ```
815
830
 
831
+ ### ModelCallSettings
832
+
833
+ Used with `AgentStartedEvent.modelCallSettings` to override AI SDK model-call parameters. On dispatch, it contains computed defaults such as `maxRetries` and `abortSignal`; a returned partial value is merged with those defaults.
834
+
835
+ ```typescript
836
+ type Reasoning = 'provider-default' | 'none' | 'minimal' | 'low' | 'medium' | 'high' | 'xhigh';
837
+
838
+ interface ModelCallTimeout {
839
+ totalMs?: number;
840
+ stepMs?: number;
841
+ chunkMs?: number;
842
+ toolMs?: number;
843
+ tools?: Record<string, number>;
844
+ }
845
+
846
+ interface ModelCallSettings {
847
+ maxOutputTokens?: number;
848
+ temperature?: number;
849
+ topP?: number;
850
+ topK?: number;
851
+ presencePenalty?: number;
852
+ frequencyPenalty?: number;
853
+ stopSequences?: string[];
854
+ seed?: number;
855
+ reasoning?: Reasoning;
856
+ maxRetries?: number;
857
+ abortSignal?: AbortSignal;
858
+ timeout?: number | ModelCallTimeout;
859
+ headers?: Record<string, string>;
860
+ }
861
+ ```
862
+
863
+ Use either `temperature` or `topP` for sampling. When `reasoning` is specified, it takes precedence over provider-specific reasoning options.
864
+
816
865
  ### QuestionOptions
817
866
 
818
867
  > ⚠️ **CRITICAL:** There is **no `options` field** on `QuestionOptions`. Multiple-choice answers are provided via the **`answers`** array, where each entry has `{ text, shortkey }`.
@@ -948,6 +997,7 @@ type UIComponentPlacement =
948
997
  | 'task-top-bar-right'
949
998
  | 'task-state-actions'
950
999
  | 'task-state-actions-all'
1000
+ | 'task-sidebar-item-badges'
951
1001
  | 'welcome-page'
952
1002
  | 'task-floating'
953
1003
  | 'project-floating'
@@ -145,6 +145,12 @@ UI components can be placed in various locations throughout the AiderDesk interf
145
145
  - *Use for*: Persistent sidebar actions, status
146
146
  - *Layout*: Full sidebar width at bottom
147
147
 
148
+ - **task-sidebar-item-badges**: Inside each task item in the sidebar (between state chip and worktree badge)
149
+ - *Use for*: Per-task badges, indicators, schedule status icons
150
+ - *Layout*: Inline, compact — renders directly in each sidebar task row
151
+ - *Props*: Receives `task` (the TaskData for this specific sidebar item) and `taskId`
152
+ - *Important*: Unlike most placements, this renders **once per task** in the sidebar, not just for the active task. Use `loadData: true` and `noDataCache: true` so each item fetches its own data. Call `context.triggerUIDataRefresh(componentId, taskId)` to refresh a specific task's badge.
153
+
148
154
  ### Global Placements
149
155
 
150
156
  - **header-left**: Left side of the main application header