curious how CRDB handles the write amplification on high-frequency streaming sessions every SSE chunk going to the DB or are you batching at the session boundary?
On write amplification — we persist at the message level, not per SSE chunk. The sandbox's workspace filesystem (claude code's native jsonl files) is the source of truth for resume, and the DB is for queryability, tracing, etc - so fire and forget works fine here.