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

package/src/browser/workspace-functions.ts

@@ -157,27 +157,26 @@ export class GetWorkspaceDirectoryStructure implements ToolProvider {
     @inject(WorkspaceFunctionScope)
     protected workspaceScope: WorkspaceFunctionScope;
 
-    private async getDirectoryStructure(): Promise<string[]> {
+    private async getDirectoryStructure(): Promise<Record<string, unknown>> {
         let workspaceRoot;
         try {
             workspaceRoot = await this.workspaceScope.getWorkspaceRoot();
         } catch (error) {
-            return [`Error: ${error.message}`];
+            return { error: error.message };
         }
 
         return this.buildDirectoryStructure(workspaceRoot);
     }
 
-    private async buildDirectoryStructure(uri: URI, prefix: string = ''): Promise<string[]> {
+    private async buildDirectoryStructure(uri: URI): Promise<Record<string, unknown>> {
         const stat = await this.fileService.resolve(uri);
-        const result: string[] = [];
+        const result: Record<string, unknown> = {};
 
         if (stat && stat.isDirectory && stat.children) {
             for (const child of stat.children) {
                 if (!child.isDirectory || await this.workspaceScope.shouldExclude(child)) { continue; };
-                const path = `${prefix}${child.resource.path.base}/`;
-                result.push(path);
-                result.push(...await this.buildDirectoryStructure(child.resource, `${path}`));
+                const dirName = child.resource.path.base;
+                result[dirName] = await this.buildDirectoryStructure(child.resource);
             }
         }
 
@@ -323,10 +322,7 @@ export class GetWorkspaceFileList implements ToolProvider {
                     if (await this.workspaceScope.shouldExclude(child)) {
                         continue;
                     };
-                    const relativePath = workspaceRootUri.relative(child.resource);
-                    if (relativePath) {
-                        result.push(relativePath.toString());
-                    }
+                    result.push(child.resource.path.base);
                 }
             }
         }

package/src/browser/workspace-search-provider.ts

@@ -16,11 +16,12 @@
 
 import { MutableChatRequestModel } from '@theia/ai-chat';
 import { ToolProvider, ToolRequest } from '@theia/ai-core';
-import { CancellationToken } from '@theia/core';
+import { CancellationToken, URI } from '@theia/core';
 import { inject, injectable } from '@theia/core/shared/inversify';
 import { SearchInWorkspaceService, SearchInWorkspaceCallbacks } from '@theia/search-in-workspace/lib/browser/search-in-workspace-service';
 import { SearchInWorkspaceResult, SearchInWorkspaceOptions } from '@theia/search-in-workspace/lib/common/search-in-workspace-interface';
 import { SEARCH_IN_WORKSPACE_FUNCTION_ID } from '../common/workspace-functions';
+import { WorkspaceFunctionScope } from './workspace-functions';
 
 @injectable()
 export class WorkspaceSearchProvider implements ToolProvider {
@@ -28,6 +29,9 @@ export class WorkspaceSearchProvider implements ToolProvider {
     @inject(SearchInWorkspaceService)
     protected readonly searchService: SearchInWorkspaceService;
 
+    @inject(WorkspaceFunctionScope)
+    protected readonly workspaceScope: WorkspaceFunctionScope;
+
     private readonly MAX_RESULTS = 50;
 
     getTool(): ToolRequest {
@@ -38,6 +42,7 @@ export class WorkspaceSearchProvider implements ToolProvider {
             The search uses case-insensitive string matching or regular expressions (controlled by the `useRegExp` parameter). \
             It returns a list of matching files, including the file path (URI), the line number, and the full text content of each matching line. \
             Multi-word patterns must match exactly (including spaces, case-insensitively). \
+            For best results, use specific search terms and consider filtering by file extensions to avoid overwhelming results. \
             For complex searches, prefer multiple simpler queries over one complex query or regular expression.',
             parameters: {
                 type: 'object',
@@ -49,6 +54,13 @@ export class WorkspaceSearchProvider implements ToolProvider {
                     useRegExp: {
                         type: 'boolean',
                         description: 'Set to true if the query is a regular expression.',
+                    },
+                    fileExtensions: {
+                        type: 'array',
+                        items: {
+                            type: 'string'
+                        },
+                        description: 'Optional array of file extensions to search in (e.g., ["ts", "js", "py"]). If not specified, searches all files.'
                     }
                 },
                 required: ['query', 'useRegExp']
@@ -59,7 +71,7 @@ export class WorkspaceSearchProvider implements ToolProvider {
 
     private async handleSearch(argString: string, cancellationToken?: CancellationToken): Promise<string> {
         try {
-            const args: { query: string, useRegExp: boolean } = JSON.parse(argString);
+            const args: { query: string, useRegExp: boolean, fileExtensions?: string[] } = JSON.parse(argString);
             const results: SearchInWorkspaceResult[] = [];
             let expectedSearchId: number | undefined;
             let searchCompleted = false;
@@ -102,6 +114,10 @@ export class WorkspaceSearchProvider implements ToolProvider {
                     maxResults: this.MAX_RESULTS,
                 };
 
+                if (args.fileExtensions && args.fileExtensions.length > 0) {
+                    options.include = args.fileExtensions.map(ext => `**/*.${ext}`);
+                }
+
                 this.searchService.search(args.query, callbacks, options)
                     .then(id => {
                         expectedSearchId = id;
@@ -128,10 +144,15 @@ export class WorkspaceSearchProvider implements ToolProvider {
 
             const finalResults = await Promise.race([searchPromise, timeoutPromise]);
 
-            const formattedResults = finalResults.map(r => ({
-                file: r.fileUri,
-                matches: r.matches.map(m => ({ line: m.line, text: m.lineText }))
-            }));
+            const workspaceRoot = await this.workspaceScope.getWorkspaceRoot();
+            const formattedResults = finalResults.map(r => {
+                const fileUri = new URI(r.fileUri);
+                const relativePath = workspaceRoot.relative(fileUri);
+                return {
+                    file: relativePath ? relativePath.toString() : r.fileUri,
+                    matches: r.matches.map(m => ({ line: m.line, text: m.lineText }))
+                };
+            });
 
             return JSON.stringify(formattedResults);
 

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

@@ -22,18 +22,26 @@ import {
 } from './workspace-functions';
 import { CONTEXT_FILES_VARIABLE_ID, TASK_CONTEXT_SUMMARY_VARIABLE_ID } from './context-variables';
 import { UPDATE_CONTEXT_FILES_FUNCTION_ID } from './context-functions';
+import {
+    SUGGEST_FILE_CONTENT_ID,
+    WRITE_FILE_CONTENT_ID,
+    SUGGEST_FILE_REPLACEMENTS_ID,
+    WRITE_FILE_REPLACEMENTS_ID,
+    CLEAR_FILE_CHANGES_ID,
+    GET_PROPOSED_CHANGES_ID
+} from './file-changeset-function-ids';
 
 export const CODER_SYSTEM_PROMPT_ID = 'coder-prompt';
-export const CODER_REWRITE_PROMPT_TEMPLATE_ID = 'coder-rewrite';
-export const CODER_REPLACE_PROMPT_TEMPLATE_ID = 'coder-search-replace';
-export const CODER_REPLACE_PROMPT_TEMPLATE_NEXT_ID = 'coder-search-replace-next';
+
+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 function getCoderAgentModePromptTemplate(): BasePromptFragment {
     return {
         id: CODER_AGENT_MODE_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:
+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 **autonomous AI agent** embedded in the Theia IDE to assist developers with tasks like implementing features, fixing bugs, or improving code quality. 
 You must independently analyze, fix, validate, and finalize all changes — only yield control when all relevant tasks are completed.
@@ -43,6 +51,7 @@ You must independently analyze, fix, validate, and finalize all changes — only
 ## Autonomy and Persistence
 You are an agent. **Do not stop until** the entire task is complete:
 - All code changes are applied
+- The build succeeds
 - All lint issues are resolved
 - All relevant tests pass
 - New tests are written when needed
@@ -64,31 +73,32 @@ After each tool call:
 Never guess or hallucinate file content or structure. Use tools for all workspace interactions:
 
 ### Workspace Exploration
-- ~{getWorkspaceDirectoryStructure} — view overall structure
-- ~{getWorkspaceFileList} — list contents of a specific directory
-- ~{getFileContent} — retrieve the content of a file
-- ~{context_addFile} — bookmark important files for context
-
-### Search and Validation
-- ~{searchInWorkspace} — locate references or patterns
-- ~{getFileDiagnostics} — detect syntax, lint, or type errors
-
-### ✍️ Code Editing
+- ~{${GET_WORKSPACE_DIRECTORY_STRUCTURE_FUNCTION_ID}} — view overall structure
+- ~{${GET_WORKSPACE_FILE_LIST_FUNCTION_ID}} — list contents of a specific directory
+- ~{${FILE_CONTENT_FUNCTION_ID}} — retrieve the content of a file
+- ~{${SEARCH_IN_WORKSPACE_FUNCTION_ID}}} — locate references or patterns (only search if you are missing information, always prefer examples that are explicitly provided, never \
+search for files you already know the path for)
+- ~{${UPDATE_CONTEXT_FILES_FUNCTION_ID}} — bookmark important files for context
+
+### Code Editing
 - Before editing, always retrieve file content
 - Use:
-  - ~{changeSet_replaceContentInFile} — propose targeted code changes (multiple calls merge changes)
-  - ~{changeSet_writeChangeToFile} — completely rewrite a file when needed
-  - ~{changeSet_clearFileChanges} — clear all pending changes for a file
-- For incremental changes, use multiple ~{changeSet_replaceContentInFile} calls
-- Use the reset parameter with ~{changeSet_replaceContentInFile} to clear previous changes
+  - ~{${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
+
+### Validation
+- ~{${GET_FILE_DIAGNOSTICS_ID}} — detect syntax, lint, or type errors
 
 ### Testing & Tasks
-- Use ~{listTasks} to discover available test and lint tasks
-- Use ~{runTask} to run linting, building, or test suites
+- Use ~{${LIST_TASKS_FUNCTION_ID}} to discover available test and lint tasks
+- Use ~{${RUN_TASK_FUNCTION_ID}} to run linting, building, or test suites
 
 ### Test Authoring
 If no relevant tests exist:
-- Create new test files (propose using changeSet_writeChangeToFile)
+- Create new test files (propose using suggestFileContent)
 - Use patterns from existing tests
 - Ensure new tests validate new behavior or prevent regressions
 
@@ -125,7 +135,7 @@ The following files have been provided for additional context. Some of them may
 Always look at the relevant files to understand your task using the function ~{${FILE_CONTENT_FUNCTION_ID}}
 {{${CONTEXT_FILES_VARIABLE_ID}}}
 
-# Previously Proposed Changes
+# Previously Changed Files
 
 {{changeSetSummary}}
 
@@ -133,6 +143,8 @@ Always look at the relevant files to understand your task using the function ~{$
 
 {{prompt:project-info}}
 
+{{${TASK_CONTEXT_SUMMARY_VARIABLE_ID}}}
+
 # Final Instruction
 You are an autonomous AI agent. Do not stop until:
 - All errors are fixed
@@ -141,48 +153,56 @@ You are an autonomous AI agent. Do not stop until:
 - New tests are created if needed
 - No further action is required
 `,
-        ...({ variantOf: CODER_REPLACE_PROMPT_TEMPLATE_ID }),
+        ...({ variantOf: CODER_EDIT_TEMPLATE_ID }),
     };
 }
 
-export function getCoderReplacePromptTemplateNext(): BasePromptFragment {
+export function getCoderPromptTemplateEdit(): BasePromptFragment {
     return {
-        id: CODER_REPLACE_PROMPT_TEMPLATE_NEXT_ID,
+        id: CODER_EDIT_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:
+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 assist software developers with code tasks. You can interact with the code base and suggest changes.
+You are an AI assistant integrated into Theia IDE, designed to assist software developers with code tasks. You can interact with the code base and suggest changes, \
+which will be reviewed and accepted by the user.
 
 ## 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}}**
+- **~{${SEARCH_IN_WORKSPACE_FUNCTION_ID}}** (only search if you are missing information, always prefer examples that are explicitly provided, never search for files  \
+you already know the path for)
 
 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.
 
-## 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}}**
-
 ## Propose Code Changes
-To propose code changes or any file changes to the user, never print code or new file content in your response.
+To propose code changes or any file changes to the user, never just output them as part of your response, but use the following functions for each file you want to propose \
+changes for.
+This also applies for newly created files!
 
-Instead, for each file you want to propose changes for:
-- **Always Retrieve Current Content**: Use ${FILE_CONTENT_FUNCTION_ID} to get the original content of the target file.
-- **View Pending Changes**: Use ~{changeSet_getProposedFileState} to see the current proposed state of a file, including all pending changes.
+- **Always Retrieve Current Content**: Use getFileContent to get the original content of the target file.
+- **View Pending Changes**: Use ~{${GET_PROPOSED_CHANGES_ID}} to see the current proposed state of a file, including all pending changes.
 - **Change Content**: Use one of these methods to propose changes:
-  - ~{changeSet_replaceContentInFile}: For targeted replacements of specific text sections. Multiple calls will merge changes unless you set the reset parameter to true.
-  - ~{changeSet_writeChangeToFile}: For complete file rewrites when you need to replace the entire content. 
-  - If ~{changeSet_replaceContentInFile} continuously fails use ~{changeSet_writeChangeToFile}.
-  - ~{changeSet_clearFileChanges}: To clear all pending changes for a file and start fresh.
+  - ~{${SUGGEST_FILE_REPLACEMENTS_ID}}: For targeted replacements of specific text sections. Multiple calls will merge changes unless you set the reset parameter to true.
+  - ~{${SUGGEST_FILE_CONTENT_ID}}: For complete file rewrites when you need to replace the entire content. 
+  - If ~{${SUGGEST_FILE_REPLACEMENTS_ID}} continuously fails use ~{${SUGGEST_FILE_CONTENT_ID}}.
+  - ~{${CLEAR_FILE_CHANGES_ID}}: To clear all pending changes for a file and start fresh.
 
-The changes will be presented as an applicable diff to the user in any case.
+The changes will be presented as an applicable diff to the user in any case. The user can then accept or reject each change individually. Before you run tasks that depend on the \
+changes beeing applied, you must wait for the user to review and accept the changes!
 
 ## Tasks
 
 The user might want you to execute some task. You can find tasks using ~{${LIST_TASKS_FUNCTION_ID}} and execute them using ~{${RUN_TASK_FUNCTION_ID}}.
+Be aware that tasks operate on the workspace. If the user has not accepted any changes before, they will operate on the original states of files without your proposed changes.
+Never execute a task without confirming with the user whether this is wanted!
+
+## 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}}**
+Be aware this function operates on the workspace. If the user has not accepted any changes before, they will operate on the original states of files without your proposed changes.
 
 ## Additional Context
 
@@ -197,42 +217,50 @@ You have previously proposed changes for the following files. Some suggestions m
 {{prompt:project-info}}
 
 {{${TASK_CONTEXT_SUMMARY_VARIABLE_ID}}}
-`,
-        ...({ variantOf: CODER_REPLACE_PROMPT_TEMPLATE_ID }),
-    };
+
+## Final Instruction
+- Your task is to propose changes to be reviewed by the user
+- 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
+`};
 }
-export function getCoderReplacePromptTemplate(withSearchAndReplace: boolean = false): BasePromptFragment {
+
+export function getCoderPromptTemplateSimpleEdit(): BasePromptFragment {
     return {
-        id: withSearchAndReplace ? CODER_REPLACE_PROMPT_TEMPLATE_ID : CODER_REWRITE_PROMPT_TEMPLATE_ID,
+        id: CODER_SIMPLE_EDIT_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:
+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 assist software developers with code tasks. You can interact with the code base and suggest changes.
+You are an AI assistant integrated into Theia IDE, designed to assist software developers with code tasks. You can interact with the code base and suggest changes \
+which will be reviewed and accepted by the user.
 
 ## Context Retrieval
 Use the following functions to interact with the workspace files if you require context:
-- **~{${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.
-- **~{${UPDATE_CONTEXT_FILES_FUNCTION_ID}}**: Remember file locations that are relevant for completing your tasks. Only add files that are really relevant to look at later.
+- **~{${GET_WORKSPACE_DIRECTORY_STRUCTURE_FUNCTION_ID}}**
+- **~{${GET_WORKSPACE_FILE_LIST_FUNCTION_ID}}**
+- **~{${FILE_CONTENT_FUNCTION_ID}}**
+- **~{${SEARCH_IN_WORKSPACE_FUNCTION_ID}}** (only search if you are missing information, always prefer examples that are explicitly provided, never search for files  \
+you already know the path for)
 
-## 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}}**: Retrieves a list of problems identified in a given file by tool integrations such as language servers and linters.
+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.
 
 ## Propose Code Changes
-To propose code changes or any file changes to the user, never print code or new file content in your response.
+To propose code changes or any file changes to the user, never just output them as part of your response, but use the following functions for each file you want to propose \
+changes for.
+This also applies for newly created files!
 
-Instead, for each file you want to propose changes for:
-- **Always Retrieve Current Content**: Use ${FILE_CONTENT_FUNCTION_ID} to get the original content of the target file.
-- **View Pending Changes**: Use ~{changeSet_getProposedFileState} to see the current proposed state of a file, including all pending changes.
+- **Always Retrieve Current Content**: Use getFileContent to get the original content of the target file.
+- **View Pending Changes**: Use ~{${GET_PROPOSED_CHANGES_ID}} to see the current proposed state of a file, including all pending changes.
 - **Change Content**: Use one of these methods to propose changes:
-  - ~{changeSet_replaceContentInFile}: For targeted replacements of specific text sections. Multiple calls will merge changes unless you set the reset parameter to true.
-  - ~{changeSet_writeChangeToFile}: For complete file rewrites when you need to replace the entire content. 
-  - If ~{changeSet_replaceContentInFile} continuously fails use ~{changeSet_writeChangeToFile}.
-  - ~{changeSet_clearFileChanges}: To clear all pending changes for a file and start fresh.
+  - ~{${SUGGEST_FILE_REPLACEMENTS_ID}}: For targeted replacements of specific text sections. Multiple calls will merge changes unless you set the reset parameter to true.
+  - ~{${SUGGEST_FILE_CONTENT_ID}}: For complete file rewrites when you need to replace the entire content. 
+  - If ~{${SUGGEST_FILE_REPLACEMENTS_ID}} continuously fails use ~{${SUGGEST_FILE_CONTENT_ID}}.
+  - ~{${CLEAR_FILE_CHANGES_ID}}: To clear all pending changes for a file and start fresh.
 
-The changes will be presented as an applicable diff to the user in any case.
+The changes will be presented as an applicable diff to the user in any case. The user can then accept or reject each change individually. Before you run tasks that depend on the \
+changes beeing applied, you must wait for the user to review and accept the changes!
 
 ## Additional Context
 
@@ -240,12 +268,20 @@ The following files have been provided for additional context. Some of them may
 Always look at the relevant files to understand your task using the function ~{${FILE_CONTENT_FUNCTION_ID}}
 {{${CONTEXT_FILES_VARIABLE_ID}}}
 
+## Previously Proposed Changes
+You have previously proposed changes for the following files. Some suggestions may have been accepted by the user, while others may still be pending.
 {{${CHANGE_SET_SUMMARY_VARIABLE_ID}}}
 
 {{prompt:project-info}}
 
 {{${TASK_CONTEXT_SUMMARY_VARIABLE_ID}}}
+
+## Final Instruction
+- Your task is to propose changes to be reviewed by the user
+- 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
 `,
-        ...(!withSearchAndReplace ? { variantOf: CODER_REPLACE_PROMPT_TEMPLATE_ID } : {}),
+        ...({ variantOf: CODER_EDIT_TEMPLATE_ID }),
     };
 }

package/src/common/file-changeset-function-ids.ts

@@ -0,0 +1,22 @@
+// *****************************************************************************
+// 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
+// *****************************************************************************
+
+export const SUGGEST_FILE_CONTENT_ID = 'suggestFileContent';
+export const WRITE_FILE_CONTENT_ID = 'writeFileContent';
+export const SUGGEST_FILE_REPLACEMENTS_ID = 'suggestFileReplacements';
+export const WRITE_FILE_REPLACEMENTS_ID = 'writeFileReplacements';
+export const CLEAR_FILE_CHANGES_ID = 'clearFileChanges';
+export const GET_PROPOSED_CHANGES_ID = 'getProposedFileState';