ocx self

​

Overview

​

Self Update

​

Usage

ocx self update [options]

​

Flags

​

Examples

# Update to latest version
ocx self update

# Force reinstall via npm
ocx self update --method npm --force

​

How It Works

• curl-installed binaries: Downloads from GitHub releases with SHA256 verification.
• npm/pnpm/bun installs: Uses the respective package manager’s global install command.

​

Self Uninstall

​

Usage

ocx self uninstall [options]

​

Flags

​

What Gets Removed

• ~/.config/opencode/profiles/ — All profiles
• ~/.config/opencode/ocx.jsonc — Global OCX config
• ~/.config/opencode/ — Root directory (only if empty after cleanup)
• Binary executable (for curl installs only; package-managed installs print the removal command)

​

Exit Codes

​

Examples

# Preview what would be removed
ocx self uninstall --dry-run

# Remove OCX installation
ocx self uninstall

​

Notes

• Package-managed installs: If installed via npm/pnpm/bun/yarn, the command removes config files but prints the package manager removal command instead of deleting the binary directly.
• Safety: Only removes known OCX files (allowlist approach). Unexpected files in the config directory are left untouched.
• Symlinks: Symlinks are unlinked without following. Symlink targets are preserved.
• Idempotent: Safe to run multiple times. Returns success if already uninstalled.

​

See Also

• Installation — How to install OCX.
• CLI Reference — All commands.