fix(sdk): playground auto-refresh after an agent commit (regression from the migration) - #5805
Conversation
…mit shape. The stream projector that turns a successful commit_revision tool output into the data-committed-revision part gated on the legacy 'count' field; the migrated handler answers {status: committed, ...} with no count, so the projector silently dropped the part, commits stored fine, and the playground never switched to the new version (live incident, session b024a6b0). The gate now accepts either shape. The suite stayed green through the regression because every fixture pinned the legacy shape; a test now pins the live handler shape. Live-verified: the round trip streams the part with correct ids and the playground signal fires.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
dosubot
Bot
added
size:S
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Railway Preview Environment
Updated at 2026-08-07T16:39:35.373Z |
1 participant
Context
Mahmoud's live QA found that after an agent commits a config change and the user approves it, the playground no longer switches to the new version automatically. The commit stores correctly; only the refresh signal is missing.
Changes
The SDK's stream adapter projects a successful commit_revision tool output into the data-committed-revision stream part the playground listens for. Its gate required the legacy output's count field. The migrated handler-mode commit answers {"status": "committed", ...} with no count, so the projector silently returned nothing. The gate now accepts either shape, with a comment recording the incident.
Before: no data-committed-revision part in the stream (verified in the reported session: zero occurrences across 108 events).
After: the part streams with correct variantId, revisionId, and version (live-verified with the gate's commit round trip; token match; version bump observed).
Tests