Run SolonCode Without Installing: Web UI Guide

Resumo

Pixel’s announcement explains SolonCode v2026.11.15 direct run mode, which launches the Web UI at http://localhost:4808/ from bundled macOS, Linux, or Windows launchers. It highlights the portable setup, Java 8+ requirement, and behavior when the port is already in use, helping developers run SolonCode without installation or admin access.

DEV Community

Run SolonCode Without Installing It: Double-Click Into the Web UI

Run SolonCode Without Installing It: Double-Click Into the Web UI You don't have to install SolonCode to use it. In v2026.11.15, SolonCode added a no-install "direct run" mode: drop the release folder anywhere — a USB stick, a network share, a scratch directory on a borrowed machine — and double-click one of the bundled launchers. It starts the full Web interface on http://localhost:4808/ and opens your browser. No PATH registration, no installer, no admin prompt. That's the whole point of the feature. Let's look at what it actually does and where its limits sit. What "no-install" really means here The release package ships three launchers, one per platform: Platform Launcher What it does macOS / Linux run.sh Runs the bundled JAR in Web mode macOS (Finder) run.mac.command Opens in Terminal, then runs run.sh Windows run.window.cmd Runs the JAR; keeps the window open so you can read the prompt Each launcher does exactly one thing: invoke Java against the bin/soloncode-cli.jar that sits in the same folder, in web mode. The run.sh entry point is self-contained: JAR_FILE="$SCRIPT_DIR/bin/soloncode-cli.jar"
exec java -Dfile.encoding=UTF-8 ... -jar "$JAR_FILE" web
On macOS, run.mac.command exists because Finder opens a .sh file with a text editor, not Terminal — so it opens Terminal and hands off to run.sh. On Windows, run.window.cmd holds the window open after the program exits so the start message doesn't just vanish. The folder is portable. Move it to a machine that has Java 8 or newer and it runs. The launchers take no arguments and do no port probing or instance takeover: if 4808 is already in use, they report the conflict and stop — close the previous window, then start. The honest constraints Being portable means a few things to know up front, so you're not surprised: Java 8+ is required on the target machine. It supports the Java 8 → 26 range, but Java must be installed. This is a JAR, not a native binary. Data lives in the user's home directory (~/.soloncode, %USERPROFILE%.soloncode on Windows), shared with the installed version. You're not scoping a second, isolated state. macOS Gatekeeper may flag a downloaded folder. One-time fix: xattr -d com.apple.quarantine run.mac.command run.sh. The launcher is Web-only. For the interactive cli, a custom port (web 4808), and so on, you use the installed soloncode command or run java -jar bin/soloncode-cli.jar directly. Why this matters for a demo This is the scenario I'd reach for: you need to show someone what a coding agent does, or trial it in an environment where you shouldn't be touching PATH or the system install — a shared network build folder, a CI runner image, an air-gapped box, a customer's laptop for a 20-minute walkthrough. You bring a folder; they double-click; the Web console is up. Because it's the same JAR as the installed product, whatever you do in the Web UI works identically — it's not a reduced "demo build." What else is in this release A couple of smaller items worth a line: Skills and MCP connectors can now be pinned to a session or an automation task. Previously a task inherited whatever was available; now it can declare exactly which skills and connectors it uses, the same way it already declares a model. The MCP section is renamed "Connectors" across the Web UI and all 22 bundled language packs — the wording now describes what it actually is, a pluggable tool gateway. Get it Install and update scripts (Mac / Linux / Harmony PC): curl -fsSL https://solon.noear.org/soloncode/setup.sh | bash
Windows (PowerShell): irm https://solon.noear.org/soloncode/setup.ps1 | iex
Once it's on a machine, the installed soloncode web command opens the same Web console. The no-launcher path — grab the release folder, point a machine with Java 8+ at it, double-click — is now a first-class way to run it. Docs: SolonCode on the official site.
Run SolonCode Without Installing: Web UI Guide
Powered by Readybot.io

As últimas novidades de Pixel

Incident Response: Look Beyond the Red Alert

Pixel’s DEV Community announcement explores how teams can fixate on one failing service while overlooking the real cause of an outage, such as a full …

Sach: AI Fact-Checks WhatsApp Forwards in India

Pixel’s announcement introduces Sach, a tool that checks forwarded messages in English, Hindi, Telugu, and 14 other Indian languages against official sources. It gives cited …

Java 25 Removes SecurityManager: What to Fix

Pixel’s announcement explains how Java 24’s JEP 486 permanently disabled the SecurityManager, breaking test workarounds that intercept System.exit. It recommends returning exit codes or throwing …