coderclaw hooksManage agent hooks (event-driven automations for commands like /new, /reset, and gateway startup).
Related:
coderclaw hooks list
List 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 requirementsExample output:
Hooks (4/4 ready)
Ready:
π boot-md β - Run BOOT.md on gateway startup
π bootstrap-extra-files β - Inject extra workspace bootstrap files during agent bootstrap
π command-logger β - Log all command events to a centralized audit file
πΎ session-memory β - Save session context to memory when /new command is issued
Example (verbose):
coderclaw hooks list --verbose
Shows missing requirements for ineligible hooks.
Example (JSON):
coderclaw hooks list --json
Returns structured JSON for programmatic use.
coderclaw hooks info <name>
Show detailed information about a specific hook.
Arguments:
<name>: Hook name (e.g., session-memory)Options:
--json: Output as JSONExample:
coderclaw hooks info session-memory
Output:
πΎ session-memory β Ready
Save session context to memory when /new command is issued
Details:
Source: coderclaw-bundled
Path: /path/to/coderclaw/hooks/bundled/session-memory/HOOK.md
Handler: /path/to/coderclaw/hooks/bundled/session-memory/handler.ts
Homepage: https://docs.coderclaw.ai/automation/hooks#session-memory
Events: command:new
Requirements:
Config: β workspace.dir
coderclaw hooks check
Show summary of hook eligibility status (how many are ready vs. not ready).
Options:
--json: Output as JSONExample output:
Hooks Status
Total hooks: 4
Ready: 4
Not ready: 0
coderclaw hooks enable <name>
Enable a specific hook by adding it to your config (~/.coderclaw/config.json).
Note: Hooks managed by plugins show plugin:<id> in coderclaw hooks list and
canβt be enabled/disabled here. Enable/disable the plugin instead.
Arguments:
<name>: Hook name (e.g., session-memory)Example:
coderclaw hooks enable session-memory
Output:
β Enabled hook: πΎ session-memory
What it does:
hooks.internal.entries.<name>.enabled = true in your configAfter enabling:
coderclaw hooks disable <name>
Disable a specific hook by updating your config.
Arguments:
<name>: Hook name (e.g., command-logger)Example:
coderclaw hooks disable command-logger
Output:
βΈ Disabled hook: π command-logger
After disabling:
coderclaw hooks install <path-or-spec>
Install 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:
~/.coderclaw/hooks/<id>hooks.internal.entries.*hooks.internal.installsOptions:
-l, --link: Link a local directory instead of copying (adds it to hooks.internal.load.extraDirs)Supported archives: .zip, .tgz, .tar.gz, .tar
Examples:
# Local directory
coderclaw hooks install ./my-hook-pack
# Local archive
coderclaw hooks install ./my-hook-pack.zip
# NPM package
coderclaw hooks install @coderclaw/my-hook-pack
# Link a local directory without copying
coderclaw hooks install -l ./my-hook-pack
coderclaw hooks update <id>
coderclaw hooks update --all
Update installed hook packs (npm installs only).
Options:
--all: Update all tracked hook packs--dry-run: Show what would change without writingSaves session context to memory when you issue /new.
Enable:
coderclaw hooks enable session-memory
Output: ~/.coderclaw/workspace/memory/YYYY-MM-DD-slug.md
See: session-memory documentation
Injects additional bootstrap files (for example monorepo-local AGENTS.md / TOOLS.md) during agent:bootstrap.
Enable:
coderclaw hooks enable bootstrap-extra-files
See: bootstrap-extra-files documentation
Logs all command events to a centralized audit file.
Enable:
coderclaw hooks enable command-logger
Output: ~/.coderclaw/logs/commands.log
View logs:
# Recent commands
tail -n 20 ~/.coderclaw/logs/commands.log
# Pretty-print
cat ~/.coderclaw/logs/commands.log | jq .
# Filter by action
grep '"action":"new"' ~/.coderclaw/logs/commands.log | jq .
See: command-logger documentation
Runs BOOT.md when the gateway starts (after channels start).
Events: gateway:startup
Enable:
coderclaw hooks enable boot-md