Docs
Refer a friend. Get a weekly-quota reset.Friend signs up and uses it → +1 reset (valid 30 days) · up to 10% cash back on their spend.
+1 resetGenerate link

Installation, PATH and uninstall

Inspect the actual installation path and preserve configuration and sessions during maintenance.

Identify the installation

Use command -v wrok and command -v crabcode on Unix, or Get-Command wrok, crabcode in PowerShell, then inspect --version. Desktop packages, the wrok Code CLI and the independent wrok Code TUI are different installations.

Script locations

PlatformOfficial CLI location
macOS/Linux${CRABCODE_HOME:-$HOME/.crabcode}/bin
WindowsCRABCODE_HOME, otherwise %LOCALAPPDATA%\CrabCode

When a new shell cannot find the command, verify the actual directory before updating PATH. Do not copy a historical location from another installer.

bash
command -v crabcode
crabcode --version
command -v crabcode
crabcode --version
powershell
Get-Command crabcode
crabcode --version
Get-Command crabcode
crabcode --version

The v1.1.32 installer adds wrok/wrokcode aliases without overwriting an existing same-name file. The original command remains useful for diagnostics.

Configuration

Default user configuration and sessions live under ~/.crabcode. CRABCODE_CONFIG_DIR and CRABCODE_HOME have different configuration/runtime and installation roles. Record existing custom values before investigating a failure; an empty directory is not recovered data.

Upgrade and uninstall

Use the same official source. Older macOS CLI installations need one installer rerun to reach 1.1.32. Use the desktop updater or official package for GUI upgrades.

Exit the application and tasks before uninstalling. Use Windows' registered uninstaller for the GUI; removing a macOS app bundle does not remove user data. For script installs, inspect the installation inventory before removing the program directory and its PATH entry.

Keep ~/.crabcode and custom data directories if retaining settings. Deleting personal data is separate: export required sessions, knowledge, skills and settings first, and revoke remaining provider authorizations. Do not use broad home-directory cleanup commands.