The Project work directory is an optional absolute path on the machine where the Bridge runs. It is stored asDocumentation Index
Fetch the complete documentation index at: https://docs.ctrlnode.ai/llms.txt
Use this file to discover all available pages before exploring further.
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 |
- WORK DIRECTORY tasks and the Files → WORKSPACE tab use
{BASE_PATH}/.ctrlnode(Bridge CTRLNODE_ROOT), not the rawBASE_PATHroot. - See Files and Bridge configuration.
How to set the path
- Open Projects (
/projects) → New project or edit an existing project. - Under PROJECT WORK DIRECTORY (optional), use Browse to pick a folder on the Bridge host.
- Confirm with Use this directory in the folder browser (one level at a time).
- Save the project.
/home/you/repos/my-app.
The path must exist on the Bridge machine, not on your browser machine. The Bridge resolves folders via its browse API when connected.
Changing Bridge workspace home
The installer workspace parent folder setsBASE_PATH (where {BASE_PATH}/.ctrlnode lives). To change it, re-run 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 for OUTPUT ONLY vs WORK DIRECTORY