Uninstall
Two paths:- Easy path if
crocbotis still installed. - Manual service removal if the CLI is gone but the service is still running.
Easy path (CLI still installed)
Recommended: use the built-in uninstaller:- Stop the gateway service:
- Uninstall the gateway service (launchd/systemd/schtasks):
- Delete state + config:
CROCBOT_CONFIG_PATH to a custom location outside the state dir, delete that file too.
- Delete your workspace (optional, removes agent files):
- Remove the CLI install (pick the one you used):
- If you used profiles (
--profile/CROCBOT_PROFILE), repeat step 3 for each state dir (defaults are~/.crocbot-<profile>). - In remote mode, the state dir lives on the gateway host, so run steps 1-4 there too.
Manual service removal (CLI not installed)
Use this if the gateway service keeps running butcrocbot is missing.
macOS (launchd)
Default label iscom.crocbot.gateway (or com.crocbot.<profile>):
com.crocbot.<profile>.
Linux (systemd user unit)
Default unit name iscrocbot-gateway.service (or crocbot-gateway-<profile>.service):
Windows (Scheduled Task)
Default task name iscrocbot Gateway (or crocbot Gateway (<profile>)).
The task script lives under your state dir.
~\.crocbot-<profile>\gateway.cmd.
Normal install vs source checkout
Normal install (install.sh / npm / pnpm / bun)
If you usedhttps://github.com/moshehbenavraham/crocbot/install.sh or install.ps1, the CLI was installed with npm install -g crocbot@latest.
Remove it with npm rm -g crocbot (or pnpm remove -g / bun remove -g if you installed that way).
Source checkout (git clone)
If you run from a repo checkout (git clone + crocbot ... / bun run crocbot ...):
- Uninstall the gateway service before deleting the repo (use the easy path above or manual service removal).
- Delete the repo directory.
- Remove state + workspace as shown above.
