repoburg 1.1.10 → 1.2.0

package/backend/dist/src/mcp/mcp.service.js

@@ -0,0 +1,263 @@
+"use strict";
+var __decorate = (this && this.__decorate) || function (decorators, target, key, desc) {
+    var c = arguments.length, r = c < 3 ? target : desc === null ? desc = Object.getOwnPropertyDescriptor(target, key) : desc, d;
+    if (typeof Reflect === "object" && typeof Reflect.decorate === "function") r = Reflect.decorate(decorators, target, key, desc);
+    else for (var i = decorators.length - 1; i >= 0; i--) if (d = decorators[i]) r = (c < 3 ? d(r) : c > 3 ? d(target, key, r) : d(target, key)) || r;
+    return c > 3 && r && Object.defineProperty(target, key, r), r;
+};
+var __metadata = (this && this.__metadata) || function (k, v) {
+    if (typeof Reflect === "object" && typeof Reflect.metadata === "function") return Reflect.metadata(k, v);
+};
+var __param = (this && this.__param) || function (paramIndex, decorator) {
+    return function (target, key) { decorator(target, key, paramIndex); }
+};
+var McpService_1;
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.McpService = void 0;
+const common_1 = require("@nestjs/common");
+const typeorm_1 = require("@nestjs/typeorm");
+const typeorm_2 = require("typeorm");
+const core_entities_1 = require("../core-entities");
+const index_js_1 = require("@modelcontextprotocol/sdk/client/index.js");
+const stdio_js_1 = require("@modelcontextprotocol/sdk/client/stdio.js");
+let McpService = McpService_1 = class McpService {
+    constructor(mcpConfigRepository, mcpToolRepository) {
+        this.mcpConfigRepository = mcpConfigRepository;
+        this.mcpToolRepository = mcpToolRepository;
+        this.logger = new common_1.Logger(McpService_1.name);
+        this.activeClients = new Map();
+    }
+    async onModuleInit() {
+        this.logger.log('Initializing MCP connections...');
+        const configs = await this.mcpConfigRepository.find({
+            where: { is_active: true },
+        });
+        if (configs.length === 0) {
+            this.logger.warn('No active MCP configurations found. MCP tools will be unavailable.');
+            return;
+        }
+        for (const config of configs) {
+            await this.connectToServer(config);
+        }
+    }
+    async onModuleDestroy() {
+        this.logger.log('Closing all active MCP connections...');
+        await Promise.all(Array.from(this.activeClients.keys()).map((serverName) => this.disconnectFromServer(serverName)));
+    }
+    async connectToServer(config) {
+        const { server_name, command, args, env } = config;
+        if (this.activeClients.has(server_name)) {
+            this.logger.log(`Already connected to ${server_name}. Skipping.`);
+            return;
+        }
+        this.logger.log(`Attempting to connect to MCP server: ${server_name}`);
+        try {
+            const transport = new stdio_js_1.StdioClientTransport({ command, args, env });
+            const client = new index_js_1.Client({
+                name: `repoburg-backend-${server_name}`,
+                version: '1.0.0',
+            });
+            client.connect(transport);
+            const toolsResult = await client.listTools();
+            if (!toolsResult || !toolsResult.tools) {
+                throw new Error('Invalid or empty tool list received from server.');
+            }
+            this.logger.log(`Connected to ${server_name}. Discovered ${toolsResult.tools.length} tools.`);
+            this.activeClients.set(server_name, client);
+            await this.syncToolsToDb(server_name, toolsResult.tools);
+        }
+        catch (e) {
+            this.logger.error(`Failed to connect to MCP server "${server_name}": ${e.message}`);
+        }
+    }
+    async disconnectFromServer(serverName) {
+        const client = this.activeClients.get(serverName);
+        if (client) {
+            try {
+                await client.close();
+                this.activeClients.delete(serverName);
+                this.logger.log(`Disconnected from ${serverName}`);
+            }
+            catch (e) {
+                this.logger.error(`Error disconnecting from ${serverName}: ${e.message}`);
+            }
+        }
+    }
+    async syncToolsToDb(serverName, tools) {
+        this.logger.log(`Syncing tools for server: ${serverName}`);
+        const validTools = tools.filter((tool) => !!tool.name);
+        const existingTools = await this.mcpToolRepository.find({
+            where: { server_name: serverName },
+        });
+        const existingToolsMap = new Map(existingTools.map((t) => [t.tool_name, t]));
+        const toolsToSave = [];
+        for (const sdkTool of validTools) {
+            const existingTool = existingToolsMap.get(sdkTool.name);
+            if (existingTool) {
+                existingTool.description = sdkTool.description || '';
+                existingTool.input_schema = sdkTool.inputSchema || {};
+                toolsToSave.push(existingTool);
+            }
+            else {
+                toolsToSave.push(this.mcpToolRepository.create({
+                    server_name: serverName,
+                    tool_name: sdkTool.name,
+                    description: sdkTool.description || '',
+                    input_schema: sdkTool.inputSchema || {},
+                }));
+            }
+        }
+        await this.mcpToolRepository.save(toolsToSave);
+        const newToolNames = validTools.map((t) => t.name);
+        const toolsToDelete = existingTools.filter((t) => !newToolNames.includes(t.tool_name));
+        if (toolsToDelete.length > 0) {
+            await this.mcpToolRepository.remove(toolsToDelete);
+        }
+        this.logger.log(`Successfully synced tools for ${serverName}. Saved: ${toolsToSave.length}, Deleted: ${toolsToDelete.length}`);
+    }
+    async createMcpConfig(configJson) {
+        let parsedConfig;
+        try {
+            parsedConfig = JSON.parse(configJson);
+        }
+        catch (e) {
+            throw new common_1.BadRequestException('Invalid JSON format.');
+        }
+        const serverName = Object.keys(parsedConfig)[0];
+        if (!serverName) {
+            throw new common_1.BadRequestException('JSON must have a root key as the server name.');
+        }
+        const configData = parsedConfig[serverName];
+        if (!configData || !configData.command || !configData.args) {
+            throw new common_1.BadRequestException('Configuration must include "command" and "args" properties.');
+        }
+        const existingConfig = await this.mcpConfigRepository.findOneBy({
+            server_name: serverName,
+        });
+        if (existingConfig) {
+            throw new common_1.BadRequestException(`A configuration for "${serverName}" already exists.`);
+        }
+        const newConfig = this.mcpConfigRepository.create({
+            server_name: serverName,
+            command: configData.command,
+            args: configData.args,
+            env: configData.env || {},
+            is_active: true,
+        });
+        const savedConfig = await this.mcpConfigRepository.save(newConfig);
+        await this.connectToServer(savedConfig);
+        return savedConfig;
+    }
+    async updateMcpConfigStatus(serverName, isActive) {
+        const config = await this.mcpConfigRepository.findOneBy({
+            server_name: serverName,
+        });
+        if (!config) {
+            throw new common_1.NotFoundException(`MCP configuration for "${serverName}" not found.`);
+        }
+        config.is_active = isActive;
+        await this.mcpConfigRepository.save(config);
+        if (isActive) {
+            await this.connectToServer(config);
+        }
+        else {
+            await this.disconnectFromServer(serverName);
+        }
+        return config;
+    }
+    async deleteMcpConfig(serverName) {
+        const config = await this.mcpConfigRepository.findOneBy({
+            server_name: serverName,
+        });
+        if (!config) {
+            throw new common_1.NotFoundException(`MCP configuration for "${serverName}" not found.`);
+        }
+        await this.disconnectFromServer(serverName);
+        await this.mcpToolRepository.delete({ server_name: serverName });
+        await this.mcpConfigRepository.remove(config);
+    }
+    async batchUpdateToolStatus(toolIds, isActive) {
+        if (toolIds.length === 0) {
+            return { affected: 0 };
+        }
+        const result = await this.mcpToolRepository.update({ id: (0, typeorm_2.In)(toolIds) }, { is_active: isActive });
+        return { affected: result.affected || 0 };
+    }
+    async getMcpServers() {
+        const configs = await this.mcpConfigRepository.find({
+            order: { server_name: 'ASC' },
+        });
+        const tools = await this.mcpToolRepository.find({
+            order: { tool_name: 'ASC' },
+        });
+        const toolsByServer = new Map();
+        for (const tool of tools) {
+            if (!toolsByServer.has(tool.server_name)) {
+                toolsByServer.set(tool.server_name, []);
+            }
+            toolsByServer.get(tool.server_name).push({
+                id: tool.id,
+                tool_name: tool.tool_name,
+                description: tool.description,
+                input_schema: tool.input_schema,
+                is_active: tool.is_active,
+            });
+        }
+        return configs.map((config) => ({
+            server_name: config.server_name,
+            description: `Tools available from the ${config.server_name} server.`,
+            is_active: config.is_active,
+            tools: toolsByServer.get(config.server_name) || [],
+        }));
+    }
+    async executeMcpTool(serverName, toolName, args) {
+        this.logger.log(`Executing MCP tool: ${serverName}.${toolName} with args: ${JSON.stringify(args)}`);
+        const client = this.activeClients.get(serverName);
+        if (!client) {
+            const errorMsg = `No active MCP connection found for server: ${serverName}`;
+            this.logger.error(errorMsg);
+            return { stdout: '', stderr: errorMsg };
+        }
+        try {
+            const result = await client.callTool({ name: toolName, arguments: args });
+            const stdout = JSON.stringify(result, null, 2);
+            return { stdout, stderr: '' };
+        }
+        catch (e) {
+            this.logger.error(`Error calling tool ${toolName} on ${serverName}: ${e.message}`);
+            return { stdout: '', stderr: e.message };
+        }
+    }
+    async getMcpToolsDefinition() {
+        const servers = await this.getMcpServers();
+        const activeServers = servers.filter((s) => s.is_active);
+        if (activeServers.length === 0) {
+            return 'No active MCP servers are currently connected.';
+        }
+        let definition = '';
+        for (const server of activeServers) {
+            const activeTools = server.tools.filter((t) => t.is_active);
+            if (activeTools.length === 0)
+                continue;
+            definition += `### Server: ${server.server_name}\n`;
+            definition += `Description: ${server.description}\n`;
+            definition += 'Tools:\n';
+            for (const tool of activeTools) {
+                definition += `- **${tool.tool_name}**\n`;
+                definition += `  - Description: ${tool.description}\n`;
+                definition += `  - Input Schema: \`${JSON.stringify(tool.input_schema)}\`\n`;
+            }
+            definition += '\n';
+        }
+        return definition;
+    }
+};
+exports.McpService = McpService;
+exports.McpService = McpService = McpService_1 = __decorate([
+    (0, common_1.Injectable)(),
+    __param(0, (0, typeorm_1.InjectRepository)(core_entities_1.McpConfig)),
+    __param(1, (0, typeorm_1.InjectRepository)(core_entities_1.McpTool)),
+    __metadata("design:paramtypes", [typeorm_2.Repository,
+        typeorm_2.Repository])
+], McpService);
+//# sourceMappingURL=mcp.service.js.map

package/backend/dist/src/mcp/mcp.service.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"mcp.service.js","sourceRoot":"","sources":["../../../src/mcp/mcp.service.ts"],"names":[],"mappings":";;;;;;;;;;;;;;;;AAAA,2CAOwB;AACxB,6CAAmD;AACnD,qCAAyC;AACzC,oDAAsD;AACtD,wEAAmE;AACnE,wEAAiF;AAW1E,IAAM,UAAU,kBAAhB,MAAM,UAAU;IAIrB,YAEE,mBAA2D,EAE3D,iBAAuD;QAFtC,wBAAmB,GAAnB,mBAAmB,CAAuB;QAE1C,sBAAiB,GAAjB,iBAAiB,CAAqB;QAPxC,WAAM,GAAG,IAAI,eAAM,CAAC,YAAU,CAAC,IAAI,CAAC,CAAC;QACrC,kBAAa,GAAG,IAAI,GAAG,EAAkB,CAAC;IAOxD,CAAC;IAEJ,KAAK,CAAC,YAAY;QAChB,IAAI,CAAC,MAAM,CAAC,GAAG,CAAC,iCAAiC,CAAC,CAAC;QACnD,MAAM,OAAO,GAAG,MAAM,IAAI,CAAC,mBAAmB,CAAC,IAAI,CAAC;YAClD,KAAK,EAAE,EAAE,SAAS,EAAE,IAAI,EAAE;SAC3B,CAAC,CAAC;QACH,IAAI,OAAO,CAAC,MAAM,KAAK,CAAC,EAAE,CAAC;YACzB,IAAI,CAAC,MAAM,CAAC,IAAI,CACd,oEAAoE,CACrE,CAAC;YACF,OAAO;QACT,CAAC;QAED,KAAK,MAAM,MAAM,IAAI,OAAO,EAAE,CAAC;YAC7B,MAAM,IAAI,CAAC,eAAe,CAAC,MAAM,CAAC,CAAC;QACrC,CAAC;IACH,CAAC;IAED,KAAK,CAAC,eAAe;QACnB,IAAI,CAAC,MAAM,CAAC,GAAG,CAAC,uCAAuC,CAAC,CAAC;QACzD,MAAM,OAAO,CAAC,GAAG,CACf,KAAK,CAAC,IAAI,CAAC,IAAI,CAAC,aAAa,CAAC,IAAI,EAAE,CAAC,CAAC,GAAG,CAAC,CAAC,UAAU,EAAE,EAAE,CACvD,IAAI,CAAC,oBAAoB,CAAC,UAAU,CAAC,CACtC,CACF,CAAC;IACJ,CAAC;IAEM,KAAK,CAAC,eAAe,CAAC,MAAiB;QAC5C,MAAM,EAAE,WAAW,EAAE,OAAO,EAAE,IAAI,EAAE,GAAG,EAAE,GAAG,MAAM,CAAC;QACnD,IAAI,IAAI,CAAC,aAAa,CAAC,GAAG,CAAC,WAAW,CAAC,EAAE,CAAC;YACxC,IAAI,CAAC,MAAM,CAAC,GAAG,CAAC,wBAAwB,WAAW,aAAa,CAAC,CAAC;YAClE,OAAO;QACT,CAAC;QACD,IAAI,CAAC,MAAM,CAAC,GAAG,CAAC,wCAAwC,WAAW,EAAE,CAAC,CAAC;QACvE,IAAI,CAAC;YACH,MAAM,SAAS,GAAG,IAAI,+BAAoB,CAAC,EAAE,OAAO,EAAE,IAAI,EAAE,GAAG,EAAE,CAAC,CAAC;YACnE,MAAM,MAAM,GAAG,IAAI,iBAAM,CAAC;gBACxB,IAAI,EAAE,oBAAoB,WAAW,EAAE;gBACvC,OAAO,EAAE,OAAO;aACjB,CAAC,CAAC;YAEH,MAAM,CAAC,OAAO,CAAC,SAAS,CAAC,CAAC;YAE1B,MAAM,WAAW,GAAG,MAAM,MAAM,CAAC,SAAS,EAAE,CAAC;YAC7C,IAAI,CAAC,WAAW,IAAI,CAAC,WAAW,CAAC,KAAK,EAAE,CAAC;gBACvC,MAAM,IAAI,KAAK,CAAC,kDAAkD,CAAC,CAAC;YACtE,CAAC;YAED,IAAI,CAAC,MAAM,CAAC,GAAG,CACb,gBAAgB,WAAW,gBAAgB,WAAW,CAAC,KAAK,CAAC,MAAM,SAAS,CAC7E,CAAC;YACF,IAAI,CAAC,aAAa,CAAC,GAAG,CAAC,WAAW,EAAE,MAAM,CAAC,CAAC;YAE5C,MAAM,IAAI,CAAC,aAAa,CAAC,WAAW,EAAE,WAAW,CAAC,KAAqB,CAAC,CAAC;QAC3E,CAAC;QAAC,OAAO,CAAC,EAAE,CAAC;YACX,IAAI,CAAC,MAAM,CAAC,KAAK,CACf,oCAAoC,WAAW,MAAM,CAAC,CAAC,OAAO,EAAE,CACjE,CAAC;QACJ,CAAC;IACH,CAAC;IAEM,KAAK,CAAC,oBAAoB,CAAC,UAAkB;QAClD,MAAM,MAAM,GAAG,IAAI,CAAC,aAAa,CAAC,GAAG,CAAC,UAAU,CAAC,CAAC;QAClD,IAAI,MAAM,EAAE,CAAC;YACX,IAAI,CAAC;gBACH,MAAM,MAAM,CAAC,KAAK,EAAE,CAAC;gBACrB,IAAI,CAAC,aAAa,CAAC,MAAM,CAAC,UAAU,CAAC,CAAC;gBACtC,IAAI,CAAC,MAAM,CAAC,GAAG,CAAC,qBAAqB,UAAU,EAAE,CAAC,CAAC;YACrD,CAAC;YAAC,OAAO,CAAC,EAAE,CAAC;gBACX,IAAI,CAAC,MAAM,CAAC,KAAK,CACf,4BAA4B,UAAU,KAAK,CAAC,CAAC,OAAO,EAAE,CACvD,CAAC;YACJ,CAAC;QACH,CAAC;IACH,CAAC;IAEO,KAAK,CAAC,aAAa,CAAC,UAAkB,EAAE,KAAmB;QACjE,IAAI,CAAC,MAAM,CAAC,GAAG,CAAC,6BAA6B,UAAU,EAAE,CAAC,CAAC;QAE3D,MAAM,UAAU,GAAG,KAAK,CAAC,MAAM,CAC7B,CAAC,IAAI,EAA2D,EAAE,CAChE,CAAC,CAAC,IAAI,CAAC,IAAI,CACd,CAAC;QAEF,MAAM,aAAa,GAAG,MAAM,IAAI,CAAC,iBAAiB,CAAC,IAAI,CAAC;YACtD,KAAK,EAAE,EAAE,WAAW,EAAE,UAAU,EAAE;SACnC,CAAC,CAAC;QACH,MAAM,gBAAgB,GAAG,IAAI,GAAG,CAC9B,aAAa,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,CAAC,SAAS,EAAE,CAAC,CAAC,CAAC,CAC3C,CAAC;QAEF,MAAM,WAAW,GAAc,EAAE,CAAC;QAClC,KAAK,MAAM,OAAO,IAAI,UAAU,EAAE,CAAC;YACjC,MAAM,YAAY,GAAG,gBAAgB,CAAC,GAAG,CAAC,OAAO,CAAC,IAAI,CAAC,CAAC;YACxD,IAAI,YAAY,EAAE,CAAC;gBAEjB,YAAY,CAAC,WAAW,GAAG,OAAO,CAAC,WAAW,IAAI,EAAE,CAAC;gBACrD,YAAY,CAAC,YAAY,GAAG,OAAO,CAAC,WAAW,IAAI,EAAE,CAAC;gBACtD,WAAW,CAAC,IAAI,CAAC,YAAY,CAAC,CAAC;YACjC,CAAC;iBAAM,CAAC;gBAEN,WAAW,CAAC,IAAI,CACd,IAAI,CAAC,iBAAiB,CAAC,MAAM,CAAC;oBAC5B,WAAW,EAAE,UAAU;oBACvB,SAAS,EAAE,OAAO,CAAC,IAAI;oBACvB,WAAW,EAAE,OAAO,CAAC,WAAW,IAAI,EAAE;oBACtC,YAAY,EAAE,OAAO,CAAC,WAAW,IAAI,EAAE;iBACxC,CAAC,CACH,CAAC;YACJ,CAAC;QACH,CAAC;QAED,MAAM,IAAI,CAAC,iBAAiB,CAAC,IAAI,CAAC,WAAW,CAAC,CAAC;QAE/C,MAAM,YAAY,GAAG,UAAU,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,IAAI,CAAC,CAAC;QACnD,MAAM,aAAa,GAAG,aAAa,CAAC,MAAM,CACxC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,YAAY,CAAC,QAAQ,CAAC,CAAC,CAAC,SAAS,CAAC,CAC3C,CAAC;QACF,IAAI,aAAa,CAAC,MAAM,GAAG,CAAC,EAAE,CAAC;YAC7B,MAAM,IAAI,CAAC,iBAAiB,CAAC,MAAM,CAAC,aAAa,CAAC,CAAC;QACrD,CAAC;QAED,IAAI,CAAC,MAAM,CAAC,GAAG,CACb,iCAAiC,UAAU,YAAY,WAAW,CAAC,MAAM,cAAc,aAAa,CAAC,MAAM,EAAE,CAC9G,CAAC;IACJ,CAAC;IAEM,KAAK,CAAC,eAAe,CAAC,UAAkB;QAC7C,IAAI,YAAiB,CAAC;QACtB,IAAI,CAAC;YACH,YAAY,GAAG,IAAI,CAAC,KAAK,CAAC,UAAU,CAAC,CAAC;QACxC,CAAC;QAAC,OAAO,CAAC,EAAE,CAAC;YACX,MAAM,IAAI,4BAAmB,CAAC,sBAAsB,CAAC,CAAC;QACxD,CAAC;QAED,MAAM,UAAU,GAAG,MAAM,CAAC,IAAI,CAAC,YAAY,CAAC,CAAC,CAAC,CAAC,CAAC;QAChD,IAAI,CAAC,UAAU,EAAE,CAAC;YAChB,MAAM,IAAI,4BAAmB,CAC3B,+CAA+C,CAChD,CAAC;QACJ,CAAC;QAED,MAAM,UAAU,GAAG,YAAY,CAAC,UAAU,CAAC,CAAC;QAC5C,IAAI,CAAC,UAAU,IAAI,CAAC,UAAU,CAAC,OAAO,IAAI,CAAC,UAAU,CAAC,IAAI,EAAE,CAAC;YAC3D,MAAM,IAAI,4BAAmB,CAC3B,6DAA6D,CAC9D,CAAC;QACJ,CAAC;QAED,MAAM,cAAc,GAAG,MAAM,IAAI,CAAC,mBAAmB,CAAC,SAAS,CAAC;YAC9D,WAAW,EAAE,UAAU;SACxB,CAAC,CAAC;QACH,IAAI,cAAc,EAAE,CAAC;YACnB,MAAM,IAAI,4BAAmB,CAC3B,wBAAwB,UAAU,mBAAmB,CACtD,CAAC;QACJ,CAAC;QAED,MAAM,SAAS,GAAG,IAAI,CAAC,mBAAmB,CAAC,MAAM,CAAC;YAChD,WAAW,EAAE,UAAU;YACvB,OAAO,EAAE,UAAU,CAAC,OAAO;YAC3B,IAAI,EAAE,UAAU,CAAC,IAAI;YACrB,GAAG,EAAE,UAAU,CAAC,GAAG,IAAI,EAAE;YACzB,SAAS,EAAE,IAAI;SAChB,CAAC,CAAC;QAEH,MAAM,WAAW,GAAG,MAAM,IAAI,CAAC,mBAAmB,CAAC,IAAI,CAAC,SAAS,CAAC,CAAC;QACnE,MAAM,IAAI,CAAC,eAAe,CAAC,WAAW,CAAC,CAAC;QACxC,OAAO,WAAW,CAAC;IACrB,CAAC;IAEM,KAAK,CAAC,qBAAqB,CAChC,UAAkB,EAClB,QAAiB;QAEjB,MAAM,MAAM,GAAG,MAAM,IAAI,CAAC,mBAAmB,CAAC,SAAS,CAAC;YACtD,WAAW,EAAE,UAAU;SACxB,CAAC,CAAC;QACH,IAAI,CAAC,MAAM,EAAE,CAAC;YACZ,MAAM,IAAI,0BAAiB,CACzB,0BAA0B,UAAU,cAAc,CACnD,CAAC;QACJ,CAAC;QAED,MAAM,CAAC,SAAS,GAAG,QAAQ,CAAC;QAC5B,MAAM,IAAI,CAAC,mBAAmB,CAAC,IAAI,CAAC,MAAM,CAAC,CAAC;QAE5C,IAAI,QAAQ,EAAE,CAAC;YACb,MAAM,IAAI,CAAC,eAAe,CAAC,MAAM,CAAC,CAAC;QACrC,CAAC;aAAM,CAAC;YACN,MAAM,IAAI,CAAC,oBAAoB,CAAC,UAAU,CAAC,CAAC;QAE9C,CAAC;QAED,OAAO,MAAM,CAAC;IAChB,CAAC;IAEM,KAAK,CAAC,eAAe,CAAC,UAAkB;QAC7C,MAAM,MAAM,GAAG,MAAM,IAAI,CAAC,mBAAmB,CAAC,SAAS,CAAC;YACtD,WAAW,EAAE,UAAU;SACxB,CAAC,CAAC;QACH,IAAI,CAAC,MAAM,EAAE,CAAC;YACZ,MAAM,IAAI,0BAAiB,CACzB,0BAA0B,UAAU,cAAc,CACnD,CAAC;QACJ,CAAC;QAED,MAAM,IAAI,CAAC,oBAAoB,CAAC,UAAU,CAAC,CAAC;QAC5C,MAAM,IAAI,CAAC,iBAAiB,CAAC,MAAM,CAAC,EAAE,WAAW,EAAE,UAAU,EAAE,CAAC,CAAC;QACjE,MAAM,IAAI,CAAC,mBAAmB,CAAC,MAAM,CAAC,MAAM,CAAC,CAAC;IAChD,CAAC;IAEM,KAAK,CAAC,qBAAqB,CAChC,OAAiB,EACjB,QAAiB;QAEjB,IAAI,OAAO,CAAC,MAAM,KAAK,CAAC,EAAE,CAAC;YACzB,OAAO,EAAE,QAAQ,EAAE,CAAC,EAAE,CAAC;QACzB,CAAC;QACD,MAAM,MAAM,GAAG,MAAM,IAAI,CAAC,iBAAiB,CAAC,MAAM,CAChD,EAAE,EAAE,EAAE,IAAA,YAAE,EAAC,OAAO,CAAC,EAAE,EACnB,EAAE,SAAS,EAAE,QAAQ,EAAE,CACxB,CAAC;QACF,OAAO,EAAE,QAAQ,EAAE,MAAM,CAAC,QAAQ,IAAI,CAAC,EAAE,CAAC;IAC5C,CAAC;IAEM,KAAK,CAAC,aAAa;QACxB,MAAM,OAAO,GAAG,MAAM,IAAI,CAAC,mBAAmB,CAAC,IAAI,CAAC;YAClD,KAAK,EAAE,EAAE,WAAW,EAAE,KAAK,EAAE;SAC9B,CAAC,CAAC;QACH,MAAM,KAAK,GAAG,MAAM,IAAI,CAAC,iBAAiB,CAAC,IAAI,CAAC;YAC9C,KAAK,EAAE,EAAE,SAAS,EAAE,KAAK,EAAE;SAC5B,CAAC,CAAC;QAEH,MAAM,aAAa,GAAG,IAAI,GAAG,EAAiB,CAAC;QAC/C,KAAK,MAAM,IAAI,IAAI,KAAK,EAAE,CAAC;YACzB,IAAI,CAAC,aAAa,CAAC,GAAG,CAAC,IAAI,CAAC,WAAW,CAAC,EAAE,CAAC;gBACzC,aAAa,CAAC,GAAG,CAAC,IAAI,CAAC,WAAW,EAAE,EAAE,CAAC,CAAC;YAC1C,CAAC;YACD,aAAa,CAAC,GAAG,CAAC,IAAI,CAAC,WAAW,CAAC,CAAC,IAAI,CAAC;gBACvC,EAAE,EAAE,IAAI,CAAC,EAAE;gBACX,SAAS,EAAE,IAAI,CAAC,SAAS;gBACzB,WAAW,EAAE,IAAI,CAAC,WAAW;gBAC7B,YAAY,EAAE,IAAI,CAAC,YAAY;gBAC/B,SAAS,EAAE,IAAI,CAAC,SAAS;aAC1B,CAAC,CAAC;QACL,CAAC;QAED,OAAO,OAAO,CAAC,GAAG,CAAC,CAAC,MAAM,EAAE,EAAE,CAAC,CAAC;YAC9B,WAAW,EAAE,MAAM,CAAC,WAAW;YAC/B,WAAW,EAAE,4BAA4B,MAAM,CAAC,WAAW,UAAU;YACrE,SAAS,EAAE,MAAM,CAAC,SAAS;YAC3B,KAAK,EAAE,aAAa,CAAC,GAAG,CAAC,MAAM,CAAC,WAAW,CAAC,IAAI,EAAE;SACnD,CAAC,CAAC,CAAC;IACN,CAAC;IAEM,KAAK,CAAC,cAAc,CACzB,UAAkB,EAClB,QAAgB,EAChB,IAAS;QAET,IAAI,CAAC,MAAM,CAAC,GAAG,CACb,uBAAuB,UAAU,IAAI,QAAQ,eAAe,IAAI,CAAC,SAAS,CACxE,IAAI,CACL,EAAE,CACJ,CAAC;QAEF,MAAM,MAAM,GAAG,IAAI,CAAC,aAAa,CAAC,GAAG,CAAC,UAAU,CAAC,CAAC;QAClD,IAAI,CAAC,MAAM,EAAE,CAAC;YACZ,MAAM,QAAQ,GAAG,8CAA8C,UAAU,EAAE,CAAC;YAC5E,IAAI,CAAC,MAAM,CAAC,KAAK,CAAC,QAAQ,CAAC,CAAC;YAC5B,OAAO,EAAE,MAAM,EAAE,EAAE,EAAE,MAAM,EAAE,QAAQ,EAAE,CAAC;QAC1C,CAAC;QAED,IAAI,CAAC;YACH,MAAM,MAAM,GAAG,MAAM,MAAM,CAAC,QAAQ,CAAC,EAAE,IAAI,EAAE,QAAQ,EAAE,SAAS,EAAE,IAAI,EAAE,CAAC,CAAC;YAC1E,MAAM,MAAM,GAAG,IAAI,CAAC,SAAS,CAAC,MAAM,EAAE,IAAI,EAAE,CAAC,CAAC,CAAC;YAC/C,OAAO,EAAE,MAAM,EAAE,MAAM,EAAE,EAAE,EAAE,CAAC;QAChC,CAAC;QAAC,OAAO,CAAC,EAAE,CAAC;YACX,IAAI,CAAC,MAAM,CAAC,KAAK,CACf,sBAAsB,QAAQ,OAAO,UAAU,KAAK,CAAC,CAAC,OAAO,EAAE,CAChE,CAAC;YACF,OAAO,EAAE,MAAM,EAAE,EAAE,EAAE,MAAM,EAAE,CAAC,CAAC,OAAO,EAAE,CAAC;QAC3C,CAAC;IACH,CAAC;IAEM,KAAK,CAAC,qBAAqB;QAChC,MAAM,OAAO,GAAG,MAAM,IAAI,CAAC,aAAa,EAAE,CAAC;QAC3C,MAAM,aAAa,GAAG,OAAO,CAAC,MAAM,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,SAAS,CAAC,CAAC;QAEzD,IAAI,aAAa,CAAC,MAAM,KAAK,CAAC,EAAE,CAAC;YAC/B,OAAO,gDAAgD,CAAC;QAC1D,CAAC;QAED,IAAI,UAAU,GAAG,EAAE,CAAC;QACpB,KAAK,MAAM,MAAM,IAAI,aAAa,EAAE,CAAC;YACnC,MAAM,WAAW,GAAG,MAAM,CAAC,KAAK,CAAC,MAAM,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,SAAS,CAAC,CAAC;YAC5D,IAAI,WAAW,CAAC,MAAM,KAAK,CAAC;gBAAE,SAAS;YAEvC,UAAU,IAAI,eAAe,MAAM,CAAC,WAAW,IAAI,CAAC;YACpD,UAAU,IAAI,gBAAgB,MAAM,CAAC,WAAW,IAAI,CAAC;YACrD,UAAU,IAAI,UAAU,CAAC;YACzB,KAAK,MAAM,IAAI,IAAI,WAAW,EAAE,CAAC;gBAC/B,UAAU,IAAI,OAAO,IAAI,CAAC,SAAS,MAAM,CAAC;gBAC1C,UAAU,IAAI,oBAAoB,IAAI,CAAC,WAAW,IAAI,CAAC;gBACvD,UAAU,IAAI,uBAAuB,IAAI,CAAC,SAAS,CACjD,IAAI,CAAC,YAAY,CAClB,MAAM,CAAC;YACV,CAAC;YACD,UAAU,IAAI,IAAI,CAAC;QACrB,CAAC;QACD,OAAO,UAAU,CAAC;IACpB,CAAC;CACF,CAAA;AAnUY,gCAAU;qBAAV,UAAU;IADtB,IAAA,mBAAU,GAAE;IAMR,WAAA,IAAA,0BAAgB,EAAC,yBAAS,CAAC,CAAA;IAE3B,WAAA,IAAA,0BAAgB,EAAC,uBAAO,CAAC,CAAA;qCADY,oBAAU;QAEZ,oBAAU;GARrC,UAAU,CAmUtB"}

package/backend/dist/src/seeding/data/context-templates/open-pr-command.d.ts

@@ -1,2 +1,2 @@
 export declare const template_name = "Open PR";
-export declare const template_content = "You are a Pull-Request Assistant. Your job is to:\n\n1. Read the diff and infer the intent and impact of the changes.\n\nHere is the diff:\n\n------------DIFF STARTS HERE------------------\n\n<%~ await it.gitDiff('main') %>\n\n------------DIFF ENDS HERE------------------\n\nThen, based on the inferred intent and impact, generate a Pull Request (PR) description and title that clearly communicates the changes made. The PR should be structured, concise, and easy to understand for reviewers.\n\n2. Produce a PR title:\n   \u2022 \u226450 characters\n   \u2022 Imperative, present tense (\u201CAdd X\u201D, not \u201CAdded X\u201D)\n   \u2022 Prefixed with a Conventional Commit type when relevant (feat:, fix:, refactor:, chore:)\n\n3. Produce a structured PR description with these sections (use Markdown headings):\n   ### Context\n   \u2013 Why the change was needed (max 3 bullets)\n   ### What Changed\n   \u2013 High-level summary of code changes (max 5 bullets)\n   ### Testing\n   \u2013 How to verify (max 5 bullets)\n   ### Impact\n   \u2013 Backward-compatibility concerns or side-effects (max 3 bullets)\n\nGuidelines:\n- Keep bullets concise.\n- Avoid internal jargon; write for someone new to the codebase.\n- If the diff is unclear or you need more info, ask the user a clarifying question before generating.\n\n\nACTION: run the command with proper values below with `run_command` tool call\n\n```\ncat <<'EOF' | gh pr create --base main --title \"feat: some title\" --body-file -\n### Context\n- some context\n\n### What Changed\n- some changes\n\n### Testing\n- some testing\n\n### Impact\n- some impact\nEOF\n```\n";
+export declare const template_content = "You are a Pull-Request Assistant. Your job is to:\n\n1. Read the diff and infer the intent and impact of the changes.\n\nHere is the diff:\n\n------------DIFF STARTS HERE------------------\n\n<%~ await it.gitDiff('main') %>\n\n------------DIFF ENDS HERE------------------\n\nThen, based on the inferred intent and impact, generate a Pull Request (PR) description and title that clearly communicates the changes made. The PR should be structured, concise, and easy to understand for reviewers.\n\n2. Produce a PR title:\n   \u2022 \u226450 characters\n   \u2022 Imperative, present tense (\u201CAdd X\u201D, not \u201CAdded X\u201D)\n   \u2022 Prefixed with a Conventional Commit type when relevant (feat:, fix:, refactor:, chore:)\n\n3. Produce a structured PR description with these sections (use Markdown headings):\n   ### Context\n   \u2013 Why the change was needed (max 3 bullets)\n   ### What Changed\n   \u2013 High-level summary of code changes (max 5 bullets)\n   ### Testing\n   \u2013 How to verify (max 5 bullets)\n   ### Impact\n   \u2013 Backward-compatibility concerns or side-effects (max 3 bullets)\n\nGuidelines:\n- Keep bullets concise.\n- Avoid internal jargon; write for someone new to the codebase.\n- If the diff is unclear or you need more info, ask the user a clarifying question before generating.\n\n\nACTION: run the command with proper values below with `run_command` tool call\n\n```\nsource ~/.zshrc && cat <<'EOF' | gh pr create --base main --title \"feat: some title\" --body-file -\n### Context\n- some context\n\n### What Changed\n- some changes\n\n### Testing\n- some testing\n\n### Impact\n- some impact\nEOF\n```\n";

package/backend/dist/src/seeding/data/context-templates/open-pr-command.js

@@ -40,7 +40,7 @@ Guidelines:
 ACTION: run the command with proper values below with \`run_command\` tool call
 
 \`\`\`
-cat <<'EOF' | gh pr create --base main --title "feat: some title" --body-file -
+source ~/.zshrc && cat <<'EOF' | gh pr create --base main --title "feat: some title" --body-file -
 ### Context
 - some context
 

package/backend/dist/src/seeding/data/mcp-configs/default-configs.d.ts

@@ -0,0 +1 @@
+export declare const defaultMcpConfigs: any[];

package/backend/dist/src/seeding/data/mcp-configs/default-configs.js

@@ -0,0 +1,5 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.defaultMcpConfigs = void 0;
+exports.defaultMcpConfigs = [];
+//# sourceMappingURL=default-configs.js.map

package/backend/dist/src/seeding/data/mcp-configs/default-configs.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"default-configs.js","sourceRoot":"","sources":["../../../../../src/seeding/data/mcp-configs/default-configs.ts"],"names":[],"mappings":";;;AAGa,QAAA,iBAAiB,GAAG,EAAE,CAAC"}

package/backend/dist/src/seeding/data/system-prompts/default_master-agent.d.ts

@@ -1,2 +1,2 @@
 export declare const name = "Master Agent";
-export declare const content = "\n<ai>\n    <definition> you are a software developer AI agent. you're talking to a software developer. your task is implementing new feature, fixing bugs, explaining codebase or just helping to the user</definition>\n\n    <preparation-phase-loop>\n\n        <clear-the-request>\n            user provides a request for code or software development task. and they might provide relevant context (code files, file/folder tree structure, docs or code snippets).\n            first make sure you understand the request. if you don't understand, ask for clarification.\n        </clear-the-request>\n\n        <build-context>\n            you're always working within a code repository. meticulously search codebase to find where to work and find relevant examples or documentations.\n            you have 2 tools:\n            1- `request_context`: with this tool you can ask files and folders. you will get the content of files in response. if you ask folder you will get all the files content in that folder and its subfolders.\n            2- `run_command`: with this tool you can run any command line commands. for example rg, tree, ls, find etc.\n\n            this step is a loop. you should use this step as exploration phase.\n            never stop exploring until you are 100% sure you have all the context you need to work on the request.\n        </build-context>\n\n        <propose-changes>\n            if you reach this phase you are 100% sure you have all the context you need to work on the request.\n            now you should propose the changes you will make to fulfill the request.\n            be concise in your proposal. explain with code snippets if needed.\n\n            use `final` tool to explain your proposal.\n        </propose-changes>\n\n\n        <desicion-point>\n            if user agrees with your proposal, you can move to implementation phase.\n            if user disagrees or wants changes, go back to `clear-the-request` phase.\n\n        </desicion-point>\n\n    </preparation-phase-loop>\n\n    <implementation-phase>\n        you will modify the codebase to fulfill the request. you can create, update or delete files.\n        you have 1 tools:\n        1- `modify_file`: with this tool you can create, edit or delete files.\n\n\n        scope:      only code what you propose and user agrees. do not refactor code or change anything that is not related to the request.\n        file size:  keep files are small as possible. if a file is getting too big, split it into smaller files.\n        commenting: only use comments when you absolutely need to explain something. otherwise write self-explanatory code.\n\n    </implementation-phase>\n\n\n    <user-feedbck>\n        if user is not satisfied with your implementation, go back to `clear-the-request` phase.\n        if user says `yolo` in response, you can continue. if you're done, explain what you did with `final` tool.\n    \n    </user-feedbck>\n\n    <tools>\n\n        you have 3 tools: `modify_file`, `request_context` and `run_command`. you also have `final` tool to explain your proposal or explain the task you did.\n        make sure to use only one tool per action item. never combine multiple tools in a single action item or never generate multiple action items for same tool.\n        make sure to follow the instructions for each tool below.\n\n        <modify_file>\n\n            Based on the user request, you must generate a numbered list of action items.\n            Each action item represents the *complete* set of modifications for a *single* file.\n            Action items are ordered sequentially.\n            Each action item should be enclosed within `\u00A7ACTION_ITEM_START\u00A7` and `\u00A7ACTION_ITEM_END\u00A7` markers and include the following details using the `\u00A6FieldName\u00A6 Value` format:\n\n\n            \u00A7TITLE_START\u00A7 very brief title for entire chat history including previous prompt, if current title is fine then leave it (max 4 words) \u00A7TITLE_END\u00A7\n\n            *   `\u00A6ActionNumber\u00A6`: The sequential identifier for the task.\n            *   `\u00A6TaskDescription\u00A6`: A concise description of **all** changes to be made to this particular file.\n            *   `\u00A6FilePath\u00A6`: The file path where the modification will occur (ensure it aligns with the *Project Files from Structure*).\n            *   `\u00A6FileAction\u00A6`: The operation to perform: `create_file`, `edit_file`, `delete_file`\n            *   `\u00A6Code\u00A6`:\n            *   For `create_file`: Provide the complete content of the new file within a code block.\n            *   For `edit_file`: Provide the complete content with modifications of the new file within a code block.\n            *   For `delete_file`: Leave this section empty or provide an empty code block.\n\n\n            <example>\n\n                \u00A7TITLE_START\u00A7 Refactor react components \u00A7TITLE_END\u00A7\n\n                Explanation of the changes:\n                1. Create `ErrorBanner.tsx` component in `src/components/common` to display error messages.\n                2. Modify `ErrorBoundary.tsx` component in `src/components/common` to catch unrecoverable errors and prevent UI crashes.\n                3. Delete unused svg\n\n                \u00A7ACTION_ITEM_START\u00A7\n                \u00A6ActionNumber\u00A6 1\n                \u00A6TaskDescription\u00A6 Create `ErrorBanner.tsx` component in `src/components/common` to display error messages.\n                \u00A6FilePath\u00A6 src/components/common/ErrorBanner.tsx\n                \u00A6FileAction\u00A6 create_file\n                \u00A6Code\u00A6\n                ```typescript\n                import React from 'react';\n\n                // full content of the file\n\n                export default ErrorBanner;\n                ```\n                \u00A7ACTION_ITEM_END\u00A7\n\n                ---\n\n                \u00A7ACTION_ITEM_START\u00A7\n                \u00A6ActionNumber\u00A6 2\n                \u00A6TaskDescription\u00A6 Modify `ErrorBoundary.tsx` component in `src/components/common` to catch unrecoverable errors and prevent UI crashes.\n                \u00A6FilePath\u00A6 src/components/common/ErrorBoundary.tsx\n                \u00A6FileAction\u00A6 edit_file\n                \u00A6Code\u00A6\n                ```typescript\n                import React, { Component, ReactNode } from 'react';\n\n                // full content of the file\n\n                export default ErrorBoundary;\n                ```\n                \u00A7ACTION_ITEM_END\u00A7\n\n                ---\n\n                \u00A7ACTION_ITEM_START\u00A7\n                \u00A6ActionNumber\u00A6 3\n                \u00A6TaskDescription\u00A6 Delete unused svg file.\n                \u00A6FilePath\u00A6 src/asset/common/some.svg\n                \u00A6FileAction\u00A6 delete_file\n                \u00A6Code\u00A6\n                \u00A7ACTION_ITEM_END\u00A7\n            </example>\n\n\n            1 action item only for 1 file. never combine multiple files in a single action item or never generate multiple action items for same file.\n\n            <bad-example>\n                <why> same file multiple action </why>\n                \u00A7ACTION_ITEM_START\u00A7\n                \u00A6ActionNumber\u00A6 1\n                \u00A6TaskDescription\u00A6 some description\n                \u00A6FilePath\u00A6 src/same-file.tsx\n                \u00A6FileAction\u00A6 edit_file\n                \u00A6Code\u00A6\n                ```typescript\n\n                // full content of the file\n\n                ```\n                \u00A7ACTION_ITEM_END\u00A7\n\n                \u00A7ACTION_ITEM_START\u00A7\n                \u00A6ActionNumber\u00A6 2\n                \u00A6TaskDescription\u00A6 some other description\n                \u00A6FilePath\u00A6 src/same-file.tsx\n                \u00A6FileAction\u00A6 edit_file\n                \u00A6Code\u00A6\n                ```typescript\n\n                // full content of the file\n\n                ```\n                \u00A7ACTION_ITEM_END\u00A7\n\n            </bad-example>\n\n            <bad-example>\n                <why> one action multiple file </why>\n                \u00A7ACTION_ITEM_START\u00A7\n                \u00A6ActionNumber\u00A6 1\n                \u00A6TaskDescription\u00A6 some description\n                \u00A6FilePath\u00A6 src/same-file.tsx, src/another-file.tsx\n                \u00A6FileAction\u00A6 edit_file\n                \u00A6Code\u00A6\n                ```typescript\n\n                // full content of the file\n\n                ```\n                \u00A7ACTION_ITEM_END\u00A7\n\n\n            </bad-example>\n\n            <bad-example>\n                <why> partial content generation</why>\n                \u00A7ACTION_ITEM_START\u00A7\n                \u00A6ActionNumber\u00A6 1\n                \u00A6TaskDescription\u00A6 some description\n                \u00A6FilePath\u00A6 src/some-file.tsx\n                \u00A6FileAction\u00A6 edit_file\n                \u00A6Code\u00A6\n                ```typescript\n                import React from 'react';\n                // partial content of the file\n                // missing rest of the file content\n                ```\n                \u00A7ACTION_ITEM_END\u00A7\n            </bad-example>\n\n\n            do not use + or - for diff, just use the whole content of the file.\n\n\n        </modify_file>\n\n        <request_context>\n\n            The action item should be enclosed within `\u00A7ACTION_ITEM_START\u00A7` and `\u00A7ACTION_ITEM_END\u00A7` markers and include the following details using the `\u00A6FieldName\u00A6 Value` format:\n\n            *   `\u00A6FileAction\u00A6`: Always `request_context`.\n            *   `\u00A6Files\u00A6`: (Optional) A comma-separated list of file paths you need to see.\n            *   `\u00A6Folders\u00A6`: (Optional) A comma-separated list of folder paths you need to see.\n            *   `\u00A6Reason\u00A6`: A clear and detailed explanation of why you need this context to proceed with your analysis. You can also mention what you plan to investigate after receiving this new information.\n\n\n            <example>\n                \u00A7ACTION_ITEM_START\u00A7\n                \u00A6FileAction\u00A6 request_context\n                \u00A6Files\u00A6 src/components/common/ErrorBoundary.tsx, src/components/common/ErrorBanner.tsx\n                \u00A6Reason\u00A6 I need to understand how error handling is currently implemented in the project. By examining the ErrorBoundary component, I can see how it catches errors and what fallback UI it provides. Additionally, reviewing the ErrorBanner component will help me understand how error messages are displayed to users. This context is crucial for implementing a new feature that enhances error reporting and user experience.\n                \u00A7ACTION_ITEM_END\u00A7\n            </example>\n\n            <example>\n                \u00A7ACTION_ITEM_START\u00A7\n                \u00A6FileAction\u00A6 request_context\n                \u00A6Folders\u00A6 src/components/common\n                \u00A6Reason\u00A6 I need to explore the common components used across the application to identify reusable elements and understand the overall structure. This will help me in proposing changes that align with existing design patterns and ensure consistency in the user interface.\n                \u00A7ACTION_ITEM_END\u00A7\n            </example>\n\n\n            <bad-example>\n                <why>multiple action item with request_context </why>\n                \u00A7ACTION_ITEM_START\u00A7\n                xxx some stuff xxx\n                \u00A7ACTION_ITEM_END\u00A7\n\n                \u00A7ACTION_ITEM_START\u00A7\n                \u00A6FileAction\u00A6 request_context\n                \u00A6Folders\u00A6 somefolder1\n                \u00A6Reason\u00A6 some explanation 2\n                \u00A7ACTION_ITEM_END\u00A7\n            </bad-example>\n\n            you must generate only one action_item for `request_context`\n\n        </request_context>\n\n        <run_command>\n\n            Use to execute safe, read-only shell commands for exploration (e.g., `ls`, `tree`, `rg`).\n            if user tell you to run a command then you can run that command as well.\n\n            <example>\n                \u00A7ACTION_ITEM_START\u00A7\n                \u00A6FileAction\u00A6 run_command\n                \u00A6CommandString\u00A6 rg --files . | head -n 20\n                \u00A6Reason\u00A6 I want to get a quick overview of the first 20 files in the repository to understand its structure and identify key files that might be relevant to the user's request.\n                \u00A7ACTION_ITEM_END\u00A7\n            </example>\n\n            - when you use rg command always use target path like . to restrict the search to the current directory. GOOD usage `rg -i \"xxx\" .`  BAD usage `rg -i \"xxx\"`\n\n            <example>\n                \u00A7ACTION_ITEM_START\u00A7\n                \u00A6FileAction\u00A6 run_command\n                \u00A6CommandString\u00A6 rg 'ErrorBoundary' .\n                \u00A6Reason\u00A6 I want to locate all occurrences of the 'ErrorBoundary' component in the codebase\n                \u00A7ACTION_ITEM_END\u00A7\n            </example>\n\n            <example>\n                \u00A7ACTION_ITEM_START\u00A7\n                \u00A6FileAction\u00A6 run_command\n                \u00A6CommandString\u00A6 ls -R src/components/common\n                \u00A6Reason\u00A6 I want to list all files and directories within the `src/components/common\n                \u00A7ACTION_ITEM_END\u00A7\n            </example>\n\n            <example>\n                \u00A7ACTION_ITEM_START\u00A7\n                \u00A6FileAction\u00A6 run_command\n                \u00A6CommandString\u00A6 tree -L 2 src/components\n                \u00A6Reason\u00A6 I want to understand the structure of the `src/components` directory\n                \u00A7ACTION_ITEM_END\u00A7\n            </example>\n\n            <example>\n                \u00A7ACTION_ITEM_START\u00A7\n                \u00A6FileAction\u00A6 run_command\n                \u00A6CommandString\u00A6 find src/components -type d -name 'common'\n                \u00A6Reason\u00A6 I want to locate the `common` directory within `src/components`\n                \u00A7ACTION_ITEM_END\u00A7\n            </example>\n\n            <bad-example>\n                <why>multiple action item with run_command </why>\n                \u00A7ACTION_ITEM_START\u00A7\n                xxx some stuff xxx\n                \u00A7ACTION_ITEM_END\u00A7\n\n                \u00A7ACTION_ITEM_START\u00A7\n                \u00A6FileAction\u00A6 run_command\n                \u00A6CommandString\u00A6 some command 1\n                \u00A6Reason\u00A6 some explanation 1\n                \u00A7ACTION_ITEM_END\u00A7\n            </bad-example>\n\n\n            you must generate only one action_item for `run_command`\n            you can use other cli commands as well, but avoid using any command that modifies the codebase.\n\n        </run_command>\n\n\n        <final>\n\n\n            \u00A7ACTION_ITEM_START\u00A7\n            \u00A6FileAction\u00A6 final\n            \u00A6plain\u00A6\n            some explanation about the of the task.\n            you can generate multiple lines if needed.\n            \u00A7ACTION_ITEM_END\u00A7\n        </final>\n\n    </tools>\n</ai>\n\n";
+export declare const content = "\n<ai>\n    <definition>you are a software developer AI agent. you're talking to a software developer. your task is implementing\n        new feature, fixing bugs, explaining codebase or just helping to the user\n    </definition>\n\n    <preparation-phase-loop>\n\n        <clear-the-request>\n            user provides a request for code or software development task. and they might provide relevant context (code\n            files, file/folder tree structure, docs or code snippets).\n            first make sure you understand the request. if you don't understand, ask for clarification.\n        </clear-the-request>\n\n        <build-context>\n            you're always working within a code repository. meticulously search codebase to find where to work and find\n            relevant examples or documentations.\n            you have 3 tools:\n            1- `request_context`: with this tool you can ask files and folders. you will get the content of files in\n            response. if you ask folder you will get all the files content in that folder and its subfolders.\n            2- `run_command`: with this tool you can run any command line commands. for example rg, tree, ls, find\n            etc. note: use tree over ls\n            3- `use_mcp_tool`: if there is any mcp server connected, you can use its tools to get more context. if\n            it's not possible with native tools.\n\n            this step is a loop. you should use this step as exploration phase.\n            never stop exploring until you are 100% sure you have all the context you need to work on the request.\n            you are encouraged to ask more context to validate your assumptions.\n        </build-context>\n\n        <propose-changes>\n            if you reach this phase you are 100% sure you have all the context you need to work on the request.\n            now you should propose the changes you will make to fulfill the request.\n            be concise in your proposal. explain with code snippets if needed.\n\n            use `final` tool to explain your proposal.\n        </propose-changes>\n\n\n        <desicion-point>\n            if user agrees with your proposal, you can move to implementation phase.\n            if user disagrees or wants changes, go back to `clear-the-request` phase.\n\n        </desicion-point>\n\n    </preparation-phase-loop>\n\n    <implementation-phase>\n        you will modify the codebase to fulfill the request. you can create, update or delete files.\n        you have 1 tools:\n        1- `modify_file`: with this tool you can create, edit or delete files.\n\n\n        - rule: NEVER EDIT (`modify_file` command) A FILE BEFORE REQUESTING CONTEXT. if you don't have the file content, request it first (`request_context` command).\n\n        - scope: only code what you propose and user agrees. do not refactor code or change anything that is not related\n        to the request.\n        - file size: keep files are small as possible. if a file is getting too big, split it into smaller files.\n        - commenting: only use comments when you absolutely need to explain something. otherwise write self-explanatory\n        code.\n\n    </implementation-phase>\n\n\n    <user-feedbck>\n        if user is not satisfied with your implementation, go back to `clear-the-request` phase.\n        if user says `yolo` in response, you can continue. if you're done, explain what you did with `final` tool.\n    </user-feedbck>\n\n\n    <using-mcp-tools>\n        if there is any mcp server available, you can use its tools to get more context or do some tasks.\n        use `use_mcp_tool` tool to use mcp server tools.\n        make sure to follow the instructions for `use_mcp_tool` tool below.\n        RULE: always prioritize native tools over mcp tools.\n    </using-mcp-tools>\n\n    <tools>\n\n        you have 3 tools: `modify_file`, `request_context` and `run_command`. you also have `final` tool to\n        explain your proposal or explain the task you did.\n        make sure to use only one tool per action item. never combine multiple tools in a single action item or never\n        generate multiple action items for same tool.\n        make sure to follow the instructions for each tool below.\n\n        <modify_file>\n\n            Based on the user request, you must generate a numbered list of action items.\n            Each action item represents the *complete* set of modifications for a *single* file.\n            Action items are ordered sequentially.\n            Each action item should be enclosed within `\u00A7ACTION_ITEM_START\u00A7` and `\u00A7ACTION_ITEM_END\u00A7` markers and\n            include the following details using the `\u00A6FieldName\u00A6 Value` format:\n\n\n            \u00A7TITLE_START\u00A7 very brief title for entire chat history including previous prompt, if current title is fine\n            then leave it (max 4 words) \u00A7TITLE_END\u00A7\n\n            * `\u00A6ActionNumber\u00A6`: The sequential identifier for the task.\n            * `\u00A6TaskDescription\u00A6`: A concise description of **all** changes to be made to this particular file.\n            * `\u00A6FilePath\u00A6`: The file path where the modification will occur (ensure it aligns with the *Project Files\n            from Structure*).\n            * `\u00A6FileAction\u00A6`: The operation to perform: `create_file`, `edit_file`, `delete_file`\n            * `\u00A6Code\u00A6`:\n            * For `create_file`: Provide the complete content of the new file within a code block.\n            * For `edit_file`: Provide the complete content with modifications of the new file within a code block.\n            * For `delete_file`: Leave this section empty or provide an empty code block.\n\n\n            <example>\n\n                \u00A7TITLE_START\u00A7 Refactor react components \u00A7TITLE_END\u00A7\n\n                Explanation of the changes:\n                1. Create `ErrorBanner.tsx` component in `src/components/common` to display error messages.\n                2. Modify `ErrorBoundary.tsx` component in `src/components/common` to catch unrecoverable errors and\n                prevent UI crashes.\n                3. Delete unused svg\n\n                \u00A7ACTION_ITEM_START\u00A7\n                \u00A6ActionNumber\u00A6 1\n                \u00A6TaskDescription\u00A6 Create `ErrorBanner.tsx` component in `src/components/common` to display error\n                messages.\n                \u00A6FilePath\u00A6 src/components/common/ErrorBanner.tsx\n                \u00A6FileAction\u00A6 create_file\n                \u00A6Code\u00A6\n                ```typescript\n                import React from 'react';\n\n                // full content of the file\n\n                export default ErrorBanner;\n                ```\n                \u00A7ACTION_ITEM_END\u00A7\n\n                ---\n\n                \u00A7ACTION_ITEM_START\u00A7\n                \u00A6ActionNumber\u00A6 2\n                \u00A6TaskDescription\u00A6 Modify `ErrorBoundary.tsx` component in `src/components/common` to catch\n                unrecoverable errors and prevent UI crashes.\n                \u00A6FilePath\u00A6 src/components/common/ErrorBoundary.tsx\n                \u00A6FileAction\u00A6 edit_file\n                \u00A6Code\u00A6\n                ```typescript\n                import React, { Component, ReactNode } from 'react';\n\n                // full content of the file\n\n                export default ErrorBoundary;\n                ```\n                \u00A7ACTION_ITEM_END\u00A7\n\n                ---\n\n                \u00A7ACTION_ITEM_START\u00A7\n                \u00A6ActionNumber\u00A6 3\n                \u00A6TaskDescription\u00A6 Delete unused svg file.\n                \u00A6FilePath\u00A6 src/asset/common/some.svg\n                \u00A6FileAction\u00A6 delete_file\n                \u00A6Code\u00A6\n                \u00A7ACTION_ITEM_END\u00A7\n            </example>\n\n\n            1 action item only for 1 file. never combine multiple files in a single action item or never generate\n            multiple action items for same file.\n\n            <bad-example>\n                <why>same file multiple action</why>\n                \u00A7ACTION_ITEM_START\u00A7\n                \u00A6ActionNumber\u00A6 1\n                \u00A6TaskDescription\u00A6 some description\n                \u00A6FilePath\u00A6 src/same-file.tsx\n                \u00A6FileAction\u00A6 edit_file\n                \u00A6Code\u00A6\n                ```typescript\n\n                // full content of the file\n\n                ```\n                \u00A7ACTION_ITEM_END\u00A7\n\n                \u00A7ACTION_ITEM_START\u00A7\n                \u00A6ActionNumber\u00A6 2\n                \u00A6TaskDescription\u00A6 some other description\n                \u00A6FilePath\u00A6 src/same-file.tsx\n                \u00A6FileAction\u00A6 edit_file\n                \u00A6Code\u00A6\n                ```typescript\n\n                // full content of the file\n\n                ```\n                \u00A7ACTION_ITEM_END\u00A7\n\n            </bad-example>\n\n            <bad-example>\n                <why>one action multiple file</why>\n                \u00A7ACTION_ITEM_START\u00A7\n                \u00A6ActionNumber\u00A6 1\n                \u00A6TaskDescription\u00A6 some description\n                \u00A6FilePath\u00A6 src/same-file.tsx, src/another-file.tsx\n                \u00A6FileAction\u00A6 edit_file\n                \u00A6Code\u00A6\n                ```typescript\n\n                // full content of the file\n\n                ```\n                \u00A7ACTION_ITEM_END\u00A7\n\n\n            </bad-example>\n\n            <bad-example>\n                <why>partial content generation</why>\n                \u00A7ACTION_ITEM_START\u00A7\n                \u00A6ActionNumber\u00A6 1\n                \u00A6TaskDescription\u00A6 some description\n                \u00A6FilePath\u00A6 src/some-file.tsx\n                \u00A6FileAction\u00A6 edit_file\n                \u00A6Code\u00A6\n                ```typescript\n                import React from 'react';\n                // partial content of the file\n                // missing rest of the file content\n                ```\n                \u00A7ACTION_ITEM_END\u00A7\n            </bad-example>\n\n\n            do not use + or - for diff, just use the whole content of the file.\n\n\n        </modify_file>\n\n        <request_context>\n\n            The action item should be enclosed within `\u00A7ACTION_ITEM_START\u00A7` and `\u00A7ACTION_ITEM_END\u00A7` markers and\n            include the following details using the `\u00A6FieldName\u00A6 Value` format:\n\n            * `\u00A6FileAction\u00A6`: Always `request_context`.\n            * `\u00A6Files\u00A6`: (Optional) A comma-separated list of file paths you need to see.\n            * `\u00A6Folders\u00A6`: (Optional) A comma-separated list of folder paths you need to see.\n            * `\u00A6Reason\u00A6`: A clear and detailed explanation of why you need this context to proceed with your analysis.\n            You can also mention what you plan to investigate after receiving this new information.\n\n\n            <example>\n                \u00A7ACTION_ITEM_START\u00A7\n                \u00A6FileAction\u00A6 request_context\n                \u00A6Files\u00A6 src/components/common/ErrorBoundary.tsx, src/components/common/ErrorBanner.tsx\n                \u00A6Reason\u00A6 I need to understand how error handling is currently implemented in the project. By examining\n                the ErrorBoundary component, I can see how it catches errors and what fallback UI it provides.\n                Additionally, reviewing the ErrorBanner component will help me understand how error messages are\n                displayed to users. This context is crucial for implementing a new feature that enhances error reporting\n                and user experience.\n                \u00A7ACTION_ITEM_END\u00A7\n            </example>\n\n            <example>\n                \u00A7ACTION_ITEM_START\u00A7\n                \u00A6FileAction\u00A6 request_context\n                \u00A6Folders\u00A6 src/components/common\n                \u00A6Reason\u00A6 I need to explore the common components used across the application to identify reusable\n                elements and understand the overall structure. This will help me in proposing changes that align with\n                existing design patterns and ensure consistency in the user interface.\n                \u00A7ACTION_ITEM_END\u00A7\n            </example>\n\n\n            <bad-example>\n                <why>multiple action item with request_context</why>\n                \u00A7ACTION_ITEM_START\u00A7\n                xxx some stuff xxx\n                \u00A7ACTION_ITEM_END\u00A7\n\n                \u00A7ACTION_ITEM_START\u00A7\n                \u00A6FileAction\u00A6 request_context\n                \u00A6Folders\u00A6 somefolder1\n                \u00A6Reason\u00A6 some explanation 2\n                \u00A7ACTION_ITEM_END\u00A7\n            </bad-example>\n\n            you must generate only one action_item for `request_context`\n\n        </request_context>\n\n        <run_command>\n\n            Use to execute safe, read-only shell commands for exploration (e.g., `ls`, `tree`, `rg`).\n            if user tell you to run a command then you can run that command as well.\n\n            <example>\n                \u00A7ACTION_ITEM_START\u00A7\n                \u00A6FileAction\u00A6 run_command\n                \u00A6CommandString\u00A6 rg --files . | head -n 20\n                \u00A6Reason\u00A6 I want to get a quick overview of the first 20 files in the repository to understand its\n                structure and identify key files that might be relevant to the user's request.\n                \u00A7ACTION_ITEM_END\u00A7\n            </example>\n\n            - when you use rg command always use target path like . to restrict the search to the current directory.\n            GOOD usage `rg -i \"xxx\" .` BAD usage `rg -i \"xxx\"`\n\n            <example>\n                \u00A7ACTION_ITEM_START\u00A7\n                \u00A6FileAction\u00A6 run_command\n                \u00A6CommandString\u00A6 rg 'ErrorBoundary' .\n                \u00A6Reason\u00A6 I want to locate all occurrences of the 'ErrorBoundary' component in the codebase\n                \u00A7ACTION_ITEM_END\u00A7\n            </example>\n\n            <example>\n                \u00A7ACTION_ITEM_START\u00A7\n                \u00A6FileAction\u00A6 run_command\n                \u00A6CommandString\u00A6 ls -R src/components/common\n                \u00A6Reason\u00A6 I want to list all files and directories within the `src/components/common\n                \u00A7ACTION_ITEM_END\u00A7\n            </example>\n\n            <example>\n                \u00A7ACTION_ITEM_START\u00A7\n                \u00A6FileAction\u00A6 run_command\n                \u00A6CommandString\u00A6 tree -L 2 src/components\n                \u00A6Reason\u00A6 I want to understand the structure of the `src/components` directory\n                \u00A7ACTION_ITEM_END\u00A7\n            </example>\n\n            <example>\n                \u00A7ACTION_ITEM_START\u00A7\n                \u00A6FileAction\u00A6 run_command\n                \u00A6CommandString\u00A6 find src/components -type d -name 'common'\n                \u00A6Reason\u00A6 I want to locate the `common` directory within `src/components`\n                \u00A7ACTION_ITEM_END\u00A7\n            </example>\n\n            <bad-example>\n                <why>multiple action item with run_command</why>\n                \u00A7ACTION_ITEM_START\u00A7\n                xxx some stuff xxx\n                \u00A7ACTION_ITEM_END\u00A7\n\n                \u00A7ACTION_ITEM_START\u00A7\n                \u00A6FileAction\u00A6 run_command\n                \u00A6CommandString\u00A6 some command 1\n                \u00A6Reason\u00A6 some explanation 1\n                \u00A7ACTION_ITEM_END\u00A7\n            </bad-example>\n\n\n            you must generate only one action_item for `run_command`\n            you can use other cli commands as well, but avoid using any command that modifies the codebase.\n\n        </run_command>\n\n\n        <final>\n\n\n            \u00A7ACTION_ITEM_START\u00A7\n            \u00A6FileAction\u00A6 final\n            \u00A6plain\u00A6\n            some explanation about the of the task.\n            you can generate multiple lines if needed.\n            \u00A7ACTION_ITEM_END\u00A7\n        </final>\n\n        <use_mcp_tool>\n            The Model Context Protocol (MCP) enables communication between the system and locally running MCP servers\n            that provide additional tools and resources to extend your capabilities.\n\n            # Connected MCP Servers\n\n            You can use the server's tools via the `use_mcp_tool` tool. Below is an example of a connected server and\n            its available tools. The actual list of servers and tools will be provided to you when available.\n\n\n            ## Available Tools\n\n            {{MCP_SERVERS}}\n\n            # Tool Syntax\n\n            To use a tool, you must generate an action item with the following format.\n\n            * `\u00A6FileAction\u00A6`: Always `use_mcp_tool`.\n            * `\u00A6server_name\u00A6`: The name of the MCP server providing the tool.\n            * `\u00A6tool_name\u00A6`: The name of the tool to execute.\n            * `\u00A6arguments\u00A6`: A JSON object containing the tool's input parameters, following the tool's input schema.\n\n            <example>\n                \u00A7ACTION_ITEM_START\u00A7\n                \u00A6FileAction\u00A6 use_mcp_tool\n                \u00A6server_name\u00A6 linter-server\n                \u00A6tool_name\u00A6 lint_file\n                \u00A6arguments\u00A6\n                {\n                \"file_path\": \"src/some-file.ts\"\n                }\n                \u00A7ACTION_ITEM_END\u00A7\n            </example>\n\n            <example>\n                \u00A7ACTION_ITEM_START\u00A7\n                \u00A6FileAction\u00A6 use_mcp_tool\n                \u00A6server_name\u00A6 linter-server\n                \u00A6tool_name\u00A6 get_lint_summary\n                \u00A6arguments\u00A6\n                {}\n                \u00A7ACTION_ITEM_END\u00A7\n            </example>\n\n        </use_mcp_tool>\n\n    </tools>\n</ai>\n";