Session Replay#

Session Replay reconstructs user DOM/sessions (and Kit-level interactive capture) for debugging and support. It is not control-plane event-log replay and not auth session.*.

Naming split (critical)#

Heavy rrweb streams never enter the control-plane event log — only content-addressed blob refs.

Defaults#

Deep Bindle integration (App Kits)#

Every App Kit receives a default platform annotation session-replay at construction — not only web:

Infra Kits (kv, bucket, queue, topic, secret, data, …) are not entrypoint hosts — no default Session Replay.

Local Yard / hobo dev wraps every HTTP App Kit (api, web, service, ui) so HTML gets a privacy-first bootstrap and /__hobo/replay/* serves ingest/list — no app tracker code required. JSON API Kits still expose the ingest path on the same wrap.

import { bindle, sessionReplay } from "hobo/bindles";

export default bindle("shop", (b) => {
 const api = b.api(() => apiHandler); // API Kit — Session Replay default-on
 const web = b.web(() => storefront); // Web Kit — Session Replay default-on
 const worker = b.service(() => worker); // Service Kit — Session Replay default-on
 const cache = b.kv(); // Infra Kit — no default Session Replay
 // opt out one Kit:
 // const api = b.api(() => apiHandler).with(sessionReplay({ enabled: false }));
 return { api, web, worker, cache };
});

Privacy (client-side before send/persist)#

• Mask password / email / tel inputs
• Mask [data-hobo-mask], .hobo-mask, payment autocomplete fields
• Redact Authorization / Cookie in network capture
• Continuous-identity principalRef only — no free-text PII

CLI / MCP#

hobo replay doctor
hobo replay list
hobo replay get <sessionId>
hobo replay summarize <sessionId>
hobo replay open <sessionId>
hobo replay retention

MCP tool parity via canonical verbs. Player surfaces are read-oriented; mutation stays on CLI under policy/PAM. hobo doctor lists contract boundary ids.

Event family (replay.*)#

Started · ChunkIngested · Ended · ErrorLinked · RetentionApplied · Accessed · Disabled · Metered

Composition#

Performance budget (targets)#

Honest scope#

• Live multi-cloud object storage + Junction federation: ports present; dual fixtures prove the path
• Full OpenReplay Assist / Helm stack: optional, not default
• High-volume product analytics warehouse: residual

Related#

Bindles · App Kits · Trail map · Harness · CLI · Event families · Dual fixtures · Stations