How does Environment Manager work in 1DevTool?

Step 1: Open Your Env Files — The Environment Manager detects all .env files in your project. Switch between .env, .env.local, and .env.production. Step 2: Edit Key-Value Pairs — Add, modify, or delete environment variables in a structured editor. Secrets are masked by default. Step 3: Save Safely — Changes are saved as drafts first. Preview what changed before writing to the file. Step 4: Monitor Ports — Switch to the Port Manager to see all active ports. Filter and kill processes that are blocking your dev server.

Environment & Ports

Environment Manager

Structured .env editor with key-value pairs, secret masking, and multi-file support (.env, .env.local, .env.production).

Download 1DevTool All Features

Screenshot coming soon

Why You Need This

How this feature boosts your daily productivity

Environment variables are the most common source of "works on my machine" bugs. Editing .env files in a text editor gives you no validation, no visibility into which variables are set across environments, and no protection against accidentally committing secrets. The Environment Manager shows all your env files in a structured key-value view with secret masking, draft saving, and instant switching between .env variants.

How It Works

Get started in 4 simple steps

Open Your Env Files

The Environment Manager detects all .env files in your project. Switch between .env, .env.local, and .env.production.

Edit Key-Value Pairs

Add, modify, or delete environment variables in a structured editor. Secrets are masked by default.

Save Safely

Changes are saved as drafts first. Preview what changed before writing to the file.

Monitor Ports

Switch to the Port Manager to see all active ports. Filter and kill processes that are blocking your dev server.

Without 1DevTool

The manual way vs. the 1DevTool way

The Hard Way

# vim .env

# Accidentally see all secrets in plain text

# Manually compare .env with .env.production

# Forget which variables changed

# Accidentally commit .env to git

# Break production with a typo

The 1DevTool Way

Structured key-value editor.

Secrets masked by default.

Draft saving prevents accidents.

Key Capabilities

Everything included with Environment Manager

Structured key-value editor for .env files with secret masking

Multi-file support: .env, .env.local, .env.production, and custom files

Draft saving with change preview before writing to disk

Active port listing with process name, command, and PID details

One-click process kill for resolving port conflicts instantly

Filter ports by number, process name, or command

Why It Matters

The productivity impact of having environment & ports built into your workspace

Structured Editing

Key-value editor with secret masking is safer and clearer than editing raw .env files in a text editor.

Multi-Environment Support

Switch between .env, .env.local, and .env.production instantly. Compare variables across environments.

Instant Port Resolution

See what's using port 3000 and kill it in one click. No more lsof | grep | kill command chains.

Draft Protection

Preview changes before saving. Never accidentally overwrite production secrets or break your local setup.

Ready to boost your workflow?

Download 1DevTool for free and experience Environment Manager along with 48 other features — all in one app.

Download for Free View Changelog