All pages
Docs · Background features
VibeHub sync
Availability: macOS.
The VibeHub integration (Settings → VibeHub) mirrors your TRMNLY activity to a vibehub.co account, so agent conversations and terminal command history are searchable alongside your other sessions. Everything is opt-in and off by default.
Setup
- Open Settings → VibeHub and flip the master Enable toggle.
- Paste your VibeHub API token (
vbh_…). It's stored in the macOS Keychain, never on disk in plaintext. - Optionally change the API URL — self-hosted and staging deployments work; the field falls back to the public host if the URL doesn't parse.
The pane shows live status: last sync time, the most recent error, and how many agent sessions have been mirrored.
What gets synced
Two capture surfaces, each with its own toggle (both default on once the master switch is enabled):
- Agent conversations. Each in-app agent session becomes a VibeHub session. New messages are appended in batches after a turn settles — streaming turns keep pushing the flush out, so partial responses are never uploaded. Sync is idempotent: re-syncs after a crash resume the same remote session instead of duplicating it. If a local transcript diverges (fork, edited turn, compaction), a fresh remote session is started rather than corrupting the old record.
- Terminal command history. Each finished command becomes one message — the command text, working directory, exit code, and duration — in a per-tab VibeHub session. Scrollback is never uploaded; only the command record.
Limits and privacy
- Long tool results are truncated per message — VibeHub is a conversation record, not an artifact store.
- Uploads are batched and paced to respect VibeHub's write rate cap.
- Values stored in the Keys vault are scrubbed from content before upload, along with everything else the secrets scrubber catches — a credential that leaked into a transcript doesn't also leak into VibeHub.
- Turning the integration off stops capture immediately; nothing runs in the background while it's disabled.
Troubleshooting
- "No VibeHub API token" — add one in Settings → VibeHub; the token must be present in the Keychain for any call to run.
- HTTP errors in the status row — the pane surfaces the API's own response text; transient 429/5xx responses are retried with backoff automatically.
- Deleting the token and disabling the integration leaves your local sessions untouched — sync is one-way, TRMNLY → VibeHub.