---
title: "Configuration"
description: "Learn how to configure project-specific properties when working with Local Platform."
canonical: https://www.quantconnect.com/docs/v2/local-platform/development-environment/configuration
markdown: https://www.quantconnect.com/docs/v2/local-platform/development-environment/configuration.md
language: python
source: https://github.com/QuantConnect/Documentation/tree/master/02%20Local%20Platform/04%20Development%20Environment/05%20Configuration
modified: 2026-10-29
index: https://www.quantconnect.com/llms.txt
---

# Configuration

[Documentation](https://www.quantconnect.com/docs/v2.md) > [Local Platform](https://www.quantconnect.com/docs/v2/local-platform.md) > Development Environment > Configuration

> Code examples are shown in Python. Append `?lang=csharp` to this URL for the C# version of this page.

## Introduction

The Local Platform is configured by extension settings in VS Code and by the LEAN Engine settings. Change these settings at any time to suit your needs.

## Extension Settings

Follow these steps to view the settings of the Local Platform extension:

1. Open VS Code.
2. In the top navigation bar, click **File > Preferences > Settings**.
3. On the Settings page, in the left navigation menu, click **Extensions > QuantConnect**.

The following table describes each setting:

| Name | Description |
| --- | --- |
| Executable Path: Docker | A path to the Docker installation you want to use. |
| Executable Path: Lean | A path to the LEAN CLI executable you want to use. |
| Lean: Init | A path to the current organization workspace. |
| Sync: Local And Cloud Projects | The synchronization mode for your local and cloud projects. **Synchronize All Projects** (default): While the extension runs, it synchronizes all your cloud and local projects in the background. **Synchronize Open Project Only**: The extension only synchronizes the project you currently have open. **Disable Synchronization**: The extension doesn't synchronize any projects. This mode is best when local agents edit your project files and you want to avoid conflicts with the cloud versions of your projects. |
| User: Preferred Language | The programming language to use when creating new projects. **Py** for Python or **C#** for C#. |

## LEAN Settings

The Lean configuration contains settings for locally running the LEAN engine. This configuration is created in the `lean.json` file when you pull or create an [organization workspace](https://www.quantconnect.com/docs/v2/local-platform/development-environment/organization-workspaces.md). The configuration is stored as JSON, with support for both single-line and multiline comments.

The Lean configuration file is based on the [Launcher / config.json](https://github.com/QuantConnect/Lean/blob/master/Launcher/config.json) file from the Lean GitHub repository. When you pull or create an organization workspace, the latest version of this file is downloaded and stored in your organization workspace. Before the file is stored, some properties are automatically removed because the Local Platform automatically sets them.

The Local Platform can update most of the values of the `lean.json` file. The following table shows the configuration settings that you need to manually adjust in the `lean.json` file if you want to change their values:

| Name | Description | Default |
| --- | --- | --- |
| `show-missing-data-logs` | Log missing data files. This is useful for debugging. | true |
| `initialization-timeout` | The maximum amount of time, in seconds, the algorithm can spend in the [initialization](https://www.quantconnect.com/docs/v2/writing-algorithms/initialization.md) phase. | 300 |
| `algorithm-manager-time-loop-maximum` | The maximum amount of time, in minutes, the algorithm can spend in a single [time loop](https://www.quantconnect.com/docs/v2/writing-algorithms/key-concepts/time-modeling/timeslices.md). | 20 |
| `maximum-warmup-history-days-look-back` | The maximum number of days of data the history provider will provide during [warm-up](https://www.quantconnect.com/docs/v2/writing-algorithms/historical-data/warm-up-periods.md) in live trading. The history provider expects older data to be on disk. | 5 |
| `maximum-chart-series` | The maximum number of chart series you can create in backtests. | 30 |
| `maximum-data-points-per-chart-series` | The maximum number of data points you can add to a chart series in backtests. | 1,000,000 |
| `data-monitor-store-succeeded-requests` | Save the paths of the data files that LEAN loads during a backtest to a `succeeded-data-requests` file in the backtest results. | false |