Describe the bug
I've noticed that from version 1.6.0 onwards, there have been issues upon launching and using Sliver's console. More specifically, upon launch, it appears that Sliver does not correctly escape the terminal, causing escape sequences to appear, and this often causes subsequent commands to not present their output and appear to hang, requiring a manual press of Enter to continue.
To Reproduce
Steps to reproduce the behaviour:
- On a clean Kali installation, with the latest version of Sliver installed, start Sliver. This presents the first problem.
- Interact with the console by spawning new Sliver implant sessions and interacting with them. You'll notice that some commands appear to hang occasionally, requiring you to press Enter to proceed.
Expected behaviour
Sliver version 1.5.43 was the final version where this issue was not apparent. There were no issues with how commands were processed or how the console appeared.
Screenshots
Launching Sliver (reproducible issue 1):

Interacting with the console (reproducible issue 2):

Note that even though all three implant sessions become established, the console appears to hang, though it's actually just expecting Enter.
Desktop (please complete the following information):
$ uname -a
Linux kali 7.0.12+kali-amd64 #1 SMP PREEMPT_DYNAMIC Kali 7.0.12-2kali1 (2026-06-18) x86_64 GNU/Linux
$ cat /etc/os-release
PRETTY_NAME="Kali GNU/Linux Rolling"
NAME="Kali GNU/Linux"
VERSION_ID="2026.3"
VERSION="2026.3"
VERSION_CODENAME=kali-rolling
ID=kali
ID_LIKE=debian
...
Describe the bug
I've noticed that from version
1.6.0onwards, there have been issues upon launching and using Sliver's console. More specifically, upon launch, it appears that Sliver does not correctly escape the terminal, causing escape sequences to appear, and this often causes subsequent commands to not present their output and appear to hang, requiring a manual press ofEnterto continue.To Reproduce
Steps to reproduce the behaviour:
Expected behaviour
Sliver version 1.5.43 was the final version where this issue was not apparent. There were no issues with how commands were processed or how the console appeared.
Screenshots

Launching Sliver (reproducible issue
1):Interacting with the console (reproducible issue

2):Note that even though all three implant sessions become established, the console appears to hang, though it's actually just expecting
Enter.Desktop (please complete the following information):