An update focused on local deployments — run UDFs locally, manage several deployments at once, and cleaner output for scripts and agents. 
Script Language Containers, Locally — NEW!
Local deployments can now run UDFs. Install an official SLC and the language just works — no manual setup. Manage them with `install`, `list`, `update`, and `remove`.
Example: exasol slc install python3 makes PYTHON3 UDFs work; exasol slc list shows what’s installed.
Named Deployments
Address a deployment by name from anywhere with --deployment / -d, and list them all with exasol deployments list. Named deployments live under ~/.exasol/personal/deployments/<name>/. Prefer full control? Path-based deployments with --deployment-dir still work.
Example: exasol status -d demo
Local Diagnostics & Clearer Errors
exasol diag local prints a JSON snapshot — VM status, guest IP, bound host ports, per-port reachability, and database readiness — and is safe to run whether or not the deployment is up. Network-reachability and blocked-state errors now point you at the actual problem.
A Consistent Output Contract
Primary output stays on stdout (and is the only thing on stdout under --json), while notices, prompts, and next-step guidance go to stderr. Agents and scripts get clean, machine-readable output; humans still get the guidance.
Fixes worth noting
exasol connect now ends CREATE SCRIPT / CREATE FUNCTION on a line containing only /, so UDF bodies with semicolons run correctly via -c, -f, and interactively. Local deployments also no longer get stuck in operation_in_progress after a failed start or stop.
Get started
curl ``https://www.exasol.com/install/`` | sh
