Best practices

For teams adopting Runtime

• Connect one workspace per team, not one per person — engineering memory is only useful when it's shared.
• Assign at least one other owner or admin besides yourself, so billing and membership never depend on a single person.
• Use Replay before asking someone to explain a change — it is usually faster than a meeting.

For integrators emitting RCP events

• Always send sessionIdwhen an event belongs to a session — it's the join key Replay depends on.
• Treat emission as fire-and-forget. Never let a failed event send block or slow down the underlying tool.
• Don't assume every event type in the taxonomy has a consumer yet — check Event taxonomy for what is live before building against it.
• Ignore unknown fields and unknown event type values rather than failing — see Versioning.

What not to send

RCP is designed around engineering activity and metadata, not raw source code or secrets. Don't put file contents, credentials or customer data directly into an event payload — reference a path or identifier instead.