Merge Dev - streaming rate-limit, lineage cost reporting, v0.3.39#162
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
CLI: streaming rate-limit, lineage cost reporting, v0.3.39
Relay broadcast batching (per-session Realtime rate cap)
The
weco start clauderelay now coalesces transcript broadcasts and rate-limits them so a single streaming session can never exceed a fixed messages/sec ceiling on Supabase Realtime — independent of how fast the SDK emits.transcript_batchevent (array of lines) — coalesced, never dropped. Sparse output still sends immediately (no added latency); throttling only kicks in under load.1000 / WECO_RELAY_FLUSH_MSmsgs/sec per session (default 100ms → ≤10/s), env-tunable.transcript_chunk.transcript_batchbefore this CLI ships (the dashboard handler is backward-compatible — handles both oldtranscriptand newtranscript_batch). Ship dashboard first, then this.Lineage-wide cost reporting
Run cost now reflects the entire lineage (parent + derived runs), not just the single run —
check_run_costqueries the new/billing/run/{id}/lineage-costendpoint (a superset of the per-run cost).Version
Bump to 0.3.39.