Environment & Ports

Port Manager: Inline Process Details

Click any PID in the Port Manager to expand a process detail panel under the row — parent PID, user, CPU%, memory%, RSS, started-at timestamp, process state, working directory, and full command line on macOS and Linux; parent PID, start time, and command line on Windows. A per-row Copy command button appears on hover.

Port Manager: Inline Process Details

Why You Need This

How this feature boosts your daily productivity

Killing a stuck dev server isn't always the right move — sometimes you need to know what the process actually is before you yank it. Clicking a PID in the Port Manager now expands a detail panel right under the row. On macOS and Linux it shows CPU%, memory%, working directory, and the full command line, read with `ps` plus `lsof` or `/proc`. On Windows it shows parent PID, start time, and the full command line from a native process-table reader, with a PowerShell fallback.

How It Works

Get started in 4 simple steps

1
1

Open Your Env Files

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

2
2

Edit Key-Value Pairs

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

3
3

Save Safely

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

4
4

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

# Search for the right tool online
# Switch between multiple apps
# Copy-paste data between windows
# Lose context every time you switch
# Repeat dozens of times per day

The 1DevTool Way

Everything in one workspace.
No context switching.
All tools integrated and connected.

How it compares

Checking what a process is before killing it usually means ps, lsof or Activity Monitor's inspector, separate from the port list.

  • 1DevToolBuilt in

    Clicking a PID in the port list expands parent PID, user, CPU, memory, start time, working directory and full command under that row (fewer fields on Windows), with a copy button.

  • Activity MonitorBuilt in

    Double-clicking a process in Activity Monitor opens an inspector with its parent, user, CPU and memory use, and its open files and ports.

  • htopPartly

    htop can show PID, parent PID, user, CPU and memory use, state, start time and the full command for each process. Ports need lsof.

  • Windows Task ManagerPartly

    Task Manager's Details tab can show PID, user, CPU, memory and the command line for each process. Listening ports are in Resource Monitor.

Checked November 2026 against each app's public docs. These products change quickly. If a row is out of date, tell us at feedback.stoicsoft.com/1devtool.

Key Capabilities

Everything included with Port Manager: Inline Process Details

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 Port Manager: Inline Process Details along with 347 other features — all in one app.