Variables

Every environment variable the workspace's crates define, modules, packages and contracts alike, from their variables.toml, by the crate defining it, and each namespace a crate computes names in. A runtime flag may name one to read when it is absent, as its command's reference says, and a spec field never reads one.

Defined

Each variable with its type, its default, and the crate defining it.

  • ALL_PROXY, string, from core: This machine's proxy for every protocol, which Link hands the programs it installs and runs
  • AWS_RESPONSE_CHECKSUM_VALIDATION, string, from core: When AWS's libraries check a response's checksum, which Link sets for rclone's run against a bucket that doesn't send one
  • CLICOLOR_FORCE, string, from core: Set: colors even in a pipe or a file.
  • COLUMNS, string, from core: Your terminal's width, where Link can't ask the terminal.
  • DBUS_SESSION_BUS_ADDRESS, string, from core: Your desktop's bus, which a sandbox opens only when its spec grants the desktop.
  • DISPLAY, string, from core: Your X11 desktop, which a sandbox opens only when its spec grants the desktop.
  • GIT_TERMINAL_PROMPT, string, from core: Whether git may ask in a terminal for a credential: 0 keeps it from asking, as Link sets it for a git it runs alone.
  • GOOGLE_APPLICATION_CREDENTIALS, string, from core: The key file a program using Google Cloud's libraries signs in with, which Link passes on only to a cloud's own run
  • HOME, string, from core: Must be absolute, or commands that delete or trust a folder refuse.
  • HOSTNAME, string, from core: This machine's name, where the system doesn't give one: scrubbed from reports.
  • HTTPS_PROXY, string, from core: This machine's HTTPS proxy, which Link hands the programs it installs and runs
  • HTTP_PROXY, string, from core: This machine's HTTP proxy, which Link hands the programs it installs and runs
  • LANG, string, from core: Your locale, kept for programs Link runs.
  • LNK_CORE, string, from core: A core program a test runs in place of the one built beside it, for tests
  • LNK_EXE, string, from core: The lnk that started a module, which it runs for other commands.
  • LNK_GITHUB_URL, string, from core: Where a module from outside Link is read from in place of https://github.com (tests): a location of the kinds LNK_RELEASES_URL takes, holding each repository's releases at <owner>/<repo>/releases/latest/download. Its pinned key is still checked.
  • LNK_INSECURE, string, from core: 1: install without ssh-keygen, so without checking the signature.
  • LNK_INSTALL_DIR, string, from core: Where lnk goes; modules go next to it.
  • LNK_MACHINE_DIR, string, from core: This machine's folder [default: ~/.lnk], for one process and what it runs: a sandbox's session whose settings can't be in the folder it writes. A relative value is ignored.
  • LNK_MODULES, string, from core: The module listing (lnk module list --json) lnk hands the module it runs, for that process alone, so its questions start no other lnk.
  • LNK_NO_BROWSER, string, from core: Set to open no browser: a command that would open a page, such as lnk issue create or lnk agent connect, prints its address instead
  • LNK_RELEASES_URL, string, from core: Where releases are read from (tests, staging and dev builds). Signatures remain required. An HTTPS address with no login, backslash, query or fragment, a bucket of yours (s3:/// or gs:///, read with that cloud's CLI and your login) or a folder here (file:///); debug builds also accept HTTP on this machine.
  • LNK_TEST_RELEASE_SIGNERS, string, from core: An allowed-signers file whose keys are trusted beside the built-in release signer (tests). Only debug builds read it.
  • LNK_UPDATE_NOTICE, string, from core: off: commands never check for or announce a newer release.
  • LNK_VERSION, string, from core: The release version to install, such as 0.14.0. A released lnk refuses a version older than itself.
  • LOGNAME, string, from core: Who you are, where USER isn't set: kept for programs Link runs, and scrubbed from reports.
  • NODE_EXTRA_CA_CERTS, string, from core: Certificates Node.js trusts besides its own
  • NODE_USE_ENV_PROXY, string, from core: Node.js's switch to send its requests through HTTPS_PROXY, set to 1 for a program Link runs in Node
  • NO_COLOR, string, from core: Set: no colors. Colors show only on a terminal.
  • NO_PROXY, string, from core: The hosts this machine reaches without its proxy
  • PATH, string, from core: Where Link finds the programs it runs, and the modules beside lnk.
  • PLAYWRIGHT_BROWSERS_PATH, string, from core: Where Playwright keeps the browsers it installs
  • SHELL, string, from core: Your shell, which a box opened here runs.
  • SSH_CONNECTION, string, from core: Set over SSH: sign-ins print their address instead of opening a browser.
  • SSH_TTY, string, from core: Set over SSH: sign-ins print their address instead of opening a browser.
  • SSL_CERT_FILE, string, from core: The certificates this machine trusts, as OpenSSL and the programs built on it read them
  • TERM, string, from core: Your terminal's kind, kept for programs Link runs.
  • TMPDIR, string, from core: Where programs Link runs keep temporary files.
  • TZ, string, from core: The time zone a program reports its times in
  • USER, string, from core: Who you are: named in a box's or a service's unit, kept for programs Link runs, and scrubbed from reports.
  • WAYLAND_DISPLAY, string, from core: Your Wayland desktop, which a sandbox opens only when its spec grants the desktop.
  • XDG_CONFIG_HOME, string, from core: Your settings folder (Linux) [default: ~/.config]: where services' units and programs' dot files are.
  • XDG_RUNTIME_DIR, string, from core: Your runtime folder (Linux), where Link's sockets and services live.
  • all_proxy, string, from core: ALL_PROXY as some programs spell it
  • http_proxy, string, from core: HTTP_PROXY as some programs spell it
  • https_proxy, string, from core: HTTPS_PROXY as some programs spell it
  • no_proxy, string, from core: NO_PROXY as some programs spell it
  • npm_config_https_proxy, string, from core: npm's HTTPS proxy
  • npm_config_noproxy, string, from core: The hosts npm reaches without its proxy
  • LNK_ASKER_BUILT_FROM, string, from link-core: The commit the program asking a question was built from, handed to the module answering it, which refuses the question when it was built from another.
  • LNK_BUILD, string, from link-core: The build a program is compiled as: dev, staging or prod, set by lnk bundle create as it compiles a bundle's programs and read as each is compiled. Left out, a build from source.
  • LNK_DEV_SIGNER, string, from link-core: The allowed-signers line of the key a dev build is signed with, which lnk bundle create --build dev derives from your signer and a dev build reads as it's compiled, refusing to compile without it.
  • LNK_PROD_SIGNER, string, from link-core: The allowed-signers line of the signer a prod build is signed with, which lnk bundle derives from the bundle's signer and a prod build reads as it's compiled, trusting it alone.
  • LNK_DISCORD_API, string, from discord: Discord's HTTP API, for tests; the Gateway's address comes from it
  • LNK_DISCORD_TOKEN, string, carries the secret discord.bot_token, from discord: The Discord bot's token, read by connect, which asks for it when it's unset
  • LNK_SIGNAL_CLI, string, from signal: On Link Harness, a signal-cli of your own to carry Signal with, for tests; the account stays in ~/.lnk/safe/agents/<agent>/connections/signal
  • LNK_SIGNAL_NUMBER, string, from signal: The agent's Signal number, with its country code, not yours; connect asks for it when it's unset
  • LNK_SIGNAL_OWNER, string, from signal: Your Signal number, with its country code, not the agent's; connect asks for it when it's unset
  • LNK_SLACK_API, string, from slack: Slack's Web API, for tests
  • LNK_SLACK_APP_TOKEN, string, carries the secret slack.app_token, from slack: The app-level token (xapp-...), with the bot token or neither, read by connect, which asks for it when it's unset
  • LNK_SLACK_BOT_TOKEN, string, carries the secret slack.bot_token, from slack: The bot token (xoxb-...), with the app token or neither, read by connect, which asks for it when it's unset
  • LNK_TELEGRAM_API, string, from telegram: Telegram's Bot API, for tests
  • LNK_TELEGRAM_TOKEN, string, carries the secret telegram.bot_token, from telegram: The bot token from BotFather, read by connect, which asks for it when it's unset; no flag takes a connection's token
  • LNK_MODEL_CREDENTIAL, string, from deepseek: The model's key in dsh's .env, which its provider reads by name
  • npm_config_cache, string, from deepseek: npm's cache folder, which a harness's install gives npm inside the harness's home, never the machine user's.
  • npm_config_update_notifier, string, from deepseek: Whether npm checks for a newer npm: false in a harness's install, so npm never checks for its own updates.
  • HERMES_HOME, string, from hermes: Where Hermes keeps its configuration and state: the agent's own folder, given to each Hermes process it runs.
  • LNK_HERMES_MANAGED_GATEWAY, string, from hermes: Set to 1 in the Hermes gateway Link starts, so its workarounds know Link manages it
  • LNK_HERMES_MODEL_URL, string, from hermes: The model's address in Hermes's config.yaml, reached through Link's proxy with the proxy's secret in it
  • LNK_OPENCLAW_GATEWAY_TOKEN, string, from openclaw: The OpenClaw gateway's token, kept in its .env and read back from it
  • LNK_OPENCLAW_MODEL_URL, string, from openclaw: The model's address in an OpenClaw provider's entry, reached through Link's proxy with the proxy's secret in it
  • NODE_OPTIONS, string, from openclaw: Node.js's options, which OpenClaw's gateway is started with, with Link's own added
  • OPENCLAW_HOME, string, from openclaw: Where OpenClaw keeps its configuration and state, which OpenClaw's processes never inherit: Link names their folders itself.
  • LNK_*, a namespace, from aws: CLI test overrides: append the uppercase program name (such as AWS) to LNK_ when selecting the external AWS CLI.
  • LNK_*, a namespace, from gcp: CLI test overrides: append the uppercase program name (such as GCLOUD or GSUTIL) to LNK_ when selecting the external Google Cloud CLI.
  • ANTHROPIC_API_KEY, string, from agent: The provider's own key variable, read by lnk agent start, create, move and model set: no flag takes a key. With no model yet, the one that is set (several set: refused, to unset all but one); with a hosted model, its provider's, to renew the key; with --model, the provider its name says; with a model on this computer, one that is set is asked about in a terminal (switch to that provider?), else said. Never passed to a harness or to a box.
  • CURL_CA_BUNDLE, string, from agent: Certificates curl trusts, which a harness's installer is given.
  • LNK_AGENT, string, from agent: The agent's name, for harness programs.
  • LNK_AGENT_FOLDER, string, from agent: The agent's own folder (~/Link/Agents/<name>/agent), for a harness that keeps Link's collections (Link Harness): each one kept at file a folder of it.
  • LNK_AGENT_ID, string, from agent: The agent's ID, for harness programs.
  • LNK_AGENT_SERVICE, string, from agent: The service the agent acts as, its bare ID, for harness programs: what its bridge calls prove beside its ID.
  • LNK_FALLBACK_CREDENTIAL, string, from agent: The fallback's key on lnk agent start --model.fallback_model, read before its provider's own variable.
  • LNK_FILES, string, from agent: The agent's Home, its files folder, for harness programs.
  • LNK_MEASURES, string, from agent: For harness programs: the file in the harness's home it may append its own measures to, as OTLP (.lnk/safe/measures/measures.jsonl), which lnk measure reads.
  • LNK_OWNER, string, from agent: The agent's owner, for harness programs.
  • LNK_PORT, string, from agent: The agent's base port, for harness programs: every agent's own.
  • LNK_TEST_BRIDGE_NONE_FOR_MS, string, from agent: Debug builds only: milliseconds an empty shared bridge waits before it stops.
  • LNK_TEST_MIGRATE_STOP, string, from agent: Debug builds only: stop migration before this numbered step so recovery can be tested.
  • OPENAI_API_KEY, string, from agent: The provider's own key variable, read by lnk agent start, create, move and model set: no flag takes a key. With no model yet, the one that is set (several set: refused, to unset all but one); with a hosted model, its provider's, to renew the key; with --model, the provider its name says; with a model on this computer, one that is set is asked about in a terminal (switch to that provider?), else said. Never passed to a harness or to a box.
  • OPENROUTER_API_KEY, string, from agent: The provider's own key variable, read by lnk agent start, create, move and model set: no flag takes a key. With no model yet, the one that is set (several set: refused, to unset all but one); with a hosted model, its provider's, to renew the key; with --model, the provider its name says; with a model on this computer, one that is set is asked about in a terminal (switch to that provider?), else said. Never passed to a harness or to a box.
  • PIP_CERT, string, from agent: Certificates pip trusts, which a harness's installer is given.
  • REQUESTS_CA_BUNDLE, string, from agent: Certificates Python's requests trusts, which a harness's installer is given.
  • LNK_*, a namespace, from agent: Link's own variables, none holding a secret, forwarded whole to the agent's background bridges and its owner's shared harness service.
  • LNK_CODE, string, from harness-contract: The code tool's address in a harness's environment: its project's language servers, each in a sandbox
  • LNK_FILE, string, from harness-contract: The file tool's address in a harness's environment: its files read and written as its sandbox file says
  • LNK_RUN, string, from harness-contract: The run tool's address in a harness's environment: its commands, each in a sandbox of its own
  • LNK_MODEL_URL, string, from model: The calling agent's granted model namespace, which the typed model commands call when it's set
  • LNK_FALLBACK_MODEL_URL, string, from link-model-contract: The fallback model's namespace, handed to a sandbox whose grant has one, beside LNK_MODEL_URL
  • LNK_STORE_AGENT, string, from store: Storage driver protocol: the agent the storage bridge selected for the request being served
  • LNK_STORE_DIR, string, from store: Storage driver protocol: the absolute folder holding the agent collections the storage bridge asks the driver to serve
  • CHROMIUM, string, from browser-tool: The Chromium the browser's tests drive, ahead of one on PATH or Playwright's
  • LNK_TEST_NOTES_PARENT, string, from memory-tool: A folder the notes test, on a Mac, saves beneath where memory's sandbox can't read it; the test runs only when it's set
  • LNK_MEMORY, string, from memory: The agent's memory's address in its harness's environment: an MCP server over HTTP
  • LNK_MEMORY_DRIVER, string, from memory: The store driver the agent's spec keeps its conversations by, the only one memory runs to read them; unset, it runs none
  • LNK_MEMORY_FROM, boolean, from memory: 1 when the agent's harness is sent messages from others, so memory writes notes only in the owner's conversations
  • LNK_MEMORY_MODEL, string, from memory: The address of the embedding model memory ranks by, an OpenAI-style API on this machine; empty when no runtime here has the model
  • LNK_MEMORY_NOTES, string, from memory: The agent's notes file memory may write; unset, it writes nothing of the agent's folder
  • LNK_MEMORY_SPEC, string, from memory: The agent's [tool.memory] opinions as JSON, in the environment of every memory command; unset, the engine's own
  • LNK_RUN_CONTEXT, string, from link-run-tool-contract: The run server's protected context, its named routes and the agent's binding lookup, read outside every task's sandbox and never passed to a task
  • LNK_CRONTAB, string, from scheduler-tool: A program to stand in for crontab in tests: the scheduler's cron driver writes its line through it, on a Mac too
  • LNK_TEST_SCHEDULER_WAKE, string, from scheduler-tool: Set by the runner's test of a wake beside another runner's firing, to run that test alone in a child of its own
  • BRAVE_API_KEY, string, from web-tool: Your Brave Search API key, in web's environment, never the harness's
  • LNK_WEB_SEARCH, string, from web-tool: The search API web uses when both keys are set: brave or tavily
  • LNK_WEB_SEARCH_URL, string, from web-tool: Where search requests go instead of the provider's API, for tests: read only by a debug build, https or http to loopback
  • TAVILY_API_KEY, string, from web-tool: Your Tavily API key, in web's environment, never the harness's
  • LNK_RESOURCE_JOURNAL, string, from cloud-contract: Private JSONL file for durable machine launch intents and sibling disposable-job identity records; unset disables journaling.
  • AWS_DEFAULT_REGION, string, from box: Read once by lnk cloud connect aws: the login to reuse and its region.
  • AWS_PROFILE, string, from box: Read once by lnk cloud connect aws: the login to reuse and its region.
  • AWS_REGION, string, from box: Read once by lnk cloud connect aws: the login to reuse and its region.
  • CLOUDSDK_CONFIG, string, from box: gcloud's own settings, as gcloud reads them: lnk cloud connect gcp asks gcloud where its login is.
  • LNK_AWS, string, from box: The cloud CLIs the adapters run (tests).
  • LNK_BOX, string, from box: In a setup script's environment: the box it sets up.
  • LNK_BOX_HERE, string, from box: In what lnk box run and lnk box ssh run in a box here: the box's name. lnk box user refuses there, since a box user is a login on a machine of its own.
  • LNK_BOX_SSH, string, from box: How lnk box reaches a box: direct, its port 22; tunnel, through its cloud's own tunnel over HTTPS (AWS Systems Manager, Google Cloud's IAP), where port 22 can't be reached, as from a Claude Code cloud session. A tunnel to a box on AWS needs AWS's session-manager-plugin here. Anything else fails, saying so.
  • LNK_GCLOUD, string, from box: The cloud CLIs the adapters run (tests).
  • LNK_SSH, string, from box: What lnk box runs (tests).
  • LNK_SSH_KEYGEN, string, from box: What lnk box runs (tests).
  • LNK_TEST_BOX_END, string, from box: Debug builds only: read the disposable-box ending policy from this file instead of /etc/lnk/end.json.
  • LNK_*, a namespace, from box: SSH program overrides: append the uppercase program name with dashes changed to underscores, such as LNK_SSH or LNK_SSH_KEYGEN.
  • LNK_JOB_OUT, string, from env: In a job's environment: the folder whose files go to its bucket with --out.
  • LNK_SUDO, string, from env: What runs a root stage, service or job on a box, for tests. A debug build reads it; a release build doesn't.
  • LNK_TEST_BOX_ROOT, string, from env: A folder standing for / where lnk box user keeps a box's users and their programs, owned by the user rather than root, for tests of a stand-in box. A debug build reads it; a release build doesn't.
  • LNK_TEST_JOB_GROUP, string, from env: Debug builds only: sample this process group instead of the current job process tree.
  • LNK_TEST_KEEPER, string, from env: The socket of a keeper of your secrets that a test serves, used in place of /run/lnk-secrets/keeper.sock whether or not this machine has the lnk-secrets user. A debug build reads it; a release build doesn't.
  • LNK_TEST_MACHINE_KIND, string, from env: A file read in place of /etc/lnk/kind.toml, owned by the user rather than root, for tests of a stand-in box. A debug build reads it; a release build doesn't.
  • LNK_TEST_WORKERS_CONFIG, string, from env: A trusted worker configuration file for a test's stand-in box, owned by the current user or root. A debug build reads it; a release build doesn't.
  • DEBIAN_FRONTEND, string, from sandbox: How Debian's installer asks: noninteractive as the sandbox installs bubblewrap with apt on a box, where no one answers, so nothing waits on a question.
  • LNK_CHECK_SECRET, string, from sandbox: The bait secret lnk sandbox check gives a helper it starts outside the sandbox, in its environment, for the probe that tries to read another program's environment: never a real secret.
  • LNK_PROBE_*, string, from sandbox: What lnk sandbox check hands each probe it runs inside the sandbox: its bait and what it tries (LNK_PROBE_ARG), the folders it reads or writes, the ports and machines it reaches. Its *: What the probe is handed, as ARG or CANARY.
  • LNK_SANDBOX_LEARN_FD, string, from sandbox: Into the sandbox, for its first program, which removes it: the descriptor it writes each program started to. A program inside that sets it only records what it runs itself.
  • LNK_TEST_CA, string, from sandbox: A certificate authority's PEM file the sandbox's proxy trusts beside this machine's, for a test's own host over TLS. A debug build reads it; a release build doesn't.
  • LNK_TEST_ON_CLOUD, string, from sandbox: 1: the sandbox takes this machine for a cloud's, refusing [lan] what it refuses there (tests). Nothing makes a cloud's machine not one.
  • LNK_TEST_RESOLVE, string, from sandbox: name=address, comma separated: the sandbox's proxy gives each name those addresses without asking this machine's resolver (tests, on a machine without DNS). A debug build reads it; a release build doesn't.
  • SSH_ORIGINAL_COMMAND, string, from sandbox: The command an SSH client asked for, which lnk sandbox enter, a key's forced command, runs in the sandbox.
  • LD_AUDIT, string, from link-sandbox-confine: Libraries the system's dynamic loader hands every symbol a program binds: never inherited by a confined program.
  • LD_LIBRARY_PATH, string, from link-sandbox-confine: Folders the system's dynamic loader searches for a program's libraries before its own: never inherited by a confined program.
  • LD_PRELOAD, string, from link-sandbox-confine: Libraries the system's dynamic loader loads into every program first, which a confined program never inherits, and lnk sandbox check sets to prove a loaded library stays inside the sandbox too.
  • LNK_PROXY_LISTENER_FD, string, from sandbox-client: Proxy startup protocol: inherited TCP listener descriptor, validated against the requested loopback address before use.
  • LNK_SANDBOX_OPEN, string, from sandbox-client: Sandbox browser protocol: authenticated loopback proxy URL used by the browser-opening shim.
  • LNK_TEST_BOOTSTRAP, string, from secret: Debug builds only: permit the bootstrap test launcher to receive box credentials without root.
  • LNK_TEST_TPM_DEVICE, string, from secret: Debug builds only: TPM device path used in place of /dev/tpmrm0.
  • LNK_TEST_TPM, string, from link-secret-contract: Debug builds only: substitute the TPM tool for isolated secret-storage tests.
  • LNK_TEST_TPM_RUN, string, from link-secret-contract: Debug builds only: private operation folder used by isolated TPM tests.
  • LNK_PERSONAL_DIR, string, from storage: Your files folder, an absolute path.
  • LNK_RCLONE, string, from storage: Run this rclone instead, unchecked (tests).
  • AWS_*, a namespace, from storage: AWS's sign-in variables, removed from a run that signs in as a cloud's own account
  • RCLONE_*, a namespace, from storage: rclone's own settings, each removed from its run so only Link's config file sets it up
  • LNK_ARTIFACT_BUDGET, string, from link-artifact: Positive byte budget for the shared immutable-download cache; defaults to 2147483648 bytes.
  • LNK_ARTIFACT_CACHE, string, from link-artifact: Shared folder for verified immutable downloads; defaults to this machine's cache/artifacts folder.
  • CARGO, string, from link-component: The Cargo that builds a component's programs for its tests [default: cargo].
  • LNK_BUILT_FROM, string, from link-component: The commit a release build from source was built from, which a component's build script gives each program as it's compiled (link_component::SOURCE_VARIABLE), so a question names the commit its asker was built from.
  • LNK_DESCRIPTION_PROTOCOL, string, from link-component: The description protocol version of the program asking another for its description or lnk for its registry (link_component::PROTOCOL_VARIABLE). The answerer answers in it, and refuses one below the oldest it accepts, naming the upgrade.
  • LNK_EXEC_DIR, string, from link-files: Absolute adapter program directory, staged during install and read only during a run. It grants no filesystem access.
  • LNK_UPGRADE_PROTOCOL, string, from link-files: The upgrade protocol version of the core asking a program of a release what it changes, or to make its changes (link_files::upgrade::PROTOCOL_VARIABLE): the program answers in that version, and refuses one below the oldest it accepts, naming lnk upgrade. A program asked to write its files refuses an asker that states none.
  • LNK_INNER, string, from link-format: Set for a nested Link command: leave next steps and the report footer to the outer command. An absolute folder is where it leaves its trace if it fails, for the outer report.
  • LNK_OUTPUT_COLOR, string, from link-format: Output color preference: always, never or auto; aliases on/off and boolean spellings are accepted.
  • LNK_OUTPUT_EMPHASIS, string, from link-format: Output emphasis preference: always, never or auto; aliases on/off and boolean spellings are accepted.
  • LNK_OUTPUT_LINKS, string, from link-format: Output link preference: always, never or auto; aliases on/off and boolean spellings are accepted.
  • LNK_OUTPUT_SYMBOLS, string, from link-format: Output symbols: emoji, plain or none; defaults to emoji.
  • RUST_LOG, string, from link-format: What a service Link runs logs, as a Rust tracing filter such as debug [default: info]. The HTTP crates it calls through stay at warnings, as they log credentials below that.
  • LNK_INTERACTIONS, string, from link-interactions: The machine's interaction store, an absolute folder, for a harness whose HOME is its own: lnk-agent names it where the harness reaches Link's settings, and the harness's tool calls then carry their work's binding.
  • LNK_SECURITY, string, from link-keychain: Debug builds only: a Keychain tool stand-in for tests, which enables Keychain access on the test host; release builds always run /usr/bin/security.
  • LNK_SECRETS_FD, string, from link-secretive: Private Link child-process protocol: descriptor for the sealed-off secret handoff pipe; never a credential value.
  • LNK_SECRET_DUMPABLE, string, from link-secretive: Debug builds only: a nonempty value leaves process dumping enabled for a debugger or memory-isolation test.
  • LNK_SERVICES, string, from link-service: Set to off to disable background service management.
  • LNK_TEST_SERVICE_CONFIG, string, from link-service: Debug builds only: select another service configuration path while preserving root ownership, ancestor, mode and no-link trust checks.
  • LNK_HISTORY_PROTOCOL, string, from link-spec: The history protocol version a program asking lnk for the release's history states: lnk upgrade asking the downloaded core, or a module its own core (link_spec::history::PROTOCOL_VARIABLE). The core answers in it, and refuses one below the oldest it accepts, naming the upgrade.