@codebolt/agent 1.2.1 → 2.2.3

package/dist/processor-pieces/messageModifiers/coreSystemPromptModifier.js

@@ -0,0 +1,130 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.CoreSystemPromptModifier = void 0;
+const base_1 = require("../base");
+class CoreSystemPromptModifier extends base_1.BaseMessageModifier {
+    constructor(options = {}) {
+        super();
+        this.options = options;
+    }
+    modify(originalRequest, createdMessage) {
+        var _a;
+        // Get user memory from metadata or options
+        const userMemory = ((_a = createdMessage.metadata) === null || _a === void 0 ? void 0 : _a.userMemory) || this.options.userMemory;
+        const systemPrompt = this.options.customSystemPrompt || this.getCoreSystemPrompt(userMemory);
+        const systemMessage = {
+            role: 'system',
+            content: systemPrompt
+        };
+        // Find existing system message or add new one
+        const messages = [...createdMessage.message.messages];
+        const systemMessageIndex = messages.findIndex(msg => msg.role === 'system');
+        if (systemMessageIndex !== -1) {
+            // Replace existing system message
+            messages[systemMessageIndex] = systemMessage;
+        }
+        else {
+            // Add new system message at the beginning
+            messages.unshift(systemMessage);
+        }
+        return Promise.resolve({
+            message: {
+                ...createdMessage.message,
+                messages
+            },
+            metadata: {
+                ...createdMessage.metadata,
+                coreSystemPromptAdded: true,
+                systemPromptSource: this.options.customSystemPrompt ? 'custom' : 'default',
+                hasUserMemory: !!userMemory
+            }
+        });
+    }
+    getCoreSystemPrompt(userMemory) {
+        const basePrompt = this.getDefaultSystemPrompt();
+        // Add user memory with separator if provided (exactly like gemini-cli)
+        const memorySuffix = userMemory && userMemory.trim().length > 0
+            ? `\n\n---\n\n${userMemory.trim()}`
+            : '';
+        return `${basePrompt}${memorySuffix}`;
+    }
+    getDefaultSystemPrompt() {
+        return `
+You are an interactive CLI agent specializing in software engineering tasks. Your primary goal is to help users safely and efficiently, adhering strictly to the following instructions and utilizing your available tools.
+
+# Core Mandates
+
+- **Conventions:** Rigorously adhere to existing project conventions when reading or modifying code. Analyze surrounding code, tests, and configuration first.
+- **Libraries/Frameworks:** NEVER assume a library/framework is available or appropriate. Verify its established usage within the project (check imports, configuration files like 'package.json', 'Cargo.toml', 'requirements.txt', 'build.gradle', etc., or observe neighboring files) before employing it.
+- **Style & Structure:** Mimic the style (formatting, naming), structure, framework choices, typing, and architectural patterns of existing code in the project.
+- **Idiomatic Changes:** When editing, understand the local context (imports, functions/classes) to ensure your changes integrate naturally and idiomatically.
+- **Comments:** Add code comments sparingly. Focus on *why* something is done, especially for complex logic, rather than *what* is done. Only add high-value comments if necessary for clarity or if requested by the user. Do not edit comments that are separate from the code you are changing. *NEVER* talk to the user or describe your changes through comments.
+- **Proactiveness:** Fulfill the user's request thoroughly, including reasonable, directly implied follow-up actions.
+- **Confirm Ambiguity/Expansion:** Do not take significant actions beyond the clear scope of the request without confirming with the user. If asked *how* to do something, explain first, don't just do it.
+- **Explaining Changes:** After completing a code modification or file operation *do not* provide summaries unless asked.
+- **Path Construction:** Before using any file system tool, you must construct the full absolute path for the file_path argument. Always combine the absolute path of the project's root directory with the file's path relative to the root. For example, if the project root is /path/to/project/ and the file is foo/bar/baz.txt, the final path you must use is /path/to/project/foo/bar/baz.txt. If the user provides a relative path, you must resolve it against the root directory to create an absolute path.
+- **Do Not revert changes:** Do not revert changes to the codebase unless asked to do so by the user. Only revert changes made by you if they have resulted in an error or if the user has explicitly asked you to revert the changes.
+
+# Primary Workflows
+
+## Software Engineering Tasks
+When requested to perform tasks like fixing bugs, adding features, refactoring, or explaining code, follow this sequence:
+1. **Understand:** Think about the user's request and the relevant codebase context. Use search tools extensively (in parallel if independent) to understand file structures, existing code patterns, and conventions. Use file reading tools to understand context and validate any assumptions you may have.
+2. **Plan:** Build a coherent and grounded (based on the understanding in step 1) plan for how you intend to resolve the user's task. Share an extremely concise yet clear plan with the user if it would help the user understand your thought process. As part of the plan, you should try to use a self-verification loop by writing unit tests if relevant to the task. Use output logs or debug statements as part of this self verification loop to arrive at a solution.
+3. **Implement:** Use the available tools to act on the plan, strictly adhering to the project's established conventions (detailed under 'Core Mandates').
+4. **Verify (Tests):** If applicable and feasible, verify the changes using the project's testing procedures. Identify the correct test commands and frameworks by examining 'README' files, build/package configuration (e.g., 'package.json'), or existing test execution patterns. NEVER assume standard test commands.
+5. **Verify (Standards):** VERY IMPORTANT: After making code changes, execute the project-specific build, linting and type-checking commands (e.g., 'tsc', 'npm run lint', 'ruff check .') that you have identified for this project (or obtained from the user). This ensures code quality and adherence to standards. If unsure about these commands, you can ask the user if they'd like you to run them and if so how to.
+
+## New Applications
+
+**Goal:** Autonomously implement and deliver a visually appealing, substantially complete, and functional prototype. Utilize all tools at your disposal to implement the application.
+
+1. **Understand Requirements:** Analyze the user's request to identify core features, desired user experience (UX), visual aesthetic, application type/platform (web, mobile, desktop, CLI, library, 2D or 3D game), and explicit constraints. If critical information for initial planning is missing or ambiguous, ask concise, targeted clarification questions.
+2. **Propose Plan:** Formulate an internal development plan. Present a clear, concise, high-level summary to the user. This summary must effectively convey the application's type and core purpose, key technologies to be used, main features and how users will interact with them, and the general approach to the visual design and user experience (UX) with the intention of delivering something beautiful, modern, and polished, especially for UI-based applications. For applications requiring visual assets (like games or rich UIs), briefly describe the strategy for sourcing or generating placeholders (e.g., simple geometric shapes, procedurally generated patterns, or open-source assets if feasible and licenses permit) to ensure a visually complete initial prototype. Ensure this information is presented in a structured and easily digestible manner.
+  - When key technologies aren't specified, prefer the following:
+  - **Websites (Frontend):** React (JavaScript/TypeScript) with Bootstrap CSS, incorporating Material Design principles for UI/UX.
+  - **Back-End APIs:** Node.js with Express.js (JavaScript/TypeScript) or Python with FastAPI.
+  - **Full-stack:** Next.js (React/Node.js) using Bootstrap CSS and Material Design principles for the frontend, or Python (Django/Flask) for the backend with a React/Vue.js frontend styled with Bootstrap CSS and Material Design principles.
+  - **CLIs:** Python or Go.
+  - **Mobile App:** Compose Multiplatform (Kotlin Multiplatform) or Flutter (Dart) using Material Design libraries and principles, when sharing code between Android and iOS. Jetpack Compose (Kotlin JVM) with Material Design principles or SwiftUI (Swift) for native apps targeted at either Android or iOS, respectively.
+  - **3d Games:** HTML/CSS/JavaScript with Three.js.
+  - **2d Games:** HTML/CSS/JavaScript.
+3. **User Approval:** Obtain user approval for the proposed plan.
+4. **Implementation:** Autonomously implement each feature and design element per the approved plan utilizing all available tools. When starting ensure you scaffold the application using shell commands for commands like 'npm init', 'npx create-react-app'. Aim for full scope completion. Proactively create or source necessary placeholder assets (e.g., images, icons, game sprites, 3D models using basic primitives if complex assets are not generatable) to ensure the application is visually coherent and functional, minimizing reliance on the user to provide these. If the model can generate simple assets (e.g., a uniformly colored square sprite, a simple 3D cube), it should do so. Otherwise, it should clearly indicate what kind of placeholder has been used and, if absolutely necessary, what the user might replace it with. Use placeholders only when essential for progress, intending to replace them with more refined versions or instruct the user on replacement during polishing if generation is not feasible.
+5. **Verify:** Review work against the original request, the approved plan. Fix bugs, deviations, and all placeholders where feasible, or ensure placeholders are visually adequate for a prototype. Ensure styling, interactions, produce a high-quality, functional and beautiful prototype aligned with design goals. Finally, but MOST importantly, build the application and ensure there are no compile errors.
+6. **Solicit Feedback:** If still applicable, provide instructions on how to start the application and request user feedback on the prototype.
+
+# Operational Guidelines
+
+## Tone and Style (CLI Interaction)
+- **Concise & Direct:** Adopt a professional, direct, and concise tone suitable for a CLI environment.
+- **Minimal Output:** Aim for fewer than 3 lines of text output (excluding tool use/code generation) per response whenever practical. Focus strictly on the user's query.
+- **Clarity over Brevity (When Needed):** While conciseness is key, prioritize clarity for essential explanations or when seeking necessary clarification if a request is ambiguous.
+- **No Chitchat:** Avoid conversational filler, preambles ("Okay, I will now..."), or postambles ("I have finished the changes..."). Get straight to the action or answer.
+- **Formatting:** Use GitHub-flavored Markdown. Responses will be rendered in monospace.
+- **Tools vs. Text:** Use tools for actions, text output *only* for communication. Do not add explanatory comments within tool calls or code blocks unless specifically part of the required code/command itself.
+- **Handling Inability:** If unable/unwilling to fulfill a request, state so briefly (1-2 sentences) without excessive justification. Offer alternatives if appropriate.
+
+## Security and Safety Rules
+- **Explain Critical Commands:** Before executing commands that modify the file system, codebase, or system state, you *must* provide a brief explanation of the command's purpose and potential impact. Prioritize user understanding and safety. You should not ask permission to use the tool; the user will be presented with a confirmation dialogue upon use (you do not need to tell them this).
+- **Security First:** Always apply security best practices. Never introduce code that exposes, logs, or commits secrets, API keys, or other sensitive information.
+
+## Tool Usage
+- **File Paths:** Always use absolute paths when referring to files with tools. Relative paths are not supported. You must provide an absolute path.
+- **Parallelism:** Execute multiple independent tool calls in parallel when feasible (i.e. searching the codebase).
+- **Command Execution:** Use shell tools for running shell commands, remembering the safety rule to explain modifying commands first.
+- **Background Processes:** Use background processes (via \`&\`) for commands that are unlikely to stop on their own, e.g. \`node server.js &\`. If unsure, ask the user.
+- **Interactive Commands:** Try to avoid shell commands that are likely to require user interaction (e.g. \`git rebase -i\`). Use non-interactive versions of commands (e.g. \`npm init -y\` instead of \`npm init\`) when available, and otherwise remind the user that interactive shell commands are not supported and may cause hangs until canceled by the user.
+- **Remembering Facts:** Use memory tools to remember specific, *user-related* facts or preferences when the user explicitly asks, or when they state a clear, concise piece of information that would help personalize or streamline *your future interactions with them* (e.g., preferred coding style, common project paths they use, personal tool aliases). This tool is for user-specific information that should persist across sessions. Do *not* use it for general project context or information. If unsure whether to save something, you can ask the user, "Should I remember that for you?"
+- **Respect User Confirmations:** Most tool calls will first require confirmation from the user, where they will either approve or cancel the function call. If a user cancels a function call, respect their choice and do _not_ try to make the function call again. It is okay to request the tool call again _only_ if the user requests that same tool call on a subsequent prompt. When a user cancels a function call, assume best intentions from the user and consider inquiring if they prefer any alternative paths forward.
+
+## Interaction Details
+- **Help Command:** The user can use '/help' to display help information.
+- **Feedback:** To report a bug or provide feedback, please use the /bug command.
+
+# Final Reminder
+Your core function is efficient and safe assistance. Balance extreme conciseness with the crucial need for clarity, especially regarding safety and potential system modifications. Always prioritize user control and project conventions. Never make assumptions about the contents of files; instead use file reading tools to ensure you aren't making broad assumptions. Finally, you are an agent - please keep going until the user's query is completely resolved.
+        `.trim();
+    }
+}
+exports.CoreSystemPromptModifier = CoreSystemPromptModifier;

package/dist/processor-pieces/messageModifiers/directoryContextModifier.d.ts

@@ -0,0 +1,36 @@
+import { ProcessedMessage } from "@codebolt/types/agent";
+import { BaseMessageModifier } from "../base";
+import { FlatUserMessage } from "@codebolt/types/sdk";
+export interface DirectoryContextOptions {
+    workspaceDirectories?: string[];
+}
+export declare class DirectoryContextModifier extends BaseMessageModifier {
+    private readonly options;
+    private gitignorePatterns;
+    private gitignoreRegexes;
+    constructor(options?: DirectoryContextOptions);
+    modify(originalRequest: FlatUserMessage, createdMessage: ProcessedMessage): Promise<ProcessedMessage>;
+    private loadGitignorePatterns;
+    private parseGitignoreContent;
+    private isGitIgnored;
+    private shouldIgnoreFile;
+    /**
+     * Generates a string representation of a directory's structure,
+     * limiting the number of items displayed. Ignored folders are shown
+     * followed by '...' instead of their contents.
+     *
+     * @param directory The absolute or relative path to the directory.
+     * @param options Optional configuration settings.
+     * @returns A promise resolving to the formatted folder structure string.
+     */
+    private getFolderStructure;
+    private readFullStructure;
+    /**
+     * Reads the directory structure using BFS, respecting maxItems.
+     * @param node The current node in the reduced structure.
+     * @param indent The current indentation string.
+     * @param isLast Sibling indicator.
+     * @param builder Array to build the string lines.
+     */
+    private formatStructure;
+}

package/dist/processor-pieces/messageModifiers/directoryContextModifier.js

@@ -0,0 +1,418 @@
+"use strict";
+var __createBinding = (this && this.__createBinding) || (Object.create ? (function(o, m, k, k2) {
+    if (k2 === undefined) k2 = k;
+    var desc = Object.getOwnPropertyDescriptor(m, k);
+    if (!desc || ("get" in desc ? !m.__esModule : desc.writable || desc.configurable)) {
+      desc = { enumerable: true, get: function() { return m[k]; } };
+    }
+    Object.defineProperty(o, k2, desc);
+}) : (function(o, m, k, k2) {
+    if (k2 === undefined) k2 = k;
+    o[k2] = m[k];
+}));
+var __setModuleDefault = (this && this.__setModuleDefault) || (Object.create ? (function(o, v) {
+    Object.defineProperty(o, "default", { enumerable: true, value: v });
+}) : function(o, v) {
+    o["default"] = v;
+});
+var __importStar = (this && this.__importStar) || (function () {
+    var ownKeys = function(o) {
+        ownKeys = Object.getOwnPropertyNames || function (o) {
+            var ar = [];
+            for (var k in o) if (Object.prototype.hasOwnProperty.call(o, k)) ar[ar.length] = k;
+            return ar;
+        };
+        return ownKeys(o);
+    };
+    return function (mod) {
+        if (mod && mod.__esModule) return mod;
+        var result = {};
+        if (mod != null) for (var k = ownKeys(mod), i = 0; i < k.length; i++) if (k[i] !== "default") __createBinding(result, mod, k[i]);
+        __setModuleDefault(result, mod);
+        return result;
+    };
+})();
+var __importDefault = (this && this.__importDefault) || function (mod) {
+    return (mod && mod.__esModule) ? mod : { "default": mod };
+};
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.DirectoryContextModifier = void 0;
+const base_1 = require("../base");
+const fs = __importStar(require("node:fs/promises"));
+const path = __importStar(require("node:path"));
+const codeboltjs_1 = __importDefault(require("@codebolt/codeboltjs"));
+const MAX_ITEMS = 200;
+const TRUNCATION_INDICATOR = '...';
+const DEFAULT_IGNORED_FOLDERS = new Set(['node_modules', '.git', 'dist', 'build', '.next', '.cache', '.tmp', 'tmp']);
+// Error handling utility (simplified version of gemini-cli's getErrorMessage)
+function getErrorMessage(error) {
+    if (error instanceof Error) {
+        return error.message;
+    }
+    try {
+        return String(error);
+    }
+    catch {
+        return 'Failed to get error details';
+    }
+}
+// Node error type guard
+function isNodeError(error) {
+    return error instanceof Error && 'code' in error;
+}
+class DirectoryContextModifier extends base_1.BaseMessageModifier {
+    constructor(options = {}) {
+        super();
+        this.gitignorePatterns = new Set();
+        this.gitignoreRegexes = [];
+        this.options = {
+            workspaceDirectories: options.workspaceDirectories || []
+        };
+    }
+    async modify(originalRequest, createdMessage) {
+        try {
+            // Get workspace directories from codebolt or use provided options
+            let workspaceDirectories = this.options.workspaceDirectories;
+            if (!workspaceDirectories || workspaceDirectories.length === 0) {
+                const { projectPath } = await codeboltjs_1.default.project.getProjectPath();
+                workspaceDirectories = projectPath ? [projectPath] : [];
+            }
+            if (workspaceDirectories.length === 0) {
+                return createdMessage;
+            }
+            // Load gitignore patterns from all workspace directories
+            await this.loadGitignorePatterns(workspaceDirectories);
+            const folderStructures = await Promise.all(workspaceDirectories.map((dir) => this.getFolderStructure(dir)));
+            const folderStructure = folderStructures.join('\n');
+            let workingDirPreamble;
+            if (workspaceDirectories.length === 1) {
+                workingDirPreamble = `I'm currently working in the directory: ${workspaceDirectories[0]}`;
+            }
+            else {
+                const dirList = workspaceDirectories.map((dir) => `  - ${dir}`).join('\n');
+                workingDirPreamble = `I'm currently working in the following directories:\n${dirList}`;
+            }
+            const directoryContext = `${workingDirPreamble}
+Here is the folder structure of the current working directories:
+
+${folderStructure}`;
+            const contextMessage = {
+                role: 'user', // Note: gemini-cli adds this as user message, not system
+                content: directoryContext
+            };
+            // Add as user message (like gemini-cli does)
+            const messages = [...createdMessage.message.messages, contextMessage];
+            return Promise.resolve({
+                message: {
+                    ...createdMessage.message,
+                    messages
+                },
+                metadata: {
+                    ...createdMessage.metadata,
+                    directoryContextAdded: true,
+                    workspaceDirectories
+                }
+            });
+        }
+        catch (error) {
+            console.error('Error in DirectoryContextModifier:', error);
+            return createdMessage;
+        }
+    }
+    async loadGitignorePatterns(workspaceDirectories) {
+        this.gitignorePatterns.clear();
+        this.gitignoreRegexes = [];
+        for (const dir of workspaceDirectories) {
+            try {
+                const gitignorePath = path.join(dir, '.gitignore');
+                const content = await fs.readFile(gitignorePath, 'utf-8');
+                this.parseGitignoreContent(content);
+            }
+            catch (error) {
+                // .gitignore file doesn't exist or can't be read, continue
+                console.debug(`No .gitignore found in ${dir}`);
+            }
+        }
+    }
+    parseGitignoreContent(content) {
+        const lines = content.split('\n')
+            .map(line => line.trim())
+            .filter(line => line && !line.startsWith('#')); // Remove empty lines and comments
+        for (const line of lines) {
+            this.gitignorePatterns.add(line);
+            // Convert gitignore pattern to regex
+            let regexPattern = line
+                .replace(/\./g, '\\.') // Escape dots
+                .replace(/\*/g, '.*') // Convert * to .*
+                .replace(/\?/g, '.') // Convert ? to .
+                .replace(/\//g, '\\/'); // Escape slashes
+            // Handle directory patterns (ending with /)
+            if (line.endsWith('/')) {
+                regexPattern = regexPattern.slice(0, -2) + '$'; // Remove \/ and add end anchor
+            }
+            try {
+                this.gitignoreRegexes.push(new RegExp(regexPattern));
+            }
+            catch (error) {
+                console.warn(`Invalid gitignore pattern: ${line}`);
+            }
+        }
+    }
+    isGitIgnored(filePath, fileName) {
+        // Check against gitignore patterns
+        for (const regex of this.gitignoreRegexes) {
+            if (regex.test(fileName) || regex.test(filePath)) {
+                return true;
+            }
+        }
+        // Check exact matches
+        return this.gitignorePatterns.has(fileName) ||
+            this.gitignorePatterns.has(filePath) ||
+            this.gitignorePatterns.has(fileName + '/'); // Directory pattern
+    }
+    shouldIgnoreFile(fileName, filePath) {
+        // Check gitignore first
+        if (filePath && this.isGitIgnored(filePath, fileName)) {
+            return true;
+        }
+        // Ignore hidden files (except .gitignore itself)
+        if (fileName.startsWith('.') && fileName !== '.gitignore') {
+            return true;
+        }
+        // Ignore temporary files and caches
+        const ignoredPatterns = [
+            /^───.*\.tar\.zst$/, // Weird temporary files like ───0069a971db0f139f.tar.zst
+            /\.tmp$/,
+            /\.temp$/,
+            /\.cache$/,
+            /\.log$/,
+            /\.swp$/,
+            /\.bak$/,
+            /~$/,
+            /^#.*#$/,
+            /\.DS_Store$/,
+            /Thumbs\.db$/,
+            /desktop\.ini$/,
+        ];
+        return ignoredPatterns.some(pattern => pattern.test(fileName));
+    }
+    /**
+     * Generates a string representation of a directory's structure,
+     * limiting the number of items displayed. Ignored folders are shown
+     * followed by '...' instead of their contents.
+     *
+     * @param directory The absolute or relative path to the directory.
+     * @param options Optional configuration settings.
+     * @returns A promise resolving to the formatted folder structure string.
+     */
+    async getFolderStructure(directory, options) {
+        var _a, _b;
+        const resolvedPath = path.resolve(directory);
+        const mergedOptions = {
+            maxItems: (_a = options === null || options === void 0 ? void 0 : options.maxItems) !== null && _a !== void 0 ? _a : MAX_ITEMS,
+            ignoredFolders: (_b = options === null || options === void 0 ? void 0 : options.ignoredFolders) !== null && _b !== void 0 ? _b : DEFAULT_IGNORED_FOLDERS,
+            fileIncludePattern: options === null || options === void 0 ? void 0 : options.fileIncludePattern,
+        };
+        try {
+            // 1. Read the structure using BFS, respecting maxItems
+            const structureRoot = await this.readFullStructure(resolvedPath, mergedOptions);
+            if (!structureRoot) {
+                return `Error: Could not read directory "${resolvedPath}". Check path and permissions.`;
+            }
+            // 2. Format the structure into a string
+            const structureLines = [];
+            // Pass true for isRoot for the initial call
+            this.formatStructure(structureRoot, '', true, true, structureLines);
+            // 3. Build the final output string
+            function isTruncated(node) {
+                if (node.hasMoreFiles || node.hasMoreSubfolders || node.isIgnored) {
+                    return true;
+                }
+                for (const sub of node.subFolders) {
+                    if (isTruncated(sub)) {
+                        return true;
+                    }
+                }
+                return false;
+            }
+            let summary = `Showing up to ${mergedOptions.maxItems} items (files + folders).`;
+            if (isTruncated(structureRoot)) {
+                summary += ` Folders or files indicated with ${TRUNCATION_INDICATOR} contain more items not shown, were ignored, or the display limit (${mergedOptions.maxItems} items) was reached.`;
+            }
+            return `${summary}\n\n${resolvedPath}${path.sep}\n${structureLines.join('\n')}`;
+        }
+        catch (error) {
+            console.error(`Error getting folder structure for ${resolvedPath}:`, error);
+            return `Error processing directory "${resolvedPath}": ${getErrorMessage(error)}`;
+        }
+    }
+    async readFullStructure(rootPath, options) {
+        const rootName = path.basename(rootPath);
+        const rootNode = {
+            name: rootName,
+            path: rootPath,
+            files: [],
+            subFolders: [],
+            totalChildren: 0,
+            totalFiles: 0,
+        };
+        const queue = [
+            { folderInfo: rootNode, currentPath: rootPath },
+        ];
+        let currentItemCount = 0;
+        // Count the root node itself as one item if we are not just listing its content
+        const processedPaths = new Set(); // To avoid processing same path if symlinks create loops
+        while (queue.length > 0) {
+            const { folderInfo, currentPath } = queue.shift();
+            if (processedPaths.has(currentPath)) {
+                continue;
+            }
+            processedPaths.add(currentPath);
+            if (currentItemCount >= options.maxItems) {
+                // If the root itself caused us to exceed, we can't really show anything.
+                // Otherwise, this folder won't be processed further.
+                // The parent that queued this would have set its own hasMoreSubfolders flag.
+                continue;
+            }
+            let entries;
+            try {
+                const rawEntries = await fs.readdir(currentPath, { withFileTypes: true });
+                // Sort entries alphabetically by name for consistent processing order
+                entries = rawEntries.sort((a, b) => a.name.localeCompare(b.name));
+            }
+            catch (error) {
+                if (isNodeError(error) &&
+                    (error.code === 'EACCES' || error.code === 'ENOENT')) {
+                    console.warn(`Warning: Could not read directory ${currentPath}: ${error.message}`);
+                    if (currentPath === rootPath && error.code === 'ENOENT') {
+                        return null; // Root directory itself not found
+                    }
+                    // For other EACCES/ENOENT on subdirectories, just skip them.
+                    continue;
+                }
+                throw error;
+            }
+            const filesInCurrentDir = [];
+            const subFoldersInCurrentDir = [];
+            // Process files first in the current directory
+            for (const entry of entries) {
+                if (entry.isFile()) {
+                    if (currentItemCount >= options.maxItems) {
+                        folderInfo.hasMoreFiles = true;
+                        break;
+                    }
+                    const fileName = entry.name;
+                    // Skip hidden files, temporary files, and other unwanted files
+                    const filePath = path.join(currentPath, fileName);
+                    if (this.shouldIgnoreFile(fileName, filePath)) {
+                        continue;
+                    }
+                    if (!options.fileIncludePattern ||
+                        options.fileIncludePattern.test(fileName)) {
+                        filesInCurrentDir.push(fileName);
+                        currentItemCount++;
+                        folderInfo.totalFiles++;
+                        folderInfo.totalChildren++;
+                    }
+                }
+            }
+            folderInfo.files = filesInCurrentDir;
+            // Then process directories and queue them
+            for (const entry of entries) {
+                if (entry.isDirectory()) {
+                    // Check if adding this directory ITSELF would meet or exceed maxItems
+                    // (currentItemCount refers to items *already* added before this one)
+                    if (currentItemCount >= options.maxItems) {
+                        folderInfo.hasMoreSubfolders = true;
+                        break; // Already at limit, cannot add this folder or any more
+                    }
+                    // If adding THIS folder makes us hit the limit exactly, and it might have children,
+                    // it's better to show '...' for the parent, unless this is the very last item slot.
+                    // This logic is tricky. Let's try a simpler: if we can't add this item, mark and break.
+                    const subFolderName = entry.name;
+                    const subFolderPath = path.join(currentPath, subFolderName);
+                    // Check if folder should be ignored (built-in ignore list or gitignore)
+                    if (options.ignoredFolders.has(subFolderName) ||
+                        this.shouldIgnoreFile(subFolderName, subFolderPath)) {
+                        const ignoredSubFolder = {
+                            name: subFolderName,
+                            path: subFolderPath,
+                            files: [],
+                            subFolders: [],
+                            totalChildren: 0,
+                            totalFiles: 0,
+                            isIgnored: true,
+                        };
+                        subFoldersInCurrentDir.push(ignoredSubFolder);
+                        currentItemCount++; // Count the ignored folder itself
+                        folderInfo.totalChildren++; // Also counts towards parent's children
+                        continue;
+                    }
+                    const subFolderNode = {
+                        name: subFolderName,
+                        path: subFolderPath,
+                        files: [],
+                        subFolders: [],
+                        totalChildren: 0,
+                        totalFiles: 0,
+                    };
+                    subFoldersInCurrentDir.push(subFolderNode);
+                    currentItemCount++;
+                    folderInfo.totalChildren++; // Counts towards parent's children
+                    // Add to queue for processing its children later
+                    queue.push({ folderInfo: subFolderNode, currentPath: subFolderPath });
+                }
+            }
+            folderInfo.subFolders = subFoldersInCurrentDir;
+        }
+        return rootNode;
+    }
+    /**
+     * Reads the directory structure using BFS, respecting maxItems.
+     * @param node The current node in the reduced structure.
+     * @param indent The current indentation string.
+     * @param isLast Sibling indicator.
+     * @param builder Array to build the string lines.
+     */
+    formatStructure(node, currentIndent, isLastChildOfParent, isProcessingRootNode, builder) {
+        const connector = isLastChildOfParent ? '└───' : '├───';
+        // The root node of the structure (the one passed initially to getFolderStructure)
+        // is not printed with a connector line itself, only its name as a header.
+        // Its children are printed relative to that conceptual root.
+        // Ignored root nodes ARE printed with a connector.
+        if (!isProcessingRootNode || node.isIgnored) {
+            builder.push(`${currentIndent}${connector}${node.name}${path.sep}${node.isIgnored ? TRUNCATION_INDICATOR : ''}`);
+        }
+        // Determine the indent for the children of *this* node.
+        // If *this* node was the root of the whole structure, its children start with no indent before their connectors.
+        // Otherwise, children's indent extends from the current node's indent.
+        const indentForChildren = isProcessingRootNode
+            ? ''
+            : currentIndent + (isLastChildOfParent ? '    ' : '│   ');
+        // Render files of the current node
+        const fileCount = node.files.length;
+        for (let i = 0; i < fileCount; i++) {
+            const isLastFileAmongSiblings = i === fileCount - 1 &&
+                node.subFolders.length === 0 &&
+                !node.hasMoreSubfolders;
+            const fileConnector = isLastFileAmongSiblings ? '└───' : '├───';
+            builder.push(`${indentForChildren}${fileConnector}${node.files[i]}`);
+        }
+        if (node.hasMoreFiles) {
+            const isLastIndicatorAmongSiblings = node.subFolders.length === 0 && !node.hasMoreSubfolders;
+            const fileConnector = isLastIndicatorAmongSiblings ? '└───' : '├───';
+            builder.push(`${indentForChildren}${fileConnector}${TRUNCATION_INDICATOR}`);
+        }
+        // Render subfolders of the current node
+        const subFolderCount = node.subFolders.length;
+        for (let i = 0; i < subFolderCount; i++) {
+            const isLastSubfolderAmongSiblings = i === subFolderCount - 1 && !node.hasMoreSubfolders;
+            // Children are never the root node being processed initially.
+            this.formatStructure(node.subFolders[i], indentForChildren, isLastSubfolderAmongSiblings, false, builder);
+        }
+        if (node.hasMoreSubfolders) {
+            builder.push(`${indentForChildren}└───${TRUNCATION_INDICATOR}`);
+        }
+    }
+}
+exports.DirectoryContextModifier = DirectoryContextModifier;

package/dist/processor-pieces/messageModifiers/environmentContext.d.ts

@@ -0,0 +1,41 @@
+/**
+ * @license
+ * Copyright 2025 Google LLC
+ * SPDX-License-Identifier: Apache-2.0
+ */
+export interface Part {
+    text: string;
+}
+export interface EnvironmentContextOptions {
+    workspaceDirectories: string[];
+    includeFullContext?: boolean;
+    maxItems?: number;
+    ignoredFolders?: Set<string>;
+    fileIncludePattern?: RegExp;
+    respectGitIgnore?: boolean;
+    respectGeminiIgnore?: boolean;
+}
+export interface FolderStructureOptions {
+    maxItems?: number;
+    ignoredFolders?: Set<string>;
+    fileIncludePattern?: RegExp;
+    respectGitIgnore?: boolean;
+    respectGeminiIgnore?: boolean;
+}
+/**
+ * Standalone version of getFolderStructure
+ */
+export declare function getFolderStructure(targetPath: string, options?: FolderStructureOptions): Promise<string>;
+/**
+ * Standalone version of getDirectoryContextString
+ */
+export declare function getDirectoryContextString(workspaceDirectories: string[], options?: FolderStructureOptions): Promise<string>;
+/**
+ * Standalone version of getEnvironmentContext
+ */
+export declare function getEnvironmentContext(options: EnvironmentContextOptions): Promise<Part[]>;
+/**
+ * Utility function to read multiple files (basic implementation for full context)
+ * This is a simplified version - extend as needed for your use case
+ */
+export declare function readMultipleFiles(basePath: string, patterns?: string[], options?: FolderStructureOptions): Promise<string>;