Skip to content

Settings, data & updates ​

Language and appearance ​

Open Settings → Appearance for Chinese/English, dark/light theme and the default font size for new sessions. Server output, file content and user names stay unchanged.

An existing local session has its own font setting in Properties; changing the default is a separate action.

Environment and local proxy ​

Global environment/network settings provide defaults; local-session environment/proxy settings can override them. Enter one KEY=value per line without additional quoting.

text
HTTP_PROXY=http://127.0.0.1:10808
NO_PROXY=localhost,127.0.0.1
MY_SETTING=value=with=equals

Proxy URLs support http://, https://, socks5:// and socks5h://. Proxy settings populate HTTP_PROXY, HTTPS_PROXY and ALL_PROXY. Precedence is: system environment → global proxy → global environment → session proxy → session environment.

These values affect newly launched local shells and child processes. They do not modify Windows system proxy settings or provide SSH proxy/jump-host support. Programs decide whether to honor proxy environment variables.

Data locations ​

Product / fileContents
%LOCALAPPDATA%\BranchTerm\config.jsonLocal projects, sessions, language and workspace
%LOCALAPPDATA%\eShell\config.jsoneShell workspace, language and local sessions
config.ssh.json inside the eShell directorySSH profiles, groups, recents and tab descriptions
config.ssh-trust.json inside the eShell directoryHost trust records
Windows Credential ManagerPasswords explicitly saved after successful authentication

Set ESHELL_CONFIG or BRANCHTERM_CONFIG before launch to choose an isolated configuration file. Valid configurations receive a backup when saved; damaged files are not silently overwritten.

Passwords are bound to the Windows user, configuration path and saved profile ID. JSON and Excel backups do not include them. Moving machines or configuration paths, or copying saved profiles, requires saving passwords again. Private-key passphrases are never saved.

Update an app ​

  1. Exit the app normally.
  2. Back up its configuration and old program directory.
  3. Replace the complete runtime folder, including both runtime files and notices.
  4. Launch from the permanent path and check menus, profiles and connections.

Windows prevents replacing a running executable. Updating source or building into another folder does not update an installed app. Restart restores descriptions, not old processes, connections or command input.

Use Excel export for an inventory and retain the configuration directory for workspace backups.

Windows desktop terminals · Illustrated guides