Environment Variable Manager

Manage local-only environments for staging, production, and QA. The active environment is exposed to other KalpLabs tools on the same origin and never leaves your browser.

CtrlEnterSave environment

CtrlShiftCCopy export

CtrlShiftXClear form

CtrlKSwitch tool

Active variables are exposed on the same origin as window.__kalpEnv. KalpLabs also stores the active environment under kalp_active_env so request tools can resolve {{VARIABLE_NAME}} placeholders locally.

Selected environment

Import .env

Upload

Export

Select or create an environment to export.

Related tools

API

API Request Builder

Build and send HTTP requests with headers, params, auth, and body directly in the browser.

Open

API

API Scenario Builder

Chain API requests with shared variables, assertions, and step-by-step execution logs.

Open

API

Webhook Payload Builder

Edit GitHub, Stripe, Slack, Jira, and PagerDuty webhook payload templates locally.

Open

About

Stores named environments with optional secret masking and exposes the active one to other KalpLabs tools on the same origin.

Accepted input

Accepts key-value pairs typed manually or imported from .env text. Exports support .env, JSON, and shell export formats, and values are stored only in localStorage.

How to use

Create a named environment such as local, staging, or production.
Add variables, mark secrets, and choose the active environment from the header selector.
Export or import .env content as needed.
Switch to API Request Builder or Scenario Builder and inject placeholders from the active environment.

Tips

window.__kalpEnv is exposed so other same-origin tools can read the active environment.
Keep separate environments for local and shared staging hosts to avoid accidental request mixups.

This manager keeps environment variables local to your browser and lets you switch active context without copying values into every tool.

Secrets can be masked in the UI, exported in multiple formats, and injected into other request-focused tools through shared local storage.

The active environment is also mirrored on window.__kalpEnv so same-origin tools can read it without a backend.

FAQ

Where are my environments stored?

Environments are stored only in browser localStorage under KalpLabs-specific keys.

How do other tools access the active environment?

KalpLabs writes the active environment to localStorage and exposes it as window.__kalpEnv on the same origin.

Environment Variable Manager

Import .env

Export

Related tools

API Request Builder

API Scenario Builder

Webhook Payload Builder

About

FAQ

Where are my environments stored?

How do other tools access the active environment?

Related Tools

Related tools

API Request Builder

API Scenario Builder

Webhook Payload Builder

About

FAQ

Where are my environments stored?

How do other tools access the active environment?

Related Tools