Clarify source and execution directories for Local runs

This commit is contained in:
Scott Werner 2026-10-07 11:12:00 -04:00
parent 19d32c7b87
commit fb79d0bc74

View file

@ -223,13 +223,13 @@ Install seeds a `default` environment into SQLite. It is a normal persisted envi
| `labels` | Warning; ignored | Warning; ignored | Daytona labels |
| `lifecycle.auto_stop` | Warning; ignored | Warning; ignored | Daytona auto-stop |
| `env` | Process environment overlay | Container environment | Sandbox environment |
| `cwd` | Server-side command working directory | Warning; ignored | Warning; ignored |
| `cwd` | Does not override the managed run workspace | Warning; ignored | Warning; ignored |
## Local
`local` runs tools on the Fabro host, in a workspace under the run's directory. It offers no filesystem or network isolation, so use it only for trusted workflows.
Create a server-managed local-provider environment through the environments API when you need a host `cwd`.
Use a folder target to select an existing source directory on the Fabro host.
A version-backed run intent can submit
`{ "kind": "folder", "path": "/absolute/server/path" }` to start from an existing
@ -244,11 +244,9 @@ work in a clone of the folder's committed `HEAD` (see
[Checkpoints](/execution/checkpoints)): retries retain the canonical
folder target, but fork and rewind are unavailable for these runs.
When `cwd` is set, local runs execute commands from that absolute server-side
path. When it is unset, Fabro keeps same-host compatibility by using the
submitted source directory only if that path exists on the server. If neither is
available, the run fails before execution with a remediation to configure
`cwd`.
The folder target identifies the source repository, while commands run in the
managed workspace under the run's directory. Setting an environment's `cwd`
does not make a folder-target run execute in place.
Fabro hard-errors if a local environment asks for blocked or CIDR-restricted networking because the provider cannot enforce it.