A new HTTP API

There is now a new HTTP API for the XPipe daemon, which allows you to programmatically manage remote systems. You can find details and an OpenAPI specification at the new API button in the sidebar. The API page contains everything you need to get started, including code samples for various different programming languages.

To start off, you can query connections based on various filters. With the matched connections, you can start remote shell sessions for each one and run arbitrary commands in them. You get the command exit code and output as a response, allowing you to adapt your control flow based on command outputs. Any kind of passwords and other secrets are automatically provided by XPipe when establishing a shell connection. You can also access the file systems via these shell connections to read and write remote files.

There already exists a community made XPipe API library for python and a python CLI client. These tools allow you to interact with the API more ergonomically and can also serve as an inspiration of what you can do with the new API. If you also built a tool to interact with the XPipe API, you can let me know and I can compile a list of community development projects.

Service integration

Many systems run a variety of different services such as web services and others. There is now support to detect, forward, and open the services. For example, if you are running a web service on a remote container, you can automatically forward the service port via SSH tunnels, allowing you to access these services from your local machine, e.g. in a web browser. These service tunnels can be toggled at any time. The port forwarding supports specifying a custom local target port and also works for connections with multiple intermediate systems through chained tunnels. For containers, services are automatically detected via their exposed mapped ports. For other systems, you can manually add services via their port.

You can use an unlimited amount of local services and one active tunneled service in the community edition.

Script rework

The scripting system has been reworked. There have been several issues with it being clunky and not fun to use. The new system allows you to assign each script one of multiple execution types. Based on these execution types, you can make scripts active or inactive with a toggle. If they are active, the scripts will apply in the selected use cases. There currently are these types:

Init scripts: When enabled, they will automatically run on init in all compatible shells. This is useful for setting things like aliases consistently
Shell scripts: When enabled, they will be copied over to the target system and put into the PATH. You can then call them in a normal shell session by their name, e.g. myscript.sh, also with arguments.
File scripts: When enabled, you can call them in the file browser with the selected files as arguments. Useful to perform common actions with files

If you have existing scripts, they will have to be manually adjusted by setting their execution types.

Docker improvements

The docker integration has been updated to support docker contexts. You can use the default context in the community edition, essentially being the same as before as XPipe previously only used the default context. Support for using multiple contexts is included in the professional edition.

There's now support for Windows docker containers running on HyperV.

Note that old docker container connections will be removed as they are incompatible with the new version.

Proxmox improvements

You can now automatically open the Proxmox dashboard website through the new service integration. This will also work with the service tunneling feature for remote servers.

You can now open VNC sessions to Proxmox VMs.

The Proxmox professional license requirement has been reworked to support one non-enterprise PVE node in the community edition.

Better connection organization

The toggle to show only running connections will now no longer actually remove the connections internally and instead just not display them. This will reduce git vault updates and is faster in general.

You can now order connections relative to other sibling connections. This ordering will also persist when changing the global order in the top left.

The UI has also been streamlined to make common actions and toggles more easily accessible.

Other

The title bar on Windows will now follow the appearance theme
Several more actions have been added for podman containers
Support VMs for tunneling
Searching for connections has been improved to show children as well
There is now an AppImage portable release
The welcome screen will now also contain the option to straight up jump to the synchronization settings
You can now launch xpipe in another data directory with xpipe open -d "<dir>"
Add option to use double clicks to open connections instead of single clicks
Add support for foot terminal
Fix rare null pointers and freezes in file browser
Fix PowerShell remote session file editing not transferring file correctly
Fix elementary terminal not launching correctly
Fix windows jumping around when created
Fix kubernetes not elevating correctly for non-default contexts
Fix ohmyzsh update notification freezing shell
Fix file browser icons being broken for links
The Linux installers now contain application icons from multiple sizes which should increase the icon display quality
The Linux builds now list socat as a dependency such that the kitty terminal integration will work without issues

Downloads

Installers

Installers are the easiest way to get started and they come with an automatic updater functionality. They can also be used to upgrade an existing installation to a newer version. The following installers are available:

Portable

If you don't like installers, you can also use portable versions that are packaged as an archive. The following portable versions are available:

Install Script

Install XPipe by pasting the installation command into your terminal. This will perform the full setup automatically.

Windows

powershell -ExecutionPolicy Bypass -Command iwr "https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.ps1" -OutFile "$env:TEMP\get-xpipe.ps1" ";"  "&" "$env:TEMP\get-xpipe.ps1" -XPipeVersion "10.0"

Bash Script (Linux / MacOS)

bash <(curl -sL https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.sh) -v 10.0

xpipe-io/xpipe 10.0 on GitHub