Most of the time after connecting the model pulls a system information and it is showing the local machine.
Some models behavior can be corrected to pointing them what is the OS of the remote and of the local machine, so it can make a distinction.
When the model is able to self correct it is showing a message similar to:
Confirmed and important: the bash tool is NOT auto-wrapped with SSH in this session. My first probes with && chains ran uname -a locally on WSL2 (Ubuntu). The only way to execute remotely is the explicit ssh -S "/root/.ssh/cm-tengb-vm" "tengb-vm" '...' form, with the entire command inside the quotes so nothing leaks to the local shell.
It will be good to add this auto-wrapping to avoid making wrong alterations to the local system.
Most of the time after connecting the model pulls a system information and it is showing the local machine.
Some models behavior can be corrected to pointing them what is the OS of the remote and of the local machine, so it can make a distinction.
When the model is able to self correct it is showing a message similar to:
Confirmed and important: the bash tool is NOT auto-wrapped with SSH in this session. My first probes with && chains ran uname -a locally on WSL2 (Ubuntu). The only way to execute remotely is the explicit ssh -S "/root/.ssh/cm-tengb-vm" "tengb-vm" '...' form, with the entire command inside the quotes so nothing leaks to the local shell.
It will be good to add this auto-wrapping to avoid making wrong alterations to the local system.