~/.waveterm
directory. None of that information ever leaves your machine. In the future we may launch cloud features to support terminal sharing, shared workspaces, shared playbooks, and terminal backup/sync. These will opt-in. We’ll never release an update that moves your private data off your machine without your explicit consent.
.bash_profile
and .zshrc
). In order to customize Wave’s environment at startup Wave will set the environment variable WAVESHELL
.
~/.ssh/config
file. Wave Terminal uses ssh natively under the hood and so any options set in your ssh config will be picked up by Wave directly.
reset
or (/reset
).
Wave loads your bash configuration by executing bash with the -l and -i options (so it is an interactive login shell). That means any changes need to be in your .bash_profile
to take effect (unless your .bash_profile
also sources your .bashrc
). Note that sessions are persistent in Wave, so even if you change your startup files the changes won’t take effect in any currently open tabs (unless you explicitly run reset
).
ssh
command at the Wave prompt. That will create a command block that runs your remote ssh session. When running ssh like this mshell/waveshell will not be installed on your remote machine.
For more information see WaveShell Helper
/reset shell=zsh
or /reset shell=bash
the shell will be changed. Note that your cwd and environment will be reset as if this were a new session. You can tell if the shell switch was successful by checking the shell type flag that appears at the bottom right hand corner of the command input box.
/reset
) will force Wave to re-read your bash config files and produce a new valid state. Note that after running the reset, your cwd and environment will be reset as if this was a new session.