Skip to main content
Create a standalone task from the project Tasks board or list. Route: /projects/{projectId}/tasks/new In the app: + New task on the Kanban or list view. You can also open create from a workflow designer step (New task on a stage); saving returns you to the designer when from=pipeline-designer is in the URL.

​
Form fields

After Create, you land on task detail in Backlog (or return to the workflow designer when applicable).

​
Work mode (MODE)

The MODE chips control where the agent may read and write files on the Bridge host. This is set at create time (the same control appears when editing a task in Backlog before dispatch).

​
The MODE control

​
OUTPUT ONLY (default)

Stored as: task_mode = output Help text in the app:
Default: deliverables go to this task’s isolated output folder under .ctrlnode. Uploaded Inputs are attachments for context.

​
WORK DIRECTORY

Stored as: task_mode = repo The agent can read and change files across the full directory configured for the project — not only uploaded inputs.

​
Scope panel

A green-bordered panel shows either: If no project work directory is configured:
No project work directory set — using the Bridge workspace root. Set one in project settings to scope tasks to a subfolder.
Configure the path in Project work directory.

​
Focus paths (optional)

You can also describe paths in Instructions for soft guidance.
WORK DIRECTORY lets the agent modify real project files. Prefer OUTPUT ONLY when you only need deliverables in the task folder or the prompt is not fully trusted.

​
How it reaches the Bridge

  1. CtrlNode saves task_mode and focus_files on the task.
  2. On dispatch, the API sends repositoryPaths and focus paths when applicable.
  3. The Bridge builds repo dispatch context for every provider.
Bridge must be connected to resolve BRIDGE WORKSPACE HOME when the project has no work directory.

​
Quick comparison

Task detail

After create — instructions, artifacts, agent activity.

Project work directory

Path used by WORK DIRECTORY mode.