Local Environment Files

Shared Ghostable environments are encrypted repository state. A local .env file is plaintext on one machine. Desktop connects these stores through explicit actions; it does not make a local file safe to commit.

Use Compare Environments to inspect key and value differences before copying state. A comparison is read-only: it helps you identify missing, changed, or extra keys without mutating either side.

Compare first when promoting configuration between development, staging, and production. Environment types and access policy still apply to the destination.

Pull Local File writes the selected shared environment into a plaintext file inside the repository. Choose the target path carefully and preview the operation when offered.

1. Select the source shared environment.
2. Open environment actions and choose Pull Local File.
3. Confirm the path and review the planned keys.
4. Write the file, then verify permissions and Git ignore status.

Pull only when a framework or tool actually requires a file. Prefer direct process injection through the CLI when no file is necessary.

Push Local File reads a plaintext file and updates the selected encrypted environment. It can change multiple values at once, so compare and inspect the destination before confirming.

Sync Local File reconciles the configured local file and shared environment according to the action's preview. Treat sync as a write operation, not background magic: inspect additions, updates, removals, and commented keys before continuing.

When the local and shared versions both changed, stop and decide which value is authoritative. Desktop cannot infer team intent from two valid values.