Spencer Bull
5345673988
OpenClaw's desktop experience on Linux is its Control UI, served by the gateway the openclaw package runs, so the Install > AI entry installs the package and a web app launcher that routes through the new omarchy-launch-openclaw: first launch hands off to OpenClaw's own onboarding wizard, later launches start the gateway when needed and open the dashboard's single-use browser handoff URL as an app window. Remove > AI tears the gateway service down through OpenClaw's own gateway uninstall (falling back to systemctl by hand), aborts rather than dropping the package under a gateway that will not stop, and keeps the user's agent in ~/.openclaw. OpenClaw also joins Setup > Defaults > Agent through the same agent_installer seam Hermes carries: its CLI is the pacman package rather than a mise tool, so omarchy-install-openclaw-cli answers --check/--now with pacman, and omarchy-agent runs `openclaw chat`, seeding prompts through --message. The menu mark is a new U+E90C glyph traced from the package's lobster favicon; E90B stays free for the Perplexity mark still in flight on its own branch. The launcher recovers the gateway through `openclaw gateway install --force` (unit not enabled: missing, or an install that died after writing it) or `openclaw gateway start` (enabled but stopped), never `openclaw dashboard --yes`: as of OpenClaw 2026.9.1 that defers to "the owning supervisor" in both cases, and once the gateway is up it copies a one-time browser pairing URL into the clipboard. The dashboard probe is bounded so an app-grid launch cannot hang without a terminal to interrupt it. Removal treats only systemd's own "inactive"/"failed" as a stopped gateway, so an unreachable user manager aborts instead of dropping the package under a live process. All of it verified against a real 2026.9.1 install. Removal also takes down the node-host unit if OpenClaw ever installed one, and asks (default no, only on a terminal) whether ~/.openclaw should go too, with its size: the chats and credentials live there next to hundreds of megabytes of plugin runtimes and cache OpenClaw downloads for itself. Onboarding goes through omarchy-openclaw-onboard rather than bare `openclaw onboard`: as of 2026.9.1 the bare command is the guided flow, which ends by running a foreground gateway and handing off to a browser tab without returning, so the install script never reached the app launch and no service was installed. The helper runs the classic wizard (--flow quickstart --install-daemon --skip-ui) as a background job that keeps the terminal as its stdin, so its prompts render and take input as upstream draws them, and stops it once the gateway answers: upstream leaves the wizard running after its outro (only the TUI branch exits, and the model sign-in holds a socket open). Every quickstart prompt precedes the service install, so that point is safe. A gateway that never comes up after this run applies setup ends the wait as a failure instead of hanging, an already-running OpenClaw is left alone rather than mistaken for this run's success, a gateway answering on the port is only this run's once its process is the unit's own MainPID (an orphan from an earlier run) is not mistaken for the service this run installs, and a signal at the helper takes the wizard down with it.
36 lines
1.4 KiB
Bash
Executable File
36 lines
1.4 KiB
Bash
Executable File
#!/bin/bash
|
|
|
|
# omarchy:summary=Install the OpenClaw agent platform and its Control UI web app
|
|
# omarchy:requires-sudo=true
|
|
|
|
set -e
|
|
|
|
echo "Installing OpenClaw..."
|
|
omarchy-pkg-add openclaw
|
|
|
|
# The desktop app is OpenClaw's Control UI: a web app served by its own
|
|
# gateway. The launcher entry goes through omarchy-launch-openclaw, which
|
|
# onboards or starts that gateway before opening the window. The icon ships
|
|
# inside the package, so nothing is fetched here.
|
|
echo "Installing the OpenClaw web app..."
|
|
omarchy-webapp-install OpenClaw "http://127.0.0.1:18789" \
|
|
/usr/lib/node_modules/openclaw/dist/control-ui/apple-touch-icon.png \
|
|
omarchy-launch-openclaw
|
|
|
|
# A first install runs onboarding right here: launching the app instead would
|
|
# open a second floating terminal for the wizard, identical to this one.
|
|
# omarchy-openclaw-onboard runs the wizard the way this flow needs (terminal
|
|
# prompts, gateway as a user service, and it actually returns). A machine
|
|
# that is already onboarded goes straight to the app.
|
|
if [[ -f $HOME/.openclaw/openclaw.json ]]; then
|
|
echo "Opening OpenClaw..."
|
|
setsid uwsm-app -- gtk-launch OpenClaw >/dev/null 2>&1 &
|
|
elif omarchy-openclaw-onboard && [[ -f $HOME/.openclaw/openclaw.json ]]; then
|
|
echo "Opening OpenClaw..."
|
|
setsid uwsm-app -- gtk-launch OpenClaw >/dev/null 2>&1 &
|
|
fi
|
|
|
|
echo ""
|
|
echo "OpenClaw has been installed."
|
|
echo "If you skipped onboarding, launching OpenClaw from the app grid resumes it."
|