# Pair debugging

> Share your live capture with up to 10 teammates in a read-only window, end-to-end encrypted through Subcloak's relay, with redacted bodies by default.

Source: https://docs.subcloak.com/cloak-proxy/team/pair-debugging/

Added in Cloak Proxy 0.7.0.

{/* L9 draft. Sources: PLAN 7.10, 7.14 (pair policy), 8.4 (pair caps), 10 (Pair viewer); T13. Re-check labels against L8. */}

Pair debugging shows your live capture to teammates anywhere, as it happens, in a read-only window in their Cloak Proxy. It works like [live sharing](https://docs.subcloak.com/cloak-proxy/sessions/live-sharing/), but across the internet and only for members of your team. The traffic is end-to-end encrypted: Subcloak's relay passes it on without being able to read it.

## Start a session

{/* PLAN 7.10 */}

1. Click **Pair…** in the toolbar, or choose **Pair…** from the **Team** menu.

2. Choose up to 10 teammates.

3. Choose what to share: a query (your current filter by default) and the body options. Bodies are redacted by default. If the team's policy forces **Hide all body values**, it's on and can't be turned off.

4. Start.

Your teammates get a notification and an Activity entry: "Priya invited you to follow their capture." A teammate who isn't online when you start sees the invitation when they're next online, while the session lasts. **Join** opens a read-only window, titled, for example, "Following Priya's capture (read-only)", with the traffic table and inspector; they see new flows within a couple of seconds. Once the session ends, the invitation disappears. {/* v1.5.9-mac (b), server item 114 */}

If the host removes someone, the session restarts with a new key for everyone else, and their windows keep following.

## What viewers can and can't do

{/* T13 (v1): viewers → host only bye and ping; frames signed by sender */}

- Viewers can read what you share and **Leave**. They can't change anything on your Mac: the only messages a viewer's Mac can send you are "leaving" and a keep-alive, and yours ignores everything else.
- Only the teammates you invited can connect, and only their Macs can decrypt the session.
- Every message is signed by the Mac that sent it, and checked against the team's member list, so neither the relay nor a viewer can pass off something as coming from you. {/* T13 v1, T20 item 8 */}
- Either side can stop. A session ends after 8 hours at most.

## Limits and policy

{/* PLAN 8.4, 7.14 */}

| Limit (per team) | Value |
|---|---|
| Viewers per session | 10 |
| Session length | 8 hours |
| Relay time | 20 hours a month for each seat |

The policy **Pair debugging** can block it for the whole team; then Subcloak's relay refuses new sessions.

## What Subcloak sees

{/* PLAN 1.1; T13 */}

The relay sees which team members are connected, how much data passes and when. It never sees the traffic.

## Related

  - [Live sharing](https://docs.subcloak.com/cloak-proxy/sessions/live-sharing/): Share with someone on the same network, with nothing uploaded.
  - [Policies](https://docs.subcloak.com/cloak-proxy/team/policies/): Turn pairing off, or force Hide all body values.
  - [Security model](https://docs.subcloak.com/cloak-proxy/team/security-model/): How the pair channel is encrypted.