> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ctrlnode.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Project work directory

> Configure repositoryPaths on a project — Files WORKSPACE tab, and WORK DIRECTORY tasks

The **Project work directory** is an optional absolute path on the machine where the **Bridge** runs. It is stored as `repositoryPaths[0]` on the project in the API.

Set it when creating or editing a project (**NEW PROJECT** / **EDIT PROJECT** → field **PROJECT WORK DIRECTORY**).

## Why configure it

| Feature                          | Uses work directory                                                        |
| -------------------------------- | -------------------------------------------------------------------------- |
| Tasks in **WORK DIRECTORY** mode | Agent reads and edits files under this path (or `.ctrlnode` home if unset) |
| **Files** → **WORKSPACE** tab    | Browse and edit files under the project path                               |
| Project list cards               | Shows the path under the CLI badge                                         |

Without a work directory:

* **WORK DIRECTORY** tasks and the **Files → WORKSPACE** tab use **`{BASE_PATH}/.ctrlnode`** (Bridge **CTRLNODE\_ROOT**), not the raw `BASE_PATH` root.
* See [Files](/getting-started/files) and [Bridge configuration](/bridge/configuration).

## How to set the path

1. Open **Projects** (`/projects`) → **New project** or edit an existing project.
2. Under **PROJECT WORK DIRECTORY** (optional), use **Browse** to pick a folder on the Bridge host.
3. Confirm with **Use this directory** in the folder browser (one level at a time).
4. Save the project.

Example path:

```text theme={null}
C:\CODE\2026\CtrlNode\src\CtrlNode.Web
```

On Linux/macOS, use an absolute path such as `/home/you/repos/my-app`.

<Note>
  The path must exist on the **Bridge machine**, not on your browser machine. The Bridge resolves folders via its browse API when connected.
</Note>

## Changing Bridge workspace home

The installer **workspace parent folder** sets `BASE_PATH` (where `{BASE_PATH}/.ctrlnode` lives). To change it, re-run [install](/bridge/install) and restart **`ctrlnode`**.

The **project work directory** is independent: it should usually be a **subfolder** under or beside that home, pointing at your real git checkout.

## Task work modes

Work directory settings apply when a task uses **WORK DIRECTORY** mode:

* Agent can modify the full tree (or selected **focus paths**)
* See [Task work modes](/tasks/create-task) for OUTPUT ONLY vs WORK DIRECTORY

## API

```json theme={null}
{
  "repositoryPaths": ["C:\\CODE\\2026\\CtrlNode\\src\\CtrlNode.Web"]
}
```

Empty array or omitted path means no project-specific directory.

## Related

* [Projects overview](/projects/overview)
* [Files](/getting-started/files)
* [Task work modes](/tasks/create-task)
* [Bridge overview](/bridge/overview)