---
title: "lanes in config.yaml"
url: https://devlanes.run/docs/reference/config/user/lanes/
description: "Reference for the lanes key in ~/.devlanes/config.yaml."
---

# lanes in config.yaml

A top-level key of [`~/.devlanes/config.yaml`](/docs/reference/config/user/).

## `lanes`

Type: mapping.

Where lane data folders (`lane.data_path`) live on this machine, and how long a lane may sit without activity before devlanes throttles or freezes it.

```yaml devlanes-user
lanes:
  data_dir: ~/.devlanes/data
```

### `lanes.data_dir`

Type: string.

Folder that holds every lane's data folder, one subfolder per project; defaults to `data` in the devlanes home (`~/.devlanes/data`). Must be an absolute path or start with `~/`. The daemon reads it when it starts. After a change and a daemon restart, lanes use new, empty folders under the new root; move the old folders there by hand to keep their data.

```yaml devlanes-user
lanes:
  data_dir: ~/.devlanes/data
```

### `lanes.freeze_after`

Type: [duration](/docs/reference/config/#durations). Default: `15m`.

After this long without activity, devlanes freezes a lane: it suspends every process of the lane and pauses the lane's own containers. Shared infra is never paused. Ports and process state are kept, so a frozen lane still counts as running. A request through the proxy, a new connection to one of the lane's ports, or a devlanes command on the lane resumes a frozen lane and restarts the timer. The lane's services using CPU keep a running lane from freezing, but cannot resume a frozen one, since its processes are suspended. A request through the proxy resumes the lane at once and then goes through; a direct connection to a port is noticed within about half a second. When both are set above `0s`, it must be longer than `throttle_after` (`5m` unless set). A running service with `services.<name>.keep_awake: true` keeps its whole lane awake. Defaults to `15m`; `0s` turns freezing off. The daemon reads it when it starts.

```yaml devlanes-user
lanes:
  freeze_after: 15m
```

### `lanes.throttle_after`

Type: [duration](/docs/reference/config/#durations). Default: `5m`.

After this long without activity, a lane's processes run at background priority: lower CPU priority, and efficiency cores on machines that have them. They keep serving requests. Activity is a request through the proxy, a new connection to one of the lane's ports, the lane's services using CPU, or a devlanes command on the lane; any of it restores normal priority and restarts the timer. macOS and Windows only; Linux has no throttling, so lanes there stay at normal priority until `freeze_after`. When both are set above `0s`, it must be shorter than `freeze_after`. A running service with `services.<name>.keep_awake: true` keeps its whole lane at normal priority. Defaults to `5m`; `0s` turns throttling off. The daemon reads it when it starts.

```yaml devlanes-user
lanes:
  throttle_after: 5m
```
