EnvSync-LE

Name: EnvSync-LE
Author: nolindnaidoo

Spot missing keys across your .env files — automatic checks, a status bar counter, and a markdown report.

FreeOpen sourceMITNo network access

Install for VS Code Source on GitHub

EnvSync-LE in use: Spot missing keys across your .env files — automatic checks, a status bar counter, and a markdown report.

What EnvSync-LE does

Environment files drift the moment one of them gains a key. EnvSync-LE compares the variable names across the .env files in your workspace and tells you which file is missing which key — names only, never values. Checks run automatically when a watched file changes, and the current issue count sits in the status bar.

What people use it for

A debounced sync check runs whenever a watched .env file changes — no command to remember.

auto compares against the union of all keys, manual only the files you list, template validates everything against one reference file.

The report lists missing keys by name. The values in a .env file are exactly what should not be copied around.

Install EnvSync-LE

VS Code

ext install nolindnaidoo.envsync-le

Open Quick Open (Cmd/Ctrl+P) and paste.

Cursor / VSCodium

cursor --install-extension OffensiveEdge.envsync-le

VS Code forks pull from Open VSX, where the namespace is OffensiveEdge.

ZedComing soon

npx -y envsync-le-mcp

Works in Zed today — add the command above as a custom MCP server from the agent panel, and compare_env_files appears in its tool list. The one-click listing in Zed's extension registry is a pull request awaiting review. Track the review.

AI agents

npx -y envsync-le-mcp

Runs EnvSync-LE's engine as an MCP server, so an agent can call compare_env_files with no editor involved. VS Code 1.101+ needs nothing — the extension registers it for you.