Bridge Client SDK

Client-side SDK for the Session Bridge system. Provides hooks for Claude Code event injection, a background WebSocket bridge runner, and a watcher daemon that auto-responds to external chat messages when Claude Code is idle.

Install

pip install -e backend/dakb_service/bridge/Client_SDK

Architecture: Two Paths, One Inbox

Path A (User active — hook-driven):
  User types → UserPromptSubmit hook → inbox_hook.py
  → consumes inbox → injects additionalContext → Claude responds inline

Path B (Agent standby — daemon-driven):
  Message arrives → Redis notify key → Watcher Daemon (BLPOP)
  → checks no interactive session active
  → claude -p --resume SESSION_ID
  → captures response → POST /api/v1/bridge/send → external chat gets reply

Components

Hooks (bridge_client_sdk/hooks/)

Scripts

Usage

Start the watcher daemon

# Auto-discover session ID
bridge-watcher

# Or specify explicitly
bridge-watcher --session-id SESSION_ID

# With debug logging
bridge-watcher --session-id SESSION_ID --log-level DEBUG

Push a test message

bridge-test-fire "Hello from test"

Launch the WebSocket bridge

bridge-launcher SESSION_ID --chat-id telegram:-456

Dual-Response Prevention

Configuration

Edit bridge_client_sdk/config/watcher_config.json:

{
    "blpop_timeout": 30,
    "batch_delay": 2.0,
    "cooldown": 5.0,
    "lock_ttl": 120,
    "max_budget_usd": 0.50,
    "allowed_tools": "Read,Bash,Grep,Glob,WebFetch,WebSearch",
    "system_prompt": "..."
}

Hook Integration

The original hook scripts at .claude/scripts/bridge_*.py are thin shims that import from this SDK. The .claude/settings.local.json hook paths remain unchanged — they call the shims which delegate to the SDK.