Bind a target. Keep authority upstream.
Four configuration values identify one existing sandbox and its canonical owner record. None of them authorizes access.
The four binding values
| Variable | Value |
|---|---|
CASTLES_PROFILE | The supported profile: castles.daytona-private-linux.v1. |
CASTLES_SANDBOX_ID | Exact ID of the one existing sandbox; never a name or label. |
CASTLES_OWNER_AGENT_ID | The canonical Coven Agents record that owns the sandbox. |
CASTLES_SANDBOX_GENERATION | The expected generation recorded on that owner record. |
See .env.example for placeholders. Do not put real identifiers in commits, issues, test fixtures or shared logs.
Environment and local file
Without --fixture, the CLI reads exported variables and an optional .env.local from its current working directory. Exported values win. The package script runs from the package root.
Node loads every key in that file into the process environment, although Castles consumes only the four binding keys. Keep the file limited to the binding. With --fixture, both binding and inspection input come from the synthetic case instead.
Credentials stay with the owning service
Castles does not consume provider, database or harness credentials. Those belong to the canonical owning service and its existing custody flow. The sandbox ID and owner record ID are targets, not secrets that grant authority.
Do not add credentials to this documentation site, its browser, fixture files or the guest sandbox. No deployment environment variable is needed to build or serve these docs.
Current non-fixture behavior
Invalid bindings are rejected before inspection. A future live window requires an accepted upstream capability and explicit authorization; the current website deployment grants neither.