--- metadata: - name: generator content: Diplodoc Platform v5.50.6 alternate: - https://sourcecraft.dev/portal/docs/en/code-assistant/operations/agent/auto-approving-actions.md - https://sourcecraft.dev/portal/docs/ru/code-assistant/operations/agent/auto-approving-actions.md title: Auto-approving actions in SourceCraft Code Assistant description: How to configure auto-approval of actions in SourceCraft Code Assistant for faster Visual Studio Code workflow --- > **Documentation Index:** Fetch the complete configuration index at https://sourcecraft.dev/portal/docs/en/llms.txt # Auto-approving actions in SourceCraft Code Assistant {% note warning %} This feature is only available in Visual Studio Code. {% endnote %} _Auto-approval of actions_ accelerates your workflow by eliminating repetitive confirmation prompts but also significantly increases security risks. {% note alert %} Auto-approval settings bypass confirmation requests, granting Code Assistant direct access to your system, which could lead to data loss, file corruption, or even greater damage. Terminal access involves most risks, as Code Assistant may run potentially malicious operations that interfere with your system or compromise security. Only enable auto-approval for actions you deem fully credible. {% endnote %} ## Quick start {#quick-start} 1. Click the **Auto-approve** panel in the chat toolbar. 1. Select which actions Code Assistant can perform without requesting permission. 1. Use the toggle to the left of **Auto-approve** to quickly enable or disable permissions. ### API request limit {#api-request-limit} In the **Auto-approve** settings, use the **Max Requests** input field to set the maximum number of API requests Code Assistant can execute automatically. This helps prevent excessive API usage and unforeseen costs, e.g., when using high-priced models, testing new workflows, or running Code Assistant autonomously for extended periods. By default, no limit is set. {% note tip %} Set a reasonable limit based on task complexity; e.g., 50 to 100 requests is sufficient for most tasks. {% endnote %} When the limit is exceeded, Code Assistant stops and displays a dialog allowing you to reset the counter and continue. ### Available permissions {#available-permissions} | Permission | Description | Risk level | | --- | --- | --- | | **Read** | Allows Code Assistant to access files without requesting approval | Medium | | **Write** | Allows Code Assistant to modify files without requesting approval | **High** | | **Execute** | Automatically runs terminal commands from the whitelist | **High** | | **Browser** | Allows access to the browser without requesting approval | Medium | | **MCP** | Allows Code Assistant to use configured [MCP servers](./mcp/overview.md) | Medium to high | | **Mode** | Automatically switches [Code Assistant modes](../chat-prompts.md) | Low | | **Subtasks** | Manages subtasks without requesting confirmation | Low | | **Retry** | Automatically retries failed API requests | Low | ### Quickly enabling or disabling permissions {#enable-disable-permissions} 1. Click the **Auto-approve** panel in the chat toolbar. 1. Select which actions Code Assistant can perform without requesting permission. 1. Use the toggle to the left of **Auto-approve** to quickly enable or disable permissions. Permission settings are preserved when toggling. For example, you can quickly disable auto-approval when working with sensitive code or enable it when rapidly iterating on a code change. This is also helpful when switching between code analysis and editing. {% note info %} Opening the **Auto-approve** menu temporarily disables auto-approval. {% endnote %} ## Advanced settings panel {#advanced-settings} 1. In the chat's top panel, click **Settings**. 1. In the left-hand panel, navigate to **Auto-approve**. 1. Select which actions Code Assistant can perform without requesting permission: * [Read](#read) * [Write](#write) * [Browser](#browser) * [Retry](#retry) * [MCP](#mcp) * [Mode](#mode) * [Subtasks](#subtasks) * [Execute](#execute) ### Read {#read} When enabled, Code Assistant automatically scans directory contents and reads files without prompting you to click **Approve**. _Risk: medium._ The additional **Include files outside workspace** option allows Code Assistant to read files you have access to outside the current working directory. _Risk: medium._ Although this setting only allows reading (not modifying) files, it could potentially expose sensitive data. We recommend this practice as a starting point for most users; yet, be mindful of which files Code Assistant can access. This option is disabled by default, i.e., Code Assistant can only read files within your current working directory. {% note tip %} Keep **Include files outside workspace** disabled unless you specifically need to grant access to external files. {% endnote %} ### Write {#write} When enabled, Code Assistant automatically creates and edits files without prompting you to click **Approve**. _Risk: high._ Additional options: * **Include files outside workspace**: Allows Code Assistant to modify files you have access to outside the current working directory. * **Include protected files**: Allows Code Assistant to modify files normally protected by `.codeassistantignore` and the `.codeassistant/` directory, as well as Code Assistant configuration files, e.g., `package.json`, `tsconfig.json`, etc., if they contain Code Assistant settings. * **Delay after writes**: Introduces a delay after writes to diagnose potential issues: * `1000 ms`: Default value, suitable for most projects with active diagnostics. * `2000 ms or more`: Recommended for complex projects where diagnostics take longer. * `0 ms`: Use when speed is critical. * `1000 ms`: Use only in controlled environments. When you enable auto-approval for file writes, the delay timer integrates with the **Problems** panel in VS Code: 1. Code Assistant makes changes in your file. 1. VS Code diagnostic tools analyze the changes. 1. The **Problems** panel updates with any errors or warnings. 1. Code Assistant detects these issues before proceeding. This brings a pause for the developer to review errors after code changes. You can adjust the delay based on: * Project complexity. * Language server performance. * Criticality of error detection for your workflow. ### Browser {#browser} When enabled, Code Assistant automatically performs browser actions without prompting you to click **Approve**, including opening websites, navigating pages, and interacting with web elements. _Risk: medium._ {% note info %} This setting only applies if supported by the AI model. {% endnote %} ### Retry {#retry} When enabled, Code Assistant automatically retries failed API requests without prompting you to click **Approve** if the server returns an error. _Risk: low._ The additional **Delay before retrying the request** option sets the wait time before a retry attempt. The default value is 10 seconds. The retry mechanism uses exponential backoff: * The **Delay before retrying the request** value is the initial delay. * Subsequent delays follow this formula: `min(baseDelay * 2^retryAttempt, 600)`. * The maximum delay is 600 seconds. > Here is an example retry sequence with an initial delay of ten seconds: > * Retry 1: 10 seconds > * Retry 2: 20 seconds > * Retry 3: 40 seconds > * Retry 4: 80 seconds > * Retry 5: 160 seconds > * Retry 6: 320 seconds > * Retry 7 and subsequent retries: 600 seconds This helps prevent API overload while recovering from transient errors. ### MCP {#mcp} When enabled, Code Assistant automatically uses individual tools from configured [MCP servers](https://sourcecraft.dev/portal/docs/en/code-assistant/operations/agent/mcp/overview.md) without prompting you to click **Approve**. _Risk: medium to high depending on configured MCP tools._ For security, this setting requires two-step approval: 1. On the **Auto-approve** panel, enable **MCP**. 1. Expand the required MCP server's menu and select the **Auto-Run** option for the relevant tools. The system will save your permissions and apply them the next time Code Assistant uses MCP tools. ### Mode {#mode} When enabled, Code Assistant automatically switches between different [modes](https://sourcecraft.dev/portal/docs/en/code-assistant/operations/chat-prompts.md) without prompting you to click **Approve**. _Risk: low._ ### Subtasks {#subtasks} When enabled, Code Assistant automatically creates and completes subtasks without prompting you to click **Approve**. _Risk: low._ ### Execute {#execute} When enabled, Code Assistant automatically runs allowed terminal commands without prompting you to click **Approve**. _Risk: high._ Under **Allowed Auto-Execute Commands**, add the prefix of a command you want to auto-execute and click **Add**. Repeat this for all commands you want to run automatically. Add the `*` prefix to allow all commands (use this with extreme caution). To remove a command prefix, click to its right. {% note tip %} * Use a whitelist with specific command prefixes. * Never use the `*` prefix in production environments or when handling sensitive data. * Carefully evaluate the security implications of each command you allow. * Always review commands that interact with external systems. * Be very specific with prefixes, e.g., instead of allowing all `python` commands, restrict to `python -m pytest` for test execution only. {% endnote %} > Here is an example of a command whitelist: > * `git`: Running version control operations. > * `npm run`: Running scripts from `package.json`. > * `python -m pytest`: Running Python tests. > * `cargo test`: Running Rust tests. > * `go test`: Running Go tests. > * `docker ps`: Listing Docker containers. > * `ls`: Listing directory contents. > * `cat`: Displaying file contents.