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.
79 lines
3.4 KiB
Bash
Executable File
79 lines
3.4 KiB
Bash
Executable File
#!/bin/bash
|
|
|
|
# omarchy:summary=Remove the OpenClaw agent platform along with its gateway service and web app.
|
|
# omarchy:requires-sudo=true
|
|
|
|
# -u so an unset HOME is an error rather than a set of rm -rf paths rooted at /.
|
|
set -euo pipefail
|
|
|
|
unit_dir="$HOME/.config/systemd/user"
|
|
|
|
# Only systemd's own word counts as "stopped": a non-zero exit from is-active
|
|
# also covers an unreachable user manager, which says nothing about whether
|
|
# the process is alive.
|
|
unit_stopped() {
|
|
local state
|
|
state=$(systemctl --user is-active "$1" 2>/dev/null) || true
|
|
[[ $state == inactive || $state == failed ]]
|
|
}
|
|
|
|
# The user services OpenClaw installs for itself: the gateway through
|
|
# onboarding, and the node host if the user ever paired this machine to
|
|
# another gateway. OpenClaw writes them to $HOME/.config regardless of
|
|
# XDG_CONFIG_HOME, so look exactly there; no unit means nothing registered.
|
|
# Upstream's own teardown knows every piece its install wrote (unit file, the
|
|
# default.target.wants enablement symlink, the reload), so prefer it while the
|
|
# binary is still installed and fall back to doing the same by hand. A service
|
|
# that will not stop aborts the removal: dropping the package would strand the
|
|
# live process on deleted code with no way to restart it cleanly.
|
|
for unit_file in "$unit_dir"/openclaw-gateway.service "$unit_dir"/openclaw-node.service; do
|
|
[[ -f $unit_file ]] || continue
|
|
unit=${unit_file##*/}
|
|
role=${unit#openclaw-}
|
|
role=${role%.service}
|
|
if openclaw "$role" uninstall >/dev/null 2>&1 ||
|
|
systemctl --user disable --now "$unit" 2>/dev/null ||
|
|
unit_stopped "$unit"; then
|
|
# .bak is what `gateway install --force` leaves behind when it rewrites a
|
|
# unit, so it goes with the unit.
|
|
rm -f "$unit_file" "$unit_file.bak" "$unit_dir/default.target.wants/$unit"
|
|
systemctl --user daemon-reload 2>/dev/null || true
|
|
# A unit that had been failing stays listed as "not-found failed" after
|
|
# its file is gone until its failed state is reset.
|
|
systemctl --user reset-failed "$unit" 2>/dev/null || true
|
|
else
|
|
echo "Could not stop $unit; OpenClaw was not removed." >&2
|
|
exit 1
|
|
fi
|
|
done
|
|
|
|
omarchy-pkg-drop openclaw
|
|
|
|
# The web app launcher and icon omarchy-install-ai-openclaw created.
|
|
rm -f "$HOME/.local/share/applications/OpenClaw.desktop"
|
|
rm -f "$HOME/.local/share/icons/hicolor/256x256/apps/openclaw.png"
|
|
gtk-update-icon-cache "$HOME/.local/share/icons/hicolor" &>/dev/null || true
|
|
|
|
# ~/.openclaw stays unless asked: the chats, memories, and credentials in
|
|
# there are the user's agent, and finding them intact after a reinstall is the
|
|
# better surprise. But it also holds the plugin runtimes and caches OpenClaw
|
|
# downloads for itself, easily hundreds of megabytes, so the choice is put in
|
|
# front of the user with the size rather than left silent. Without a terminal
|
|
# to ask in, keeping it is the answer.
|
|
state_removed=false
|
|
if [[ -d $HOME/.openclaw && -t 0 ]] && command -v gum >/dev/null; then
|
|
size=$(du -sh "$HOME/.openclaw" 2>/dev/null | cut -f1)
|
|
if gum confirm --default=false "Also delete ~/.openclaw ($size: chats, memories, credentials, and downloaded plugins)?"; then
|
|
rm -rf "$HOME/.openclaw"
|
|
state_removed=true
|
|
fi
|
|
fi
|
|
|
|
echo ""
|
|
echo "OpenClaw has been removed."
|
|
if [[ $state_removed == true ]]; then
|
|
echo "Its chats, memories, and settings in ~/.openclaw are gone too."
|
|
elif [[ -d $HOME/.openclaw ]]; then
|
|
echo "Your agent's chats, memories, and settings are still in ~/.openclaw."
|
|
fi
|