Skip to content
d_devboxby 508.dev/ DocumentationDashboard ↗
Browse documentation
DOCUMENTATION / Secrets & environment

Secrets and environment variables

Keep authentication at its owning boundary. Installing a client or creating a worktree must not silently grant credentials to a remote process.

Vendor sign-in stays on the host

Authenticate Claude, Codex and other vendor tools through their supported CLI flows in the host account. Devbox never copies a laptop credential store, SSH private key, GitHub App private key or refresh token to the host.

Using a subscription depends on the vendor's supported product and organization settings. Devbox does not bypass those terms or own the vendor's sign-in process.

Repository transfer is not secret sync

Ignored files such as local .env files are excluded from setup. Credential-like tracked filenames and included history are refused conservatively. This is not a content secret scanner: review repository history yourself.

Provision development secrets on the host through your normal secret manager or carefully managed private files. Never bake them into a shared machine image.

Process environments

An environment variable affects a process when it starts. Editing a file does not update an already-running tmux session, agent or development server. Restart the specific process deliberately after a change.

Discovery reads metadata only. Watching a workspace does not execute its setup scripts, source .env, evaluate shell hooks or authorize secret inheritance.

CLI credentials

Linux desktop credentials use the system secret service when available. Headless or unsupported keyring platforms require explicit --allow-private-file for a private-file fallback. Saved relay credentials are scoped by origin and computer, separately from account credentials.

Planned environment profiles

Project/workspace environment-profile editing, provider integrations and materialization remain design work. They are not a shipped hosted secrets manager. Do not build an onboarding dependency on them yet.

Worktrees sharing one Unix account share its privileges. For secrets that must be isolated from an untrusted workload, use a separate account or machine with an explicit boundary.

Development machines. Your code. Your control.
Private pilot · Feature availability is called out in each guide.