Notify Server Management

Implementation details for managing the notification bridge server.

Important: The Plugin Root path from command context must be used for server commands. ${CLAUDE_PLUGIN_ROOT} is only available in hooks, not skill/command execution. See GitHub #9354.

Server Commands

All commands use the port from the port file (written by server on startup):

PORT=$(cat "<plugin-root>/port" 2>/dev/null)
[ -z "$PORT" ] && { echo "Server not started (no port file)"; exit 1; }

Check Status

curl -s "http://localhost:$PORT/api/status"

Start Server

Use the plugin root path from command context:

cd "<plugin-root>" && nohup bun run server >> logs/server.log 2>&1 &

Wait for ready (up to 5 seconds):

for i in 1 2 3 4 5; do curl -s "http://localhost:$PORT/api/status" >/dev/null 2>&1 && break || sleep 1; done

Stop Server

pkill -f "bun run server" 2>/dev/null || true

Global Enable/Disable

Enable Notifications

curl -s -X POST "http://localhost:$PORT/api/enable"

Disable Notifications

curl -s -X POST "http://localhost:$PORT/api/disable"

Send Test Message

curl -s -X POST "http://localhost:$PORT/api/send" \
  -H 'Content-Type: application/json' \
  -d '{"sessionId": "'$CLAUDE_SESSION_ID'", "event": "Notification", "message": "Test message from Claude Code. Your notification setup is working!"}'

Logs

Server logs: logs/YY-MM-DD.log in plugin directory.

Troubleshooting

If notifications fail:

1. Check environment variables: EMAIL_USER, EMAIL_PASS, EMAIL_RECIPIENT (or TELEGRAM_BOT_TOKEN, TELEGRAM_CHAT_ID)
2. For Gmail: Verify app password is correct (16-character), 2FA is enabled
3. Check server logs for SMTP/API errors
4. Ensure at least one channel is configured