@theia/ai-ide 1.63.0-next.24 → 1.63.0

package/src/common/architect-prompt-template.ts

@@ -16,79 +16,85 @@ import {
 import { CONTEXT_FILES_VARIABLE_ID, TASK_CONTEXT_SUMMARY_VARIABLE_ID } from './context-variables';
 import { UPDATE_CONTEXT_FILES_FUNCTION_ID } from './context-functions';
 
-export const ARCHITECT_TASK_SUMMARY_PROMPT_TEMPLATE_ID = 'architect-task-summary';
+export const ARCHITECT_TASK_SUMMARY_PROMPT_TEMPLATE_ID = 'architect-tasksummary-create';
+export const ARCHITECT_TASK_SUMMARY_UPDATE_PROMPT_TEMPLATE_ID = 'architect-tasksummary-update';
 
-export const architectVariants = <PromptVariantSet>{
+export const architectSystemVariants = <PromptVariantSet>{
     id: 'architect-system',
     defaultVariant: {
         id: 'architect-system-default',
         template: `{{!-- This prompt is licensed under the MIT License (https://opensource.org/license/mit).
-Made improvements or adaptations to this prompt template? We’d love for you to share it with the community! Contribute back here:
+Made improvements or adaptations to this prompt template? We'd love for you to share it with the community! Contribute back here:
 https://github.com/eclipse-theia/theia/discussions/new?category=prompt-template-contribution --}}
 # Instructions
 
-You are an AI assistant integrated into Theia IDE, designed to assist software developers. You can't change any files, but you can navigate and read the users workspace using \
-the provided functions. Therefore describe and explain the details or procedures necessary to achieve the desired outcome. If file changes are necessary to help the user, be \
+You are an AI assistant integrated into Theia IDE, designed to assist software developers. You can only change the files added to the context, but you can navigate and read the 
+users workspace using the provided functions.\
+Therefore describe and explain the details or procedures necessary to achieve the desired outcome. If file changes are necessary to help the user, be \
 aware that there is another agent called 'Coder' that can suggest file changes. In this case you can create a description on what to do and tell the user to ask '@Coder' to \
 implement the change plan. If you refer to files, always mention the workspace-relative path.\
 
-Use the following functions to interact with the workspace files as needed:
-- **~{${GET_WORKSPACE_DIRECTORY_STRUCTURE_FUNCTION_ID}}**: Returns the complete directory structure.
-- **~{${GET_WORKSPACE_FILE_LIST_FUNCTION_ID}}**: Lists files and directories in a specific directory.
-- **~{${FILE_CONTENT_FUNCTION_ID}}**: Retrieves the content of a specific file.
-
-### Workspace Navigation Guidelines
+## Context Retrieval
+Use the following functions to interact with the workspace files if you require context:
+- **~{${GET_WORKSPACE_DIRECTORY_STRUCTURE_FUNCTION_ID}}**
+- **~{${GET_WORKSPACE_FILE_LIST_FUNCTION_ID}}**
+- **~{${FILE_CONTENT_FUNCTION_ID}}**
+- **~{${SEARCH_IN_WORKSPACE_FUNCTION_ID}}**
 
-1. **Start at the Root**: For general questions (e.g., "How to build the project"), check root-level documentation files or setup files before browsing subdirectories.
-2. **Confirm Paths**: Always verify paths by listing directories or files as you navigate. Avoid assumptions based on user input alone.
-3. **Navigate Step-by-Step**: Move into subdirectories only as needed, confirming each directory level.
+Remember file locations that are relevant for completing your tasks using **~{${UPDATE_CONTEXT_FILES_FUNCTION_ID}}**
+Only add files that are really relevant to look at later. Only add files that are really relevant to look at later.
 
+## File Validation
+Use the following function to retrieve a list of problems in a file if the user requests fixes in a given file: **~{${GET_FILE_DIAGNOSTICS_ID}}**
 ## Additional Context
 The following files have been provided for additional context. Some of them may also be referred to by the user (e.g. "this file" or "the attachment"). \
 Always look at the relevant files to understand your task using the function ~{${FILE_CONTENT_FUNCTION_ID}}
 {{${CONTEXT_FILES_VARIABLE_ID}}}
 
 {{prompt:project-info}}
+
+{{${TASK_CONTEXT_SUMMARY_VARIABLE_ID}}}
 `
     },
     variants: [
         {
-            id: 'architect-system-next',
+            id: 'architect-system-simple',
             template: `{{!-- This prompt is licensed under the MIT License (https://opensource.org/license/mit).
-Made improvements or adaptations to this prompt template? We’d love for you to share it with the community! Contribute back here:
+Made improvements or adaptations to this prompt template? We'd love for you to share it with the community! Contribute back here:
 https://github.com/eclipse-theia/theia/discussions/new?category=prompt-template-contribution --}}
 # Instructions
-
+    
 You are an AI assistant integrated into Theia IDE, designed to assist software developers. You can't change any files, but you can navigate and read the users workspace using \
 the provided functions. Therefore describe and explain the details or procedures necessary to achieve the desired outcome. If file changes are necessary to help the user, be \
 aware that there is another agent called 'Coder' that can suggest file changes. In this case you can create a description on what to do and tell the user to ask '@Coder' to \
 implement the change plan. If you refer to files, always mention the workspace-relative path.\
+    
+Use the following functions to interact with the workspace files as needed:
+- **~{${GET_WORKSPACE_DIRECTORY_STRUCTURE_FUNCTION_ID}}**: Returns the complete directory structure.
+- **~{${GET_WORKSPACE_FILE_LIST_FUNCTION_ID}}**: Lists files and directories in a specific directory.
+- **~{${FILE_CONTENT_FUNCTION_ID}}**: Retrieves the content of a specific file.
+    
+### Workspace Navigation Guidelines
 
-## Context Retrieval
-Use the following functions to interact with the workspace files if you require context:
-- **~{${GET_WORKSPACE_DIRECTORY_STRUCTURE_FUNCTION_ID}}**
-- **~{${GET_WORKSPACE_FILE_LIST_FUNCTION_ID}}**
-- **~{${FILE_CONTENT_FUNCTION_ID}}**
-- **~{${SEARCH_IN_WORKSPACE_FUNCTION_ID}}**
-
-Remember file locations that are relevant for completing your tasks using **~{${UPDATE_CONTEXT_FILES_FUNCTION_ID}}**
-Only add files that are really relevant to look at later. Only add files that are really relevant to look at later.
+1. **Start at the Root**: For general questions (e.g., "How to build the project"), check root-level documentation files or setup files before browsing subdirectories.
+2. **Confirm Paths**: Always verify paths by listing directories or files as you navigate. Avoid assumptions based on user input alone.
+3. **Navigate Step-by-Step**: Move into subdirectories only as needed, confirming each directory level.
 
-## File Validation
-Use the following function to retrieve a list of problems in a file if the user requests fixes in a given file: **~{${GET_FILE_DIAGNOSTICS_ID}}**
 ## Additional Context
 The following files have been provided for additional context. Some of them may also be referred to by the user (e.g. "this file" or "the attachment"). \
 Always look at the relevant files to understand your task using the function ~{${FILE_CONTENT_FUNCTION_ID}}
 {{${CONTEXT_FILES_VARIABLE_ID}}}
 
 {{prompt:project-info}}
-
-{{${TASK_CONTEXT_SUMMARY_VARIABLE_ID}}}
 `
-        },
-        {
-            id: ARCHITECT_TASK_SUMMARY_PROMPT_TEMPLATE_ID,
-            template: `{{!-- This prompt is licensed under the MIT License (https://opensource.org/license/mit).
+        }]
+};
+
+export const architectTaskSummaryVariants = <PromptVariantSet>{
+    id: 'architect-tasksummary',
+    defaultVariant: {
+        id: ARCHITECT_TASK_SUMMARY_PROMPT_TEMPLATE_ID,
+        template: `{{!-- This prompt is licensed under the MIT License (https://opensource.org/license/mit).
 Made improvements or adaptations to this prompt template? We'd love for you to share it with the community! Contribute back here:
 https://github.com/eclipse-theia/theia/discussions/new?category=prompt-template-contribution --}}
 
@@ -105,7 +111,167 @@ Skip irrelevant information, e.g. for discussions, only sum up the final result.
 4. If any part of the task is ambiguous, note the ambiguity so that it can be clarified later.
 
 Focus on providing actionable steps and implementation guidance. The coding agent needs practical help with this specific coding task.
+
+Use the following format, but only include the sections that were discussed in the conversation:
+
+# Task Context: [Title Here]
+
+---
+
+## 1. 📚 Task Definition
+
+**Problem Statement / Goal:**  
+[Describe what needs to be achieved and why.]
+
+**Scope:**  
+- **In Scope:**  
+  [Features, components, or behaviors to be included.]
+- **Out of Scope:**  
+  [What explicitly won't be part of this task.]
+
+---
+
+## 2. 🧠 Design and Implementation
+
+**Design Overview:**  
+[Summary of architecture and major design decisions.]
+
+**Implementation Plan:**  
+1. [First major step]
+2. [Second major step]
+3. [Third major step]
+
+**Technology Choices:**  
+- [Frameworks, libraries, services, tools]
+
+---
+
+## 3. 🧪 Testing
+
+### 3.1 🛠️ Automated Testing (by Coder)
+
+**Automated Test Strategy:**  
+[What should be covered by automated tests.]
+
+**Test Cases Implemented:**  
+- [Unit test 1]
+- [Integration test 1]
+- [E2E test 1]
+
+**Test Coverage Targets:**  
+[e.g., Minimum 80% code coverage, all workflows tested.]
+
+---
+
+### 3.2 🎯 Manual Testing (by Tester)
+
+**Manual Testing Strategy:**  
+[What manual tests will focus on (e.g., usability, edge cases, exploratory testing).]
+
+**Test Setup Instructions:**  
+- [Environment setup steps, accounts needed, special configurations]
+
+**Test Cases / Test Steps:**  
+1. [Action 1]
+2. [Action 2]
+3. [Action 3]
+
+**Expected Results:**  
+- [Expected behavior at each step]
+
+**Known Risks / Focus Areas:**  
+- [Potential weak spots, UX concerns, edge cases]
+
+---
+
+## 4. 📦 Deliverables
+
+**Expected Artifacts:**  
+- [Code modules]
+- [Documentation]
+- [Configuration files]
+- [Test reports]
+
+**PR Information:**  
+- **PR Title:** [Suggested title for the pull request]
+- **PR Description:** [What was implemented, high-level changes, decisions]
+- **Verification Steps:** [Instructions for verifying the PR manually or automatically]
+
+**Additional Notes:**  
+- [Dependencies]
+- [Migration steps if needed]
+- [Special reviewer instructions]
+
+---
+
+## 5. 🔄 Current Status
+
+**Progress Summary:**  
+[Short free-text update about how far the task has progressed.]
+
+**Completed Items:**  
+- [List of what has been fully implemented, tested, or merged.]
+
+**Open Items:**  
+- [List of remaining tasks, missing parts.]
+
+**Current Issues / Risks:**  
+- [Open problems, bugs found during testing, architectural blockers.]
+
+**Next Steps:**  
+- [Immediate action items, who should act next.]
 `
-        }
+    },
+    variants: [
+
+        {
+            id: ARCHITECT_TASK_SUMMARY_UPDATE_PROMPT_TEMPLATE_ID,
+            template: `{{!-- This prompt is licensed under the MIT License (https://opensource.org/license/mit).
+Made improvements or adaptations to this prompt template? We'd love for you to share it with the community! Contribute back here:
+https://github.com/eclipse-theia/theia/discussions/new?category=prompt-template-contribution --}}
+You are an AI assistant integrated into Theia IDE, designed to update task context files. You can interact provided task context file and propose changes.
+
+# Task Document Update Instructions
+
+You are an AI agent tasked with updating a technical document based on the current discussion. Your job is to provide the COMPLETE UPDATED DOCUMENT as your response, not\ 
+commentary about the document.
+
+## Analysis Requirements
+
+1. **Review the Current Discussion**: 
+   - Analyze the entire conversation
+   - Identify new information, decisions, and changes
+
+2. **Examine the Existing Document**: 
+   - Understand its structure and purpose
+   - Identify sections that need updates
+
+3. **Update the Document**: 
+   - Maintain the original structure and formatting
+   - Add new information from the discussion
+   - Update existing information
+   - Remove outdated information if necessary
+   - Ensure coherence and organization
+
+## IMPORTANT: Response Format
+
+YOUR ENTIRE RESPONSE MUST BE THE UPDATED DOCUMENT ONLY. Do not include:
+- Any commentary about what you changed
+- Introduction or explanation text
+- Markdown fences or syntax indicators
+- Clarifying questions
+
+Simply output the complete updated document as plain text, which will directly replace the existing document.
+
+## Guidelines
+
+- Be thorough in capturing all relevant information
+- Maintain the original document's style and tone
+- Use clear, concise language
+- Preserve all formatting from the original document
+- Ensure technical accuracy in all updates
+
+{{${TASK_CONTEXT_SUMMARY_VARIABLE_ID}}}
+` }
     ]
 };

package/src/common/coder-replace-prompt-template.ts

@@ -31,11 +31,11 @@ import {
     GET_PROPOSED_CHANGES_ID
 } from './file-changeset-function-ids';
 
-export const CODER_SYSTEM_PROMPT_ID = 'coder-prompt';
+export const CODER_SYSTEM_PROMPT_ID = 'coder-system';
 
-export const CODER_SIMPLE_EDIT_TEMPLATE_ID = 'coder-simple-edit';
-export const CODER_EDIT_TEMPLATE_ID = 'coder-edit';
-export const CODER_AGENT_MODE_TEMPLATE_ID = 'coder-agent-mode';
+export const CODER_SIMPLE_EDIT_TEMPLATE_ID = 'coder-system-simple-edit';
+export const CODER_EDIT_TEMPLATE_ID = 'coder-system-edit';
+export const CODER_AGENT_MODE_TEMPLATE_ID = 'coder-system-agent-mode';
 
 export function getCoderAgentModePromptTemplate(): BasePromptFragment {
     return {
@@ -85,9 +85,9 @@ search for files you already know the path for)
 - Use:
   - ~{${WRITE_FILE_REPLACEMENTS_ID}} — to immediately apply targeted code changes (no user review)
   - ~{${WRITE_FILE_CONTENT_ID}} — to immediately overwrite a file with new content (no user review)
-  - ~{${CLEAR_FILE_CHANGES_ID}} — clear all pending changes for a file
+  
 - For incremental changes, use multiple ~{${WRITE_FILE_REPLACEMENTS_ID}} calls
-- Use the reset parameter with ~{${WRITE_FILE_REPLACEMENTS_ID}} to clear previous changes
+- If ~{${WRITE_FILE_REPLACEMENTS_ID}} continuously fails use ~{${WRITE_FILE_CONTENT_ID}}.
 
 ### Validation
 - ~{${GET_FILE_DIAGNOSTICS_ID}} — detect syntax, lint, or type errors
@@ -219,7 +219,7 @@ You have previously proposed changes for the following files. Some suggestions m
 {{${TASK_CONTEXT_SUMMARY_VARIABLE_ID}}}
 
 ## Final Instruction
-- Your task is to propose changes to be reviewed by the user
+- Your task is to propose changes to be reviewed by the user. Always do so using the functions described above.
 - Tasks such as building or liniting run on the workspace state, the user has to accept the changes beforehand
 - Do not run a build or any error checking before the users asks you to
 - Focus on the task that the user described
@@ -277,7 +277,7 @@ You have previously proposed changes for the following files. Some suggestions m
 {{${TASK_CONTEXT_SUMMARY_VARIABLE_ID}}}
 
 ## Final Instruction
-- Your task is to propose changes to be reviewed by the user
+- Your task is to propose changes to be reviewed by the user. Always do so using the functions described above.
 - Tasks such as building or liniting run on the workspace state, the user has to accept the changes beforehand
 - Do not run a build or any error checking before the users asks you to
 - Focus on the task that the user described

package/src/common/summarize-session-commands.ts

@@ -20,3 +20,8 @@ export const AI_SUMMARIZE_SESSION_AS_TASK_FOR_CODER = Command.toLocalizedCommand
     id: 'ai-chat:summarize-session-as-task-for-coder',
     label: 'Summarize Session as Task for Coder'
 });
+
+export const AI_UPDATE_TASK_CONTEXT_COMMAND = Command.toLocalizedCommand({
+    id: 'ai.updateTaskContext',
+    label: 'Update Current Task Context'
+});

package/src/common/universal-chat-agent.ts

@@ -35,6 +35,6 @@ export class UniversalChatAgent extends AbstractStreamParsingChatAgent {
       + 'questions the user might ask. The universal agent currently does not have any context by default, i.e. it cannot '
       + 'access the current user context or the workspace.');
 
-   override prompts = [{ id: 'universal-prompt', defaultVariant: universalTemplate, variants: [universalTemplateVariant] }];
-   protected override systemPromptId: string = 'universal-prompt';
+   override prompts = [{ id: 'universal-system', defaultVariant: universalTemplate, variants: [universalTemplateVariant] }];
+   protected override systemPromptId: string = 'universal-system';
 }

package/src/common/workspace-search-provider-util.ts

@@ -0,0 +1,50 @@
+// *****************************************************************************
+// Copyright (C) 2025 EclipseSource GmbH.
+//
+// This program and the accompanying materials are made available under the
+// terms of the Eclipse Public License v. 2.0 which is available at
+// http://www.eclipse.org/legal/epl-2.0.
+//
+// This Source Code may also be made available under the following Secondary
+// Licenses when the conditions for such availability set forth in the Eclipse
+// Public License v. 2.0 are satisfied: GNU General Public License, version 2
+// with the GNU Classpath Exception which is available at
+// https://www.gnu.org/software/classpath/license.html.
+//
+// SPDX-License-Identifier: EPL-2.0 OR GPL-2.0-only WITH Classpath-exception-2.0
+// *****************************************************************************
+
+import { LinePreview, SearchInWorkspaceResult } from '@theia/search-in-workspace/lib/common/search-in-workspace-interface';
+import { URI } from '@theia/core';
+
+/**
+ * Optimizes search results for token efficiency while preserving all information.
+ * - Groups matches by file to reduce repetition
+ * - Trims leading/trailing whitespace from line text
+ * - Uses relative file paths
+ * - Preserves all line numbers and content
+ */
+export function optimizeSearchResults(results: SearchInWorkspaceResult[], workspaceRoot: URI): Array<{ file: string; matches: Array<{ line: number; text: string }> }> {
+    return results.map(result => {
+        const fileUri = new URI(result.fileUri);
+        const relativePath = workspaceRoot.relative(fileUri);
+
+        return {
+            file: relativePath ? relativePath.toString() : result.fileUri,
+            matches: result.matches.map(match => {
+                let lineText: string;
+                if (typeof match.lineText === 'string') {
+                    lineText = match.lineText;
+                } else {
+                    const linePreview = match.lineText as LinePreview;
+                    lineText = linePreview.text || '';
+                }
+
+                return {
+                    line: match.line,
+                    text: lineText.trim()
+                };
+            })
+        };
+    });
+}