{"version":"2.1.304","anchor":"request-replay-capture-and-bridge-owner-check-changes","canonical_anchor":"request-replay-capture-and-bridge-owner-check-changes","heading":"Changes to request-replay capture and remote connection ownership checks","tier":"internal","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/request-replay-capture-and-bridge-owner-check-changes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Changes to request-replay capture and remote connection ownership checks\n\nRequest-replay capture now fingerprints requests differently, and a new check links a host-supplied login token to a server-side identity\n\n**What**\n\nTwo changes to how Claude Code handles requests internally:\n\n- Request-replay capture, which records the shape of requests into the session transcript (the saved record of a conversation), now fingerprints that shape with a SHA-256 hash computed as the data streams in. The fingerprint is taken from the cleaned-up request settings.\n\n- A new ownership check on the bridge connection matches a login token supplied by the host program to an identity on the server side, and records when it does so.\n\n**Why**\n\nBoth changes are internal bookkeeping, and nothing here points to a visible difference for people using Claude Code.\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}