Environments

Environments are app-wide groups of variables. Unlike collection variables, which belong to a single collection, environments are global: you create them once and can activate any environment from the TabBar while working across collections and tabs.

One active environment is shared across all open request tabs. When an environment is selected, its variables become available to every request you send.

Managing environments

The Environments section in the sidebar sits below Collections. Each section can be collapsed independently.

• Add — Click the + button in the Environments header to open the Add environment dialog. Use Create new to enter a name, or Import from file to load a HarborClient environment export.
• Activate — Click an environment name to make it the active environment. The selected row is highlighted.
• Settings — Double-click an environment, or choose Settings from the row menu, to open environment settings. Edit the name and variables, then save.
• Export — Choose Export from the row menu. HarborClient opens a save dialog with a default filename of {environment-name}.json.
• Duplicate — Choose Duplicate from the row menu. HarborClient creates a new environment named {original-name} (copy) with the same variables and activates it. The original environment is unchanged.
• Delete — Choose Delete from the row menu. This removes the environment and clears the active selection if it was selected.

Selecting an environment

Use the environment dropdown on the far right of the TabBar. Choose an environment name to activate it, or No Environment to clear the selection.

The active environment persists across app restarts. All tabs share the same selection.

Variables

Environment variables use the same shape as collection variables and support {{key}} syntax in:

• Request URLs
• Headers and query params
• Request body
• Pre- and post-request script source

Each variable has four fields:

Field	Description
Key	Variable name referenced in {{key}} placeholders
Value	Value substituted when the variable is resolved
Default	Used when Value is empty
Share	When unchecked, the variable Value is cleared in environment exports (Key, Default, and Share are kept)

When Value is empty, HarborClient uses Default instead.

Dynamic variables

HarborClient supports Postman-style dynamic variables whose values are generated fresh each time a request is sent. Use them in {{$name}} placeholders in:

• Request URLs
• Headers and query params
• Request body
• Auth fields

See Variables for the complete list of supported dynamic variables.

HarborClient variable names are case-sensitive and include the leading $ for dynamic placeholders.

Dynamic variables resolve after collection and environment variables. If you define a static variable with the same key (for example $randomInt), the static value wins.

Dynamic placeholders are highlighted in the request editor. Hover a token to see its description.

Precedence

At send time, HarborClient builds a runtime variable map from global variables, the active collection, and the active environment. Global variables are loaded first; collection variables are applied on top; environment variables are applied last. When multiple scopes define the same key, environment wins, then collection, then global.

Values set with hc.request.variables.set in a pre- or post-request script override global, collection, and environment variables for the remainder of that send. Use hc.environment.variables.clear(key), hc.collection.variables.clear(key), or hc.globals.clear(key) to remove persisted keys after the send completes. Dynamic variables ({{$name}}) resolve after static variables when no runtime value is defined for that key. See Request scripts for script execution order and the full hc variable API.

The request editor highlights {{variable}} tokens using the merged set of global, collection, and environment variables, with higher-precedence scopes shown when keys overlap.

Storage

Sidebar environments are stored locally on each machine in HarborClient's hidden local database — they are not assignable to a remote storage location or Team Hub. Even when collections live on a shared Firestore, MySQL, PostgreSQL, or Team Hub backend, environment variable groups in the sidebar stay per-instance.

See Storage for how storage locations work and which entities can be assigned to each provider.

The active environment ID is stored in browser localStorage under harborclient.activeEnvironmentId, not in storage.

Export and import

Export

Choose Export from the environment row menu. HarborClient opens a save dialog with a default filename of {environment-name}.json. After a successful export, an Environment exported toast appears.

Variables with Share unchecked have their Value cleared in the export file. Key, Default, and the Share flag are kept so you can share exports without exposing secrets.

Import

Import an environment from a .json file using either:

• File → Import (auto-detects environment exports)
• Add environment → Import from file

If an environment with the same portable uuid already exists, HarborClient prompts you to Update existing, Import as new copy (fresh uuid), or Cancel. Otherwise import creates a new environment. On success, HarborClient activates the imported environment and shows an Environment imported or Environment updated toast.

If the file is invalid, HarborClient shows an alert with a descriptive error (for example, unsupported format version or missing environment name). Canceling the file dialog does nothing.

Export file format

HarborClient environment export files require harborclientExport: "environment" and harborclientVersion: 1. They contain the environment name and variables. Storage IDs are not included.

Example (abbreviated):

{
  "harborclientVersion": 1,
  "harborclientExport": "environment",
  "name": "Staging",
  "variables": [
    {
      "key": "baseUrl",
      "value": "https://staging.example.com",
      "defaultValue": "",
      "share": true
    }
  ]
}

Common validation errors:

Error	Cause
unsupported format version	harborclientVersion is not 1
not a HarborClient environment export	harborclientExport is not "environment"
environment name is required	Name is missing or blank