Repository navigation
Status too large for the cloud: clear error, server capabilities, MCP keeps the connection (SDK + MCP 2.13.15) - #78
Merged
Conversation
…CP keeps the connection (SDK + MCP 2.13.15)
Firmware 3.10.4's status could be larger than the cloud channel takes, so a cloud connect failed
with "status: reply too large for the cloud channel". The SDK's error now names the fix
(firmware 3.10.5), and bp.capabilities falls back to the server's capability set and keeps it
rather than reading the status again on every access. The MCP status/connect report the
firmware fields as unknown with a warning instead of failing the connect.
Firmware 3.10.5 sends the short form over the cloud ("short_form": true), without lan_tls: the
MCP status fills firmware.lan_tls from the lan_tls command there (the desktop Pod Settings reads it).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Firmware 3.10.4's
statuscould be larger than the cloud channel takes, so a cloud connect failed withFirmwareError: status: reply too large for the cloud channel (1838 bytes, limit 1791). Firmware fix: embeddedci-com/benchpod-firmware#143 (3.10.5).SDK (embeddedci 2.13.15)
benchpod flash-selfor the web app's firmware update).bp.capabilitiesfalls back to the server'scap.*set when status is too large, and keeps it, instead of re-reading status on every access.MCP (embeddedci-mcp 2.13.15)
connect/statusno longer fail on that pod: the firmware fields are reported as unknown with a warning to update to 3.10.5.short_form: true, nolan_tls),statusfillsfirmware.lan_tlsfrom thelan_tlscommand (the desktop Pod Settings readslan_tls.https_only).Tests
connectover the cloud returns firmware 3.10.5 withlan_tlsfilled.🤖 Generated with Claude Code