SSH CONNECTION SETTINGS / AUTOMATION

Save the connection details, not the busywork.

Bring existing PuTTY and OpenSSH config hosts into ShadeTerm, then keep per-host options such as startup commands and environment variables together.

Connection settings for a host

Import PuTTY and SSH configStartup commandsPer-connection environment settings

01 / WHY IT MATTERS

Recreating SSH host settings is repetitive — and a typo in a port, key path, or jump host can make troubleshooting harder than it needs to be.

ShadeTerm keeps your tools focused on a connection and the task you are doing — rather than adding more windows and manual steps.

01 / FEATURE

Import what already exists

Start from PuTTY sessions or OpenSSH ~/.ssh/config entries instead of recreating every hostname and port.

02 / FEATURE

Keep per-host behavior explicit

Store a startup command or connection-specific environment settings with the profile where they belong.

03 / FEATURE

Adjust advanced connections

Configure options for tunnels, jump hosts and forwarding when your network requires them.

SEE IT IN SHADETERM

Set up and import connection profiles.

Screens from ShadeTerm for Windows — the interface behind the workflow.

Actual import UI offering PuTTY and OpenSSH config import — Bring existing SSH profiles into ShadeTerm

Actual per-host settings for startup command and environment variables, if available — Keep advanced options with the connection

02 / IN PRACTICE

How this fits your server workflow.

Designed around everyday developer tasks, not a dashboard of features you never use.

Move existing configurations into one interface

An OpenSSH config might define HostName, User, Port and IdentityFile. Importing relevant settings makes the transition faster, but review the imported profile before using it in production.

PuTTY session imports and ~/.ssh/config imports are supported entry points. Advanced OpenSSH constructs can require manual review.

Startup commands and environment variables

Use per-host startup commands for deliberate, repeatable setup steps. Keep environment variables scoped to the intended session or connection rather than assuming they should apply globally.

Avoid putting tokens or passwords into visible command text; use appropriately protected secrets instead. Be mindful that remote sshd policy may restrict environment forwarding.

03 / WORKFLOW

From connection to result.

A focused sequence you can follow in your own ShadeTerm workspace.

01 / STEP

Import

Choose PuTTY or OpenSSH configurations, or create a profile manually.

02 / STEP

Review

Check host, port, username and identity settings.

03 / STEP

Connect

Add advanced options only where a server requires them.

04 / DETAILS

Common questions.

Practical limitations and useful details before you get started.

Will every OpenSSH directive import perfectly?

Not necessarily. Complex Include, Match, ProxyCommand and other settings can require review after import.

Can startup commands change my server?

Yes. Review commands carefully, especially if they execute automatically on connection.

Are environment variables the same as secret storage?

No. Environment variables can be observable to processes and logs. Do not treat them as a secure vault.

Explore related featuresSSH Key Manager ↗ SSH Jump Host ↗ Command Snippets ↗

ShadeTerm / WINDOWS

Work with your server, not around your tools.

Terminal, files, code and more — organized around your SSH connections.

Try ShadeTerm