Removing feature to persist session since is not possible because OAuth process of github.

entrypoint.sh

@@ -157,15 +157,8 @@ else
     echo "File extensions.json not found"
 fi
 
-# Check if CLI directory exists and has content
-if [ -d "/home/${HOME_USER}/.vscode/cli" ] && [ "$(ls -A /home/${HOME_USER}/.vscode/cli 2>/dev/null)" ]; then
-    # CLI directory exists and has content, use restart
-    sudo su ${HOME_USER} -c "code tunnel restart --cli-data-dir /home/${HOME_USER}/.vscode/cli"
-else
-    # No CLI directory or empty, use normal startup
 if [[ -v VSCODE_TUNNEL_NAME && -n "${VSCODE_TUNNEL_NAME}" ]]; then
     sudo su ${HOME_USER} -c "code tunnel --accept-server-license-terms --name ${VSCODE_TUNNEL_NAME}"
 else
     sudo su ${HOME_USER} -c "code tunnel --accept-server-license-terms"
 fi
-fi

readme.md

@@ -39,15 +39,6 @@ docker run -it -e HOME_USER=custom-home-user -e GLOBAL_ENV_MY_GLOBAL_VARIABLE=my
 ```
 In this example, MY_GLOBAL_VARIABLE will be set to my_global_value in the /etc/environment file.
 
-### Persistent VS Code Tunnel
-
-You can maintain the VS Code tunnel configuration between container restarts by adding a volume mount to `/home/${HOME_USER}/.vscode/cli`. When this volume is mounted and the container restarts, it will use `code tunnel restart` to reconnect using the existing tunnel configuration instead of creating a new one.
-
-Example:
-```bash
-docker run -it -e HOME_USER=custom-home-user -e VSCODE_TUNNEL_NAME=vscode-ssh-remote-server -v /path/to/vscode-cli:/home/custom-home-user/.vscode/cli -v /path/to/extensions.json:/home/extensions.json aleleba/vscode
-```
-
 ### Adding VSCode Extensions
 
 To add VSCode extensions to the container, create a JSON file with an array of objects containing the extension details you want to install, the only Mandatory field is uniqueIdentifier and follow this structure. For example:

version.txt

@@ -1 +1 @@
-3.2.2
+3.2.7