Jio Client v0.5.0

jio create --exec creates a VM and runs its first command in one API request. Short hosted jio exec commands now use the guest control channel; commands requesting more than 30 seconds continue to use SSH.

jio create --exec 'printf hello'
jio exec <session-id> 'uname -a'
jio update

• jio update installs the latest release into the current executable’s directory, verifies the archive checksum and binary version, and preserves saved credentials and VM state. The directory must be writable.
• Public HTTP exposures and private TCP forwards have clearer errors and port listings.
• The Rust SDK exposes direct execution and create-and-exec, with an opt-in hosted lifecycle acceptance example. Node.js and Python bindings retain SSH execution.

Direct execution requires a compatible Server, Core and guest template. It is bounded to 30 seconds and 64 KiB of combined output. An unsupported endpoint falls back to SSH for jio exec; unknown execution outcomes are not retried automatically. SDK binaries remain source-build only.

Install

macOS / Linux:

curl -fsSL https://github.com/jiovannish/client/releases/latest/download/install.sh | sh

Windows (PowerShell):

irm https://github.com/jiovannish/client/releases/latest/download/install.ps1 | iex

Windows (CMD):

powershell.exe -NoProfile -ExecutionPolicy Bypass -Command "irm https://github.com/jiovannish/client/releases/latest/download/install.ps1 | iex"

The installers verify archive checksums and preserve API keys, VM keys, and saved configuration. Windows installs into %LOCALAPPDATA%\Jio\bin and updates the user PATH; reopen CMD afterward. Enable OpenSSH Client in Windows Settings → Optional features.

Native binaries: macOS ARM64 and Intel (11+), Linux ARM64 and x86-64 (glibc 2.35+), and Windows x64. OpenSSH is required. Windows ARM64 and Alpine/musl binaries are not included.

Each archive includes the CLI, Apache-2.0 license, and dependency notices. Checksums detect download corruption; they are not independent publisher signatures. Node.js and Python SDKs remain source-build only.

Published app URLs are public; use application authentication for private content. Persistent port publication requires a compatible Server and systemd guest; older templates require republishing after restart.

CLI guide · Security · Code of Conduct

Jio Client v0.4.0

jio forward adds private TCP access to VM services such as PostgreSQL through authenticated SSH. Both the local listener and guest destination use IPv4 loopback; guest host keys remain pinned.

jio forward 5432 --local-port 15432
# In another terminal:
psql -h 127.0.0.1 -p 15432 -U <database-user> -d <database>

Keep the forward running; Ctrl-C closes it and leaves the VM and database running. --local-port avoids conflicts with a local database, and an optional session ID selects another VM. jio expose continues to publish HTTP apps through public HTTPS URLs.

Template compatibility: forwarding requires guest SSH policy that permits local TCP forwarding to 127.0.0.1. Existing templates with AllowTcpForwarding no reject connections; upgrading the client alone does not update their policy. This client release does not deploy or modify VM templates. Database authentication is still required. The existing hosted gateway has a one-hour stream limit; automatic reconnection is not provided.

Validated locally with real PostgreSQL through direct SSH, hosted-style HTTPS/SSH, and SSH jump-host aliases, including authentication failures, restricted destinations, occupied ports, disconnects and cleanup. These checks used local fixtures; native PostgreSQL inside a rebuilt Jio VM remains unverified.

Install

macOS / Linux:

curl -fsSL https://github.com/jiovannish/client/releases/latest/download/install.sh | sh

Windows (PowerShell):

irm https://github.com/jiovannish/client/releases/latest/download/install.ps1 | iex

Windows (CMD):

powershell.exe -NoProfile -ExecutionPolicy Bypass -Command "irm https://github.com/jiovannish/client/releases/latest/download/install.ps1 | iex"

The installers verify archive checksums and preserve API keys, VM keys, and saved configuration. Windows installs into %LOCALAPPDATA%\Jio\bin and updates the user PATH; reopen CMD afterward. Enable OpenSSH Client in Windows Settings → Optional features.

Native binaries: macOS ARM64 and Intel (11+), Linux ARM64 and x86-64 (glibc 2.35+), and Windows x64. OpenSSH is required. Windows ARM64 and Alpine/musl binaries are not included.

Each archive includes the CLI, Apache-2.0 license, and dependency notices. Checksums detect download corruption; they are not independent publisher signatures. Node.js and Python SDKs remain source-build only.

Published app URLs are public; use application authentication for private content. Persistent port publication requires a compatible Server and systemd guest; older templates require republishing after restart.

CLI guide · Security · Code of Conduct

Jio Client v0.3.1

jio ports now prints No exposed ports. when the current or specified VM has no published ports.

Install

macOS / Linux:

curl -fsSL https://github.com/jiovannish/client/releases/latest/download/install.sh | sh

Windows (PowerShell):

irm https://github.com/jiovannish/client/releases/latest/download/install.ps1 | iex

Windows (CMD):

powershell.exe -NoProfile -ExecutionPolicy Bypass -Command "irm https://github.com/jiovannish/client/releases/latest/download/install.ps1 | iex"

The installers verify archive checksums and preserve API keys, VM keys, and saved configuration. Windows installs into %LOCALAPPDATA%\Jio\bin and updates the user PATH; reopen CMD afterward. Enable OpenSSH Client in Windows Settings → Optional features.

Native binaries: macOS ARM64 and Intel (11+), Linux ARM64 and x86-64 (glibc 2.35+), and Windows x64. OpenSSH is required. Windows ARM64 and Alpine/musl binaries are not included.

Each archive includes the CLI, Apache-2.0 license, and dependency notices. Checksums detect download corruption; they are not independent publisher signatures. Node.js and Python SDKs remain source-build only.

Published app URLs are public; use application authentication for private content. Persistent port publication requires a compatible Server and systemd guest; older templates require republishing after restart.

CLI guide · Security · Code of Conduct

Jio Client v0.3.0

Clone a running VM with jio fork, preserving its processes and files.

• Fork the current VM or pass a source ID; the child gets a new VM ID and network address.
• Preserve local SSH credentials before sending the fork request, including when the response is lost.
• Reuse HTTP connections across session operations.

Fork requires a compatible Server and worker, local source credentials, and capacity for a second VM. It stays on the same worker and currently supports non-expiring accounts only. Application credentials and SSH keys are inherited; external connections may need to reconnect.

Install

macOS / Linux:

curl -fsSL https://github.com/jiovannish/client/releases/latest/download/install.sh | sh

Windows (PowerShell):

irm https://github.com/jiovannish/client/releases/latest/download/install.ps1 | iex

Windows (CMD):

powershell.exe -NoProfile -ExecutionPolicy Bypass -Command "irm https://github.com/jiovannish/client/releases/latest/download/install.ps1 | iex"

The installers verify archive checksums and preserve API keys, VM keys, and saved configuration. Windows installs into %LOCALAPPDATA%\Jio\bin and updates the user PATH; reopen CMD afterward. Enable OpenSSH Client in Windows Settings → Optional features.

Native binaries: macOS ARM64 and Intel (11+), Linux ARM64 and x86-64 (glibc 2.35+), and Windows x64. OpenSSH is required. Windows ARM64 and Alpine/musl binaries are not included.

Each archive includes the CLI, Apache-2.0 license, and dependency notices. Checksums detect download corruption; they are not independent publisher signatures. Node.js and Python SDKs remain source-build only.

Published app URLs are public; use application authentication for private content. Persistent port publication requires a compatible Server and systemd guest; older templates require republishing after restart.

CLI guide · Security · Code of Conduct

Jio Client v0.2.4

Keep newly created VMs selected when confirmation input fails.

• Pasting an oversized answer into a confirmation prompt now asks again instead of aborting.
• Finish saving an accepted VM before returning a connect-prompt input/output error, so it remains available to jio connect and jio destroy.

Install

macOS / Linux:

curl -fsSL https://github.com/jiovannish/client/releases/latest/download/install.sh | sh

Windows (PowerShell):

irm https://github.com/jiovannish/client/releases/latest/download/install.ps1 | iex

Windows (CMD):

powershell.exe -NoProfile -ExecutionPolicy Bypass -Command "irm https://github.com/jiovannish/client/releases/latest/download/install.ps1 | iex"

The installers verify archive checksums and preserve API keys, VM keys, and saved configuration. Windows installs into %LOCALAPPDATA%\Jio\bin and updates the user PATH; reopen CMD afterward. Enable OpenSSH Client in Windows Settings → Optional features.

Native binaries: macOS ARM64 and Intel (11+), Linux ARM64 and x86-64 (glibc 2.35+), and Windows x64. OpenSSH is required. Windows ARM64 and Alpine/musl binaries are not included.

Each archive includes the CLI, Apache-2.0 license, and dependency notices. Checksums detect download corruption; they are not independent publisher signatures. Node.js and Python SDKs remain source-build only.

Published app URLs are public; use application authentication for private content. Persistent port publication requires a compatible Server and systemd guest; older templates require republishing after restart.

CLI guide · Security · Code of Conduct

Jio Client v0.2.3

X-Large selection and cleaner terminal behavior in jio config.

• Add X-Large (8 vCPU, 16 GiB) to the size menu, subject to endpoint availability and account quota.
• Restore the cursor to the start of the prompt when closing the menu, without leaving blank lines or erasing terminal history.

Install

macOS / Linux:

curl -fsSL https://github.com/jiovannish/client/releases/latest/download/install.sh | sh

Windows (PowerShell):

irm https://github.com/jiovannish/client/releases/latest/download/install.ps1 | iex

Windows (CMD):

powershell.exe -NoProfile -ExecutionPolicy Bypass -Command "irm https://github.com/jiovannish/client/releases/latest/download/install.ps1 | iex"

The installers verify archive checksums and preserve API keys, VM keys, and saved configuration. Windows installs into %LOCALAPPDATA%\Jio\bin and updates the user PATH; reopen CMD afterward. Enable OpenSSH Client in Windows Settings → Optional features.

Native binaries: macOS ARM64 and Intel (11+), Linux ARM64 and x86-64 (glibc 2.35+), and Windows x64. OpenSSH is required. Windows ARM64 and Alpine/musl binaries are not included.

Each archive includes the CLI, Apache-2.0 license, and dependency notices. Checksums detect download corruption; they are not independent publisher signatures. Node.js and Python SDKs remain source-build only.

Published app URLs are public; use application authentication for private content. Persistent port publication requires a compatible Server and systemd guest; older templates require republishing after restart.

CLI guide · Security · Code of Conduct

Jio Client v0.2.2

Clearer command discovery and Bun-based client tooling.

• Keep jio run available for compatible lab endpoints, while hiding it from the main help and command suggestions.
• Explain that jio run is unsupported on hosted Jio and direct users to jio create and jio exec.
• Simplify status wording in CLI messages and documentation while retaining the documented limitations.
• Use Bun and TypeScript for repository tooling, packaging scripts and Node SDK checks.

Install

macOS / Linux:

curl -fsSL https://github.com/jiovannish/client/releases/latest/download/install.sh | sh

Windows (PowerShell):

irm https://github.com/jiovannish/client/releases/latest/download/install.ps1 | iex

Windows (CMD):

powershell.exe -NoProfile -ExecutionPolicy Bypass -Command "irm https://github.com/jiovannish/client/releases/latest/download/install.ps1 | iex"

The installers verify archive checksums and preserve API keys, VM keys, and saved configuration. Windows installs into %LOCALAPPDATA%\Jio\bin and updates the user PATH; reopen CMD afterward. Enable OpenSSH Client in Windows Settings → Optional features.

Native binaries: macOS ARM64 and Intel (11+), Linux ARM64 and x86-64 (glibc 2.35+), and Windows x64. OpenSSH is required. Windows ARM64 and Alpine/musl binaries are not included.

Each archive includes the CLI, Apache-2.0 license, and dependency notices. Checksums detect download corruption; they are not independent publisher signatures. Node.js and Python SDKs remain source-build only.

Published app URLs are public; use application authentication for private content. Persistent port publication requires a compatible Server and systemd guest; older templates require republishing after restart.

CLI guide · Security · Code of Conduct

Jio Client v0.2.1

Native Windows support and Ubuntu compatibility fixes.

• Install on Windows x64 from PowerShell or CMD, using Windows OpenSSH. No WSL is required.
• Publish multiple VM ports without exhausting the small temporary filesystem in older Ubuntu templates.
• On systemd templates with a renewal-capable Server, supervise each published port with a service that reconnects after a clean restart.
• Use the guest home directory for jio yolo codex, accept shutdown reasons, and allow more time for clean stop and deletion.

Install

macOS / Linux:

curl -fsSL https://github.com/jiovannish/client/releases/latest/download/install.sh | sh

Windows (PowerShell):

irm https://github.com/jiovannish/client/releases/latest/download/install.ps1 | iex

Windows (CMD):

powershell.exe -NoProfile -ExecutionPolicy Bypass -Command "irm https://github.com/jiovannish/client/releases/latest/download/install.ps1 | iex"

The installers verify archive checksums and preserve API keys, VM keys, and saved configuration. Windows installs into %LOCALAPPDATA%\Jio\bin and updates the user PATH; reopen CMD afterward. Enable OpenSSH Client in Windows Settings → Optional features.

Native binaries: macOS ARM64 and Intel (11+), Linux ARM64 and x86-64 (glibc 2.35+), and Windows x64. OpenSSH is required. Windows ARM64 and Alpine/musl binaries are not included.

Each archive includes the CLI, Apache-2.0 license, and dependency notices. Checksums detect download corruption; they are not independent publisher signatures. Node.js and Python SDKs remain source-build only.

Jio remains experimental. Published app URLs are public; use application authentication for private content. Persistent port publication requires a compatible Server and systemd guest; older templates require republishing after restart.

CLI guide · Security · Code of Conduct

Jio Client v0.2.0

Adds jio expose, jio unexpose, jio ports and jio domains for HTTP apps,
SSE and WebSockets. A detached guest helper supports apps bound to localhost and
keeps publication active after the local terminal closes. Custom domains use DNS
ownership verification and automatic HTTPS, alongside the default Jio URL.

Requires an ingress-enabled Server and matching Linux helper release. Stop/start
requires republishing. This remains an experimental CLI release.

Install

curl -fsSL https://github.com/jiovannish/client/releases/latest/download/install.sh | sh

The installer verifies the archive's SHA-256 checksum and replaces only the CLI binary. It
does not change API keys, VM keys, shell startup files or saved configuration.
The installer uses ~/.local/bin when it is on PATH, otherwise /usr/local/bin
when writable or accessible with passwordless sudo. If neither is available, it
uses ~/.local/bin and prints an export PATH=... command. License notices are
installed under ../share/jio relative to the install directory.

Native binaries: macOS ARM64 and Intel (11+), Linux ARM64 and x86-64 (glibc 2.35+).
OpenSSH (ssh and ssh-keygen) is required for VM access. Windows and Alpine/musl
are not supported by these binaries. Linux client support does not imply ARM
support for the VM host runtime.

Run jio login '<your-api-key>', then jio usage, jio create, jio list and
jio connect. Account quotas, session expiry and available sizes are enforced by
the service. Exiting a shell does not destroy the VM; use jio destroy to remove it.

Source is attached by GitHub for this exact tag. Each archive contains the CLI,
Apache license and bundled dependency notices. Checksums detect corrupted
downloads; they are not independent signatures of the publisher.

The npm and Python SDKs remain source-build only in this release.

Documentation

CLI guide · Security · Code of Conduct

Jio Client v0.1.2

Fixes the unclear No such file or directory error when jio create cannot
run ssh-keygen. The error now names the missing command and explains that
OpenSSH must be installed and available on PATH. The CLI guide includes
installation commands for Arch Linux and Ubuntu/Debian.

This remains an experimental CLI release. Account quotas, session lifetimes,
and VM host trust requirements are unchanged.

Install

curl -fsSL https://github.com/jiovannish/client/releases/latest/download/install.sh | sh

The installer verifies the archive's SHA-256 checksum and replaces only the CLI binary. It
does not change API keys, VM keys, shell startup files or saved configuration.
The installer uses ~/.local/bin when it is on PATH, otherwise /usr/local/bin
when writable or accessible with passwordless sudo. If neither is available, it
uses ~/.local/bin and prints an export PATH=... command. License notices are
installed under ../share/jio relative to the install directory.

Native binaries: macOS ARM64 and Intel (11+), Linux ARM64 and x86-64 (glibc 2.35+).
OpenSSH (ssh and ssh-keygen) is required for VM access. Windows and Alpine/musl
are not supported by these binaries. Linux client support does not imply ARM
support for the VM host runtime.

Run jio login '<your-api-key>', then jio usage, jio create, jio list and
jio connect. Account quotas, session expiry and available sizes are enforced by
the service. Exiting a shell does not destroy the VM; use jio destroy to remove it.

Source is attached by GitHub for this exact tag. Each archive contains the CLI,
Apache license and bundled dependency notices. Checksums detect corrupted
downloads; they are not independent signatures of the publisher.

The npm and Python SDKs remain source-build only in this release.

Documentation

CLI guide · Security · Code of Conduct