claude-bridge-setup

claude-bridge-setup — Live-data activation

The v0.9.0+ live-data architecture requires two additions to ~/.claude/settings.json:

1. statusLine wrapper — writes CC per-render stdin JSON to ~/.claude-bridge/live/statusline.json. Optional passthrough to user's original statusLine.
2. PostToolUse hook — calls Anthropic OAuth /api/oauth/usage (throttled ~1/min) as fallback rate-limits source. Writes to ~/.claude-bridge/live/oauth-api.json.

Without at least one, peer_context_status and rate_limit_status return hasLiveData: false with a setupPointer.

Auto-setup path (recommended)

The plugin's bundled SessionStart hook (setup-check.cjs) does most of this for you:

• Detects the newest installed plugin version in cache dir
• Refreshes stable symlinks at ~/.claude/claude-bridge-{statusline,refresh-limits}.cjs
• Auto-generates a wrapper script at ~/.claude/claude-bridge-statusline-wrapper.sh that preserves any pre-existing statusLine command as passthrough
• Prints a banner on stderr with copy-paste snippets when setup is incomplete

If you saw a banner starting with ━━━ claude-bridge vX.Y.Z setup ━━━, follow its instructions. Otherwise apply the manual steps below.

Manual setup

Step 1 — statusLine wrapper

Edit ~/.claude/settings.json:

{
  "statusLine": {
    "type": "command",
    "command": "~/.claude/claude-bridge-statusline-wrapper.sh"
  }
}

The wrapper script is auto-generated by the plugin's SessionStart hook on first run. If it doesn't exist yet, restart Claude Code once, then verify with:

cat ~/.claude/claude-bridge-statusline-wrapper.sh

Step 2 — PostToolUse hook

Add to the same settings.json:

{
  "hooks": {
    "PostToolUse": [{
      "matcher": ".*",
      "hooks": [{
        "type": "command",
        "command": "node ~/.claude/claude-bridge-refresh-limits.cjs",
        "timeout": 6
      }]
    }]
  }
}

If PostToolUse already exists in your settings.json, merge into the existing array — don't replace.