dotenv-org

Dotenv Vault — Development skill for Claude Code

Development community intermediate

Sync environment variables across machines for consistent Claude Code behavior.

How to install Dotenv Vault

This entry records only its repository, not the path inside it, so there is no exact command to give. Open dotenv-org/dotenv-vault and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Dotenv Vault does

It works with a single command. Run `npx dotenv-vault@latest push`.

Alternatives in Development

n8n Expression Syntax — n8n expression syntax with {{}} and $json/$node variables 3.6k ★
Harness Remote — Native-session control plane for Codex, Claude Code, OpenCode, OMP and PI 356 ★
Env — Manage Vercel environment variables 263 ★

README

`dotenv-vault` is a cli to *sync .env files across machines, environments, and team members*.

[](https://npmjs.org/package/dotenv-vault)

[!NOTE] dotenv-vault is a **paid only cloud service for syncing your .env files** (as of May 2025).

*Looking for a free cloud-less alternative?* See my new product [dotenvx](https://github.com/dotenvx/dotenvx) – that lets you:

encrypt your .env files
commit them to code
and securely sync them over git

🌱 Install

It works with a single command. Run `npx dotenv-vault@latest push`.

npx dotenv-vault@latest push

remote:   Securely pushing (.env)... done
remote:   Securely pushed development (.env)
remote:   Securely built vault (.env.vault)

That's it. You securely synced your `.env` file. Next, tell your teammate to run `npx dotenv-vault@latest pull`

npx dotenv-vault@latest pull

Nice!

See further [usage](#%EF%B8%8F-usage) and [commands](#-commands).

🏗️ Usage

When you make a change to your `.env` file, push it up.

$ npx dotenv-vault@latest push

Commit your `.env.vault` file safely to code.

$ git add .env.vault
$ git commit -am "Add .env.vault"
$ git push

Now your teammate can pull the latest `.env` changes.

$ git pull
$ npx dotenv-vault@latest pull

That's it!

Learn more about usage

🚀 Deploying

Stop scattering your production secrets across multiple third-parties and tools. Instead, use an encrypted `.env.vault` file.

Generate your encrypted `.env.vault` file.

$ npx dotenv-vault@latest build

Fetch your production `DOTENV_KEY`.

$ npx dotenv-vault@latest keys production
remote:   Listing .env.vault decryption keys... done
dotenv://:key_1234…@dotenv.org/vault/.env.vault?environment=production

Set `DOTENV_KEY` on your server.