Things on this page are fragmentary and immature notes/thoughts of the author. Please read with your own judgement!
You can create a token using
zellij web --create-tokenand then start a web server for zellij usingzellij web.By default,
zellij webuses the IPv4 address127.0.0.1. Modern browsers (Chrome, Edge, ect) might resolveslocalhostas the IPv6 address::1. If that’s the case, visitinglocalhost:8082will results in the error codeERR_EMPTY_RESPONSE. It is suggested that you use127.0.0.1instead oflocalhostwhen visiting the web page or doing local port fowarding via SSH tunneling.Use
mkcertto create certificate for hosting HTTPS if you need to share sessions beyong the local network.
For more discussions, please refer to The Zellij Web Client - Share Sessions in the Browser .
Handle Conflicts of Keybindings with Google Chrome¶
Configure different keybindings in Zellij.
Configure different keybindings in Google Chrome for those non-builtin keybindings.
Enter a tab into the fullscreen Mode (with Keyboard Lock). Chrome includes the Keyboard Lock API, which allows web applications to capture reserved system keystrokes (including Ctrl + T, Ctrl + N, and Ctrl + W), but only when the browser tab is in fullscreen. This is kind of like the lock mode of Zellij, which allows keystokes to be passed into applications running in Zellij terminals.