Skip to main content

Setup & Login

For the CLI to access your consultation channels, it needs a secret key (blumnb-...) and an endpoint. Credentials are verified and then stored in ~/.bridge-agent/config.json.

There are two ways to register them.

Method 1 — login (OAuth pairing, recommended)​

Log in to TalkBridge Center in your browser and pick a brand; the CLI automatically obtains and stores a BrandWrite key.

talkbridge login

Flow:

  1. The CLI opens TalkBridge Center's /Partner/CliLogin in your browser.
  2. The partner logs in and selects a brand.
  3. TalkBridge Center displays a 5-digit code valid for 5 minutes.
  4. Enter the code in the terminal; the CLI exchanges, verifies, and stores the key.

Options: --console <URL>, --endpoint <URL>

Method 2 — setup​

(a) TUI wizard​

Run it without arguments and an interactive setup wizard (Terminal.Gui) appears.

talkbridge setup

Screen layout:

Channel
 ├─ Inbound  ▸ Kakao        (secret key · live verification via [Health check])
 └─ Outbound ▸ Discord / Slack / Webhook   (Gateway sink)
CS Features ▸ Customer Memo (SQLite / MySQL / CSV)
AI          ▸ AI Chatbot    (provider · base URL · key → model selection)
Knowledge   ▸ Ontology
  • If existing settings are present, check only the sections you want to reconfigure; unselected sections keep their existing values.
  • In the Kakao step, the [Health check] button lets you verify the key you entered immediately.
  • The AI step queries GET /v1/models for the actual model list so you can choose from it.
TUI troubleshooting
  • If the arrow keys misbehave and act as cancel, run with BRIDGE_TUI_DIAG=1 to log key events (to a temp file).
  • On Windows, this issue is worked around by using WindowsDriver and disabling VT input mode.

(b) Non-interactive (secret key and flags)​

Pass the key as an argument and it is verified and stored immediately (no TUI).

talkbridge setup blumnb-xxxx-xxxx-xxxx --endpoint https://<bridge-endpoint>

Main flags:

GroupFlags
Basic--key, --endpoint
Webhook sink--webhook-url, --webhook-secret (HMAC signing), --webhook-brand, --webhook-console
Discord sink--discord-token, --guild, --channel, --discord-brand
Slack sink--slack-bot (xoxb), --slack-app (xapp), --slack-channel, --slack-brand
CRM--crm sqlite|mysql|csv, --sqlite-path, --mysql-conn, --csv-path
AI--ai-base, --ai-key, --ai-model, --ai-provider, --ai-api chat|responses

After setup completes, your name, permissions, and consultable channels are printed.

Authentication & endpoint​

  • Every request is authenticated with Authorization: Bearer <secret key>.
  • Keys have scopes: BrandRead / BrandWrite / Admin. Sending and changing settings require BrandWrite or higher.
  • The default bridge endpoint is https://webhook.talkbridge.io; you can change it with setup --endpoint or login.
  • Credentials are stored at ~/.talkbridge/config.json — protected with user-only permissions.
  • The Brand Key you pass to --webhook-brand, --discord-brand, --slack-brand and each command's --channel is shown in the "Integration keys" card in Developer mode of TalkBridge Center. The Agent Key (secret key) and the signature verification key are in the same card.

Verification​

talkbridge whoami

If your name, permissions (scopes), endpoint, and consultable channels are shown, you're ready. → Command reference