hooks
remoteclaw hooks
Manage agent hooks (event-driven automations for commands like /new, /reset, and gateway startup).
Related:
List All Hooks
remoteclaw hooks listList all discovered hooks from workspace, managed, and bundled directories.
Options:
--eligible: Show only eligible hooks (requirements met)--json: Output as JSON-v, --verbose: Show detailed information including missing requirements
Example output:
Hooks (2/2 ready)
Ready: π boot β - Run boot prompt on gateway startup π command-logger β - Log all command events to a centralized audit fileExample (verbose):
remoteclaw hooks list --verboseShows missing requirements for ineligible hooks.
Example (JSON):
remoteclaw hooks list --jsonReturns structured JSON for programmatic use.
Get Hook Information
remoteclaw hooks info <name>Show detailed information about a specific hook.
Arguments:
<name>: Hook name (e.g.,command-logger)
Options:
--json: Output as JSON
Example:
remoteclaw hooks info command-loggerOutput:
π command-logger β Ready
Log all command events to a centralized audit file
Details: Source: remoteclaw-bundled Path: /path/to/remoteclaw/hooks/bundled/command-logger/HOOK.md Handler: /path/to/remoteclaw/hooks/bundled/command-logger/handler.ts Homepage: https://docs.remoteclaw.org/automation/hooks#command-logger Events: commandCheck Hooks Eligibility
remoteclaw hooks checkShow summary of hook eligibility status (how many are ready vs. not ready).
Options:
--json: Output as JSON
Example output:
Hooks Status
Total hooks: 4Ready: 4Not ready: 0Enable a Hook
remoteclaw hooks enable <name>Enable a specific hook by adding it to your config (~/.remoteclaw/config.json).
Note: Hooks managed by plugins show plugin:<id> in remoteclaw hooks list and
canβt be enabled/disabled here. Enable/disable the plugin instead.
Arguments:
<name>: Hook name (e.g.,command-logger)
Example:
remoteclaw hooks enable command-loggerOutput:
β Enabled hook: π command-loggerWhat it does:
- Checks if hook exists and is eligible
- Updates
hooks.internal.entries.<name>.enabled = truein your config - Saves config to disk
After enabling:
- Restart the gateway so hooks reload (menu bar app restart on macOS, or restart your gateway process in dev).
Disable a Hook
remoteclaw hooks disable <name>Disable a specific hook by updating your config.
Arguments:
<name>: Hook name (e.g.,command-logger)
Example:
remoteclaw hooks disable command-loggerOutput:
βΈ Disabled hook: π command-loggerAfter disabling:
- Restart the gateway so hooks reload
Install Hooks
remoteclaw hooks install <path-or-spec>remoteclaw hooks install <npm-spec> --pinInstall a hook pack from a local folder/archive or npm.
Npm specs are registry-only (package name + optional version/tag). Git/URL/file
specs are rejected. Dependency installs run with --ignore-scripts for safety.
What it does:
- Copies the hook pack into
~/.remoteclaw/hooks/<id> - Enables the installed hooks in
hooks.internal.entries.* - Records the install under
hooks.internal.installs
Options:
-l, --link: Link a local directory instead of copying (adds it tohooks.internal.load.extraDirs)--pin: Record npm installs as exact resolvedname@versioninhooks.internal.installs
Supported archives: .zip, .tgz, .tar.gz, .tar
Examples:
# Local directoryremoteclaw hooks install ./my-hook-pack
# Local archiveremoteclaw hooks install ./my-hook-pack.zip
# NPM packageremoteclaw hooks install @remoteclaw/my-hook-pack
# Link a local directory without copyingremoteclaw hooks install -l ./my-hook-packUpdate Hooks
remoteclaw hooks update <id>remoteclaw hooks update --allUpdate installed hook packs (npm installs only).
Options:
--all: Update all tracked hook packs--dry-run: Show what would change without writing
When a stored integrity hash exists and the fetched artifact hash changes,
RemoteClaw prints a warning and asks for confirmation before proceeding. Use
global --yes to bypass prompts in CI/non-interactive runs.
Bundled Hooks
session-memory (removed)
The session-memory hook has been removed.
bootstrap-extra-files (removed)
The bootstrap-extra-files hook has been removed.
command-logger
Logs all command events to a centralized audit file.
Enable:
remoteclaw hooks enable command-loggerOutput: ~/.remoteclaw/logs/commands.log
View logs:
# Recent commandstail -n 20 ~/.remoteclaw/logs/commands.log
# Pretty-printcat ~/.remoteclaw/logs/commands.log | jq .
# Filter by actiongrep '"action":"new"' ~/.remoteclaw/logs/commands.log | jq .See: command-logger documentation
boot
Runs the configured boot prompt when the gateway starts (after channels start).
Events: gateway:startup
Enable:
remoteclaw hooks enable bootSee: boot documentation