Skip to content

install-feedback-20260220.md

Latest commit

 

History

History
61 lines (43 loc) · 3.14 KB

install-feedback-20260220.md

File metadata and controls

61 lines (43 loc) · 3.14 KB
Raw

Installation Feedback Report

Environment

  • Date: 2026-02-20
  • Target Version: v2.14.0 (installed from main branch)
  • OS: Linux 2c3f60c4506f 6.18.10-100.fc42.x86_64 #1 SMP PREEMPT_DYNAMIC Wed Feb 11 16:15:47 UTC 2026 x86_64 GNU/Linux
  • Python Version: Python 3.11.2
  • Default Python Path: /usr/bin/python3
  • Project Path: /workspace
  • Project Path Length: 10 characters

Installation Method

  • Automated (install.sh via curl)
  • Manual (step-by-step)

Results

  • Overall: SUCCESS
  • Daemon Status: RUNNING

Step-by-Step Log

  1. Pre-flight checks: Checked for existing .claude/hooks-daemon/ - none found.
  2. Prerequisites (git, python, uv): git found, Python 3.11.2 confirmed. uv not installed but installer downloaded and installed it automatically.
  3. Repository clone: Cloned from https://github.com/Edmonds-Commerce-Limited/claude-code-hooks-daemon.git (main branch) to .claude/hooks-daemon/. Success.
  4. Venv creation: Created at .claude/hooks-daemon/untracked/venv using uv. 13 packages installed including claude-code-hooks-daemon v2.14.0. Success.
  5. Config generation: Deployed 11 hook scripts to .claude/hooks/. Container/YOLO mode auto-detected.
  6. Hook deployment: settings.json, hooks-daemon.env, hooks-daemon.yaml all deployed. Success.
  7. gitignore setup: .claude/.gitignore auto-created with daemon exclusion entries. Root .gitignore updated. Success.
  8. Daemon start: PID 679, socket at .claude/hooks-daemon/untracked/daemon-2c3f60c4506f.sock. Success.
  9. Post-install validation: All checks passed.

Verification Tests

  • git reset --hard HEAD → BLOCKED (deny) ✅
  • sed -i s/foo/bar/ file.txt → BLOCKED (deny) ✅
  • ls -la → ALLOWED (empty response) ✅
  • Daemon status: RUNNING ✅

Issues Encountered

  1. Issue: handler_status.py reads from .claude/hooks-daemon/.claude/hooks-daemon.yaml (internal template) rather than the deployed project config at .claude/hooks-daemon.yaml, causing it to show "0 enabled handlers" even though handlers are active. Severity: Minor / Cosmetic Workaround: Tested hooks manually to confirm they work despite misleading status report output. Suggestion: handler_status.py should accept a --config flag to specify the project config path, or auto-detect the correct config.

Documentation Gaps

  1. The handler_status.py script reads the wrong config path and displays misleading "0 enabled" output. The LLM-INSTALL.md post-install step 12 says to run handler_status.py, but its output is confusing when it reads from the internal template config.

Suggestions

  1. Auto-detect project config in handler_status.py (look for .claude/hooks-daemon.yaml two levels up from hooks-daemon/).
  2. The pre-installation check bash script uses array syntax in parentheses that fails in some bash environments (the find command with multiple conditions).

Warnings & Anomalies

  • Some handlers showed "ProjectContext not initialized" errors in handler_status.py output - these are non-blocking and only affect the status report display.
  • Skills deployed to .claude/skills/hooks-daemon/ (not mentioned in directory structure diagram).