Link & status

link

The edge link command writes a .edge.json file in the current directory. Any edge command run inside that directory tree automatically picks up the linked workspace, project, and environment — without needing flags or a globally active context.

edge link [--workspace <slug>] [--project <slug>] [--env <slug>]

How it works

edge link writes .edge.json in your current working directory:

{
  "workspace": "acme-corp",
  "project": "payments",
  "env": "production"
}

When you run any edge command, the CLI walks up the directory tree from cwd looking for this file. The first one found wins. This means you can have different link files in different subdirectories with different contexts.

Interactive usage

Run edge link with no flags and the CLI will prompt for each value. Existing global context is used as a default:

cd ~/code/payments-api
edge link
# Workspace slug: acme-corp
# Project slug: payments
# Environment slug: production
# ✓ Linked to workspace=acme-corp project=payments env=production

Flags

Flag	Description
`--workspace`	Workspace slug
`--project`	Project slug
`--env`	Environment slug

Non-interactive usage

Pass all values as flags to skip prompts (e.g. in setup scripts):

edge link --workspace acme-corp --project payments --env production

Unlinking

Delete the .edge.json file to remove the link:

rm .edge.json

status

Show the current resolved context — including which token is active, the API URL, and the workspace/project/environment with the source of each value.

edge status
edge status --json

Example output

SETTING      VALUE                            SOURCE
Auth         authenticated                    CLOUD_TOKEN env var
API URL      https://api.cloud.simplifyd.com  config
Workspace    acme-corp                        .edge.json
Project      payments                         .edge.json
Environment  production                       .edge.json

Sources explained:

Source	Meaning
`CLOUD_TOKEN env var`	Token from the `CLOUD_TOKEN` environment variable
`~/.simplifyd/config.json`	Value from the global config file
`.edge.json`	Value from the nearest `.edge.json` link file
`-`	Not set

JSON output

edge status --json

{
  "auth": "authenticated",
  "api_url": "https://api.cloud.simplifyd.com",
  "active_workspace": "acme-corp",
  "active_project": "payments",
  "active_env": "production",
  "link_workspace": "acme-corp",
  "link_project": "payments",
  "link_env": "production"
}

Link & status

On this page