Files
claude-code-monitor/.claude/hooks/README.md
felix.zoesch 4582ead572 Add config file support for hook backend URL
Hooks now read backend URL from ~/.claude/monitor_url config file,
making it easier to configure for remote/VM deployments without
relying on environment variables.

Priority order:
1. Config file (~/.claude/monitor_url)
2. Environment variable (CLAUDE_MONITOR_URL)
3. Default (http://localhost:8000)

This fixes the issue where Claude Code doesn't see environment
variables when not started from a configured shell.

Usage:
  echo "http://your-vm:8000" > ~/.claude/monitor_url
  cp .claude/hooks/*.sh ~/.claude/hooks/
  chmod +x ~/.claude/hooks/*.sh

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
2025-12-16 08:06:14 +01:00

122 lines
2.7 KiB
Markdown

# Claude Code Monitor Hooks
These hooks capture Claude Code events and send them to the monitoring backend.
## Installation
### Local Installation (localhost)
```bash
# Copy hooks to Claude Code directory
cp .claude/hooks/*.sh ~/.claude/hooks/
# Make hooks executable
chmod +x ~/.claude/hooks/*.sh
```
The hooks will automatically use `http://localhost:8000` as the backend URL.
### Remote/VM Installation
**Method 1: Config File (Recommended)**
Create a config file with your backend URL:
```bash
# Set backend URL in config file
echo "http://your-vm-ip:8000" > ~/.claude/monitor_url
# Or for specific domain
echo "http://monitor.example.com:8000" > ~/.claude/monitor_url
# Copy and enable hooks
cp .claude/hooks/*.sh ~/.claude/hooks/
chmod +x ~/.claude/hooks/*.sh
```
**Method 2: Environment Variable**
For remote installations, set the `CLAUDE_MONITOR_URL` environment variable:
```bash
# Add to your shell profile (~/.bashrc, ~/.zshrc, etc.)
export CLAUDE_MONITOR_URL="http://your-vm-ip:8000"
# IMPORTANT: Restart terminal or run
source ~/.bashrc
# Then copy and enable hooks
cp .claude/hooks/*.sh ~/.claude/hooks/
chmod +x ~/.claude/hooks/*.sh
```
**Priority Order:**
1. Config file (`~/.claude/monitor_url`) - highest priority
2. Environment variable (`CLAUDE_MONITOR_URL`)
3. Default (`http://localhost:8000`)
### Docker Deployment Examples
```bash
# Backend on port 8000
echo "http://192.168.1.100:8000" > ~/.claude/monitor_url
# Backend via nginx on port 3000
echo "http://192.168.1.100:3000" > ~/.claude/monitor_url
# With domain
echo "http://monitor.example.com:8000" > ~/.claude/monitor_url
```
## Verification
Test if hooks are working:
```bash
# Check if environment variable is set
echo $CLAUDE_MONITOR_URL
# Manually test a hook
echo '{"session_id":"test","timestamp":1234567890}' | ~/.claude/hooks/session_start.sh
# Check backend logs for the test event
curl http://your-backend:8000/api/events | jq
```
## Available Hooks
- `pre_tool_use.sh` - Before tool execution
- `post_tool_use.sh` - After tool execution
- `user_prompt.sh` - When user submits a prompt
- `session_start.sh` - Session initialization
- `session_end.sh` - Session termination
- `subagent_stop.sh` - Agent completion
## Troubleshooting
### No events appearing in dashboard
1. Check if `CLAUDE_MONITOR_URL` is set correctly:
```bash
echo $CLAUDE_MONITOR_URL
```
2. Verify backend is reachable:
```bash
curl $CLAUDE_MONITOR_URL/health
```
3. Check hook permissions:
```bash
ls -la ~/.claude/hooks/*.sh
```
4. Test hook manually:
```bash
echo '{"session_id":"test","timestamp":1234567890}' | ~/.claude/hooks/session_start.sh
```
### Events only work locally
Make sure to set `CLAUDE_MONITOR_URL` in your shell profile and restart your terminal.