Link

Documentation Index

Fetch the complete documentation index at: https://docs.envless.cloud/llms.txt

Use this file to discover all available pages before exploring further.

​

Usage

envless link

Walks an interactive picker: choose a workspace, then a project, then one or more environments. The selection is written to a .envless file at the repo root so subsequent commands know what to sync.

If .envless already exists, link reads it and pre-selects your current values in the picker — you can press enter to keep them or arrow-key to a different one. There’s no separate “re-link” command; running envless link again is how you change the binding.

​

Non-interactive

Skip the prompts by passing slugs (or unique IDs) directly.

envless link --workspace acme --project my-app --env development

Pass multiple environments by comma-separating them:

envless link --workspace acme --project my-app --env development,staging

If any identifier doesn’t resolve, the CLI errors out and exits with code 1. Both slugs and unique IDs are accepted on every flag.

​

The .envless file

The link command creates a small JSON file that pins the directory to a workspace, project, and a set of environments. Commit it — it contains no secrets, only slugs.

{
    "workspace": "acme",
    "project": "my-app",
    "environments": ["development"]
}

environments is always an array, even with a single environment, so the file shape doesn’t change when you add more later.

​

Flags

​

Requirements

You must be signed in (envless login) before running link. If you only have one workspace, the picker is skipped automatically.