ClipBridge Frequently Asked Questions

ClipBridge is a desktop-first clipboard bridge that lets trusted devices share clipboard content securely across macOS, Windows, and Linux. Once devices are paired into a mesh, ClipBridge keeps clipboard history, delivers new items in near real time, and provides controls to pause or revoke sharing at any moment.

ClipBridge is designed for individuals and teams that move sensitive information between workstations and need strong trust controls, auditability, and predictable delivery paths (LAN, relay, or direct sockets). It supports solo users with multiple devices just as effectively as larger groups.

1. Install and sign in to the ClipBridge desktop app on the device you want to add, using the same account as your trusted devices.
2. From the post-login pairing prompt, display the temporary verification phrase for that device.
3. On another trusted device signed in to the same account, open the pairing modal, review the spoken phrase, and approve the request.
4. Once both sides confirm, our system issues a mesh token and device token so the new device can join and stay trusted.

Decline the request immediately. The session will be invalidated and you can start a new one. Always confirm the exact phrase aloud to prevent unauthorized pairing.

ClipBridge handles plain text, files, and structured payloads. Large files flow through the reservation workflow, allowing recipients to request fulfillment once the publisher confirms the upload.

Yes. Use the Clipboard Bridge toggle in the desktop app to disable the bridge for a specific device. Disabled devices stop publishing and consuming clipboard items until re-enabled.

By default, ClipBridge keeps the ten most recent clipboard items per mesh so teammates can re-copy content quickly. Mesh owners may clear history by revoking or rotating devices.

Clipboard contents are encrypted end-to-end using mesh-scoped end-to-end keys. Our system queues and routes encrypted blobs, but it never decrypts payloads. Device and mesh tokens rotate regularly to limit token reuse.

Immediately revoke the device from the Overview dashboard. This clears its clipboard queues, disconnects active sessions, and prevents further access. Pair a replacement device once you are confident the environment is secure.

ClipBridge only stores encrypted payloads and limited metadata (timestamps, source device, delivery status). You control what enters the clipboard and can pause sharing or disable notifications when working with especially sensitive data.

The transport layer selects the best path on demand-LAN QUIC, direct peer sockets, or encrypted relay queues-based on device availability and configured policies. Transfers retry automatically and chunk large payloads for resilience.

Presence indicators reflect heartbeat updates received from each device. Green means the device is active, yellow means the heartbeat is stale, and gray indicates the device is offline or recently revoked.

ClipBridge maintains desktop builds for macOS, Windows, and Linux. Ensure you install the latest version from the Releases page. Some OS-specific features (e.g., menu bar integrations) may vary by platform.

Yes. Each desktop can enable or disable clipboard notifications individually. The app throttles alerts when it detects you have just consumed the same clipboard item to reduce noise.

Submit issues in the project repository or contact the team atclipbridge@bytelogic.me. Include logs or reproduction steps whenever possible to speed up triage.