Troubleshooting and support

Common issues and how to resolve them, for every install type. If none of this helps, contact Tidbit support and, if asked, turn on full-capture debug so we can see what your session is doing.

First, check status#

• Desktop or CLI (intercept): sudo bash install.sh status
• API (BYOK): bash install-byok.sh status

Status tells you the environment, the endpoint, whether the redirect is active, whether the device is paired, and (for BYOK) the base URL and masked API key.

Traffic is not routing through Tidbit#

• Intercept: restart the Claude app, or open a brand-new terminal for the CLI. The change only takes effect on a fresh launch or shell.
• Intercept: check the redirect is active in install.sh status. If it shows "inactive", the watchdog may have failed over because the gateway was briefly unreachable; it restores itself once the gateway is healthy again.
• Intercept: a pre-existing ANTHROPIC_BASE_URL bypasses the redirect, since the intercept install only captures the default api.anthropic.com endpoint. The installer warns you when it detects one.
• BYOK: confirm echo "$ANTHROPIC_BASE_URL" shows https://api.usetidbit.ai in a new shell.
• BYOK: for Claude Code specifically, ~/.claude/settings.json’s env block overrides your shell exports. Re-run the installer with --write-settings if a base URL there is winning.

Pairing failed or timed out#

• The pairing code is single-use and expires after about 10 minutes. Re-run sudo bash install.sh pair-link for a fresh one.
• The confirm page needs you signed in to Tidbit, and two-factor if your account enforces it.
• "No Ed25519-capable openssl found": stock macOS ships LibreSSL, whose CLI cannot mint the device key. Install OpenSSL 3 (brew install openssl) and re-run, or set TIDBIT_OPENSSL=/path/to/openssl.
• Pairing is fail-open: if it never completes, Tidbit still works, just without your identity presented yet.

Uninstalling or disconnecting#

• Full removal, per install type: see Uninstall and unpair.
• Disconnect one machine but keep Tidbit: bash install.sh unpair, or revoke the device from your console device list.

Helping support diagnose#

By default Tidbit keeps nothing beyond what it needs to optimize. If support asks, turn on full-capture debug for your own identity so we can see the failing session, then turn it back off. It is opt-in, affects only your traffic, and stops recording the moment you turn it off.

sudo bash install.sh debug on
sudo bash install.sh debug off