⚡ Terminal Session Proxy Manager

Manage proxy profiles for your terminal session from one command, in Rust: switch profiles, benchmark latency, diagnose connectivity, and control the environment variables your tools actually read — on macOS and Linux (Zsh / Bash).

• Profiles, not exports. Name your proxies once, then switch with a single command or an interactive picker.
• Interactive TUI dashboard. Live IP, geolocation, latency sparkline, and profile switching in one screen.
• Pick the fastest automatically. Benchmarks every profile — each against all its ping targets at once — and selects the best one, with a health monitor that fails over to another profile when the active proxy dies.
• Diagnostics. Latency probes, socket checks, and a real bandwidth test.
• Exports everything. One command for Docker, cURL, Git, .env, and JVM build tooling — with correct shell quoting.
• Bilingual. Full English and Russian interface.

Homebrew (macOS / Linux):

brew install LebedevKondakovSergeyVach/tap/tspm

Cargo (requires Rust 1.88+):

cargo install tspm

This installs the tspm command into ~/.cargo/bin.

From source:

git clone https://github.com/LebedevKondakovSergeyVach/Terminal-Session-Proxy-Manager.git
cd Terminal-Session-Proxy-Manager
cargo install --path .

The binary cannot change the environment of the shell that launched it — no process can. The proxy shell function bridges that gap, so add the init script to your shell configuration:

Zsh (~/.zshrc):

eval "$(tspm init zsh)"

Bash (~/.bashrc):

eval "$(tspm init bash)"

Restart your terminal or run source ~/.zshrc. You now have proxy on, proxy off, proxy switch, and tab completion.

proxy profile set home --name "Home" --host 127.0.0.1 --port 1080
proxy on
proxy status

The active profile in config.json supplies two ways to apply proxy settings:

flowchart TD
    accTitle: Where proxy settings apply
    accDescr: Both commands read the active profile in config.json. proxy on changes the current shell and its future child commands. proxy run sets variables for one child command and its children, leaving the current shell unchanged.
    Profile["Active profile in config.json"]
    Profile --> On["proxy on"]
    Profile --> Run["proxy run -- …"]
    On --> Shell["Current shell environment"]
    Shell --> Commands["New commands inherit variables"]
    Run --> Child["Child command and its children"]

proxy on applies variables in your current shell; commands started there inherit them. proxy run -- <cmd> applies them to that child command and its children, leaving the shell unchanged. Tools must support these proxy settings. Other terminals and already running processes keep their environment. See the shell integration guide for the export and dashboard sequences.

Anything that changes your current shell goes through the proxy function; everything else works with the full binary name too.

Available on every subcommand.

NO_COLOR is honoured. Useful for keeping several setups apart:

TSPM_CONFIG=~/work-proxies.json proxy best

Two files, both JSON:

• config.json — profiles and the endpoints used for testing.
• settings.json — interface language and an optional custom config path.

Both live in your OS configuration directory (~/Library/Application Support/tspm on macOS, ~/.config/tspm on Linux). Run proxy config path to see exactly which file is in use.

Resolution order for config.json: --config-file → TSPM_CONFIG → config_path in settings.json → the OS config directory.

A config file that exists but contains invalid JSON is reported and left alone — it is never overwritten with defaults.

See docs/CONFIGURATION.md for the full schema, and configs/config.default.json for a complete example.

• 🌐 Documentation site — everything below, searchable and cross-linked
• 📦 Installation — build instructions and PATH setup
• 🐚 Shell Integration — Zsh, Bash, and prompt setup
• ⚙️ Configuration — full config.json and settings.json schema
• 📖 Command Reference — every subcommand and flag
• 🤝 Contributing · 🔒 Security · 📝 Changelog

GNU AGPLv3