Practical Agent workflows
Let the Agent set up your terminal
WispTerm's Agent can now save SSH server profiles with a built-in tool, connect those profiles, inspect terminals, and keep PowerShell beside the Agent on first launch.
Create SSH profiles by asking
This use case came from issue #33: the SSH profile form is not obvious for new users, but an Agent can turn a natural-language request into a saved profile.
What to ask
Tell the Agent the profile name, host, user, port, and whether a password should be saved. It will call ssh_profile_save instead of editing files by hand.
What gets saved
The profile is stored in WispTerm's normal SSH profile list. Existing profiles are updated by name or host, and new profiles default to port 22.
Password handling
Approval text and tool output redact the password. If you omit the password while updating an existing profile, the saved password is preserved.
Ask:
Create an SSH profile named lab:
host 192.0.2.10, user alice, port 2222.
Save this password, then connect it.
Agent tools:
ssh_profile_save
ssh_profile_connectStart with Agent and PowerShell
On a plain first launch, WispTerm opens the AI Agent first and PowerShell second. Session restore and explicit working-directory launches keep their existing behavior.
Profile exists
The first tab is the default AI profile running with Agent mode enabled. The second tab is the configured PowerShell family shell.
No AI profile yet
WispTerm opens a terminal placeholder, opens the AI profile setup form on it, and still creates the PowerShell tab beside it.
Restore wins
When restore-tabs-on-startup = true successfully restores a previous session, WispTerm does not add default Agent or PowerShell tabs.
Good Agent prompts
SSH onboarding
Help me set up SSH.
Create a profile called gpu-box for:
host gpu.example.com
user demo
port 22
Then connect it.Daily terminal work
Use the PowerShell tab to inspect this repo.
Find the test command, run it, and summarize
only the failures that need my attention.