Repository navigation
The Claude Code pane reads a Board with much finished work again - #11
Merged
Merged
Conversation
The Board's overview answer had grown past the 4 MiB Claude Code reads of a plugin's fetch. The host cut the decompressed answer there, the cut dropped the line's end, and the pane's ndjson reader found no Exit, so the pane said the Board sent no answer. The overview now leaves out every item's record and Fleet's completed work, which no overview reader showed. The plugin names an answer that breaks off mid-message instead of reporting no answer.
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.
Why?
Marvin keeps the Work Board pane open beside his Claude sessions. On Platform's Board it showed only "The Work Board sent no answer to work-board.overview.", and Refresh did not help. The Board itself was healthy and answered the same request from
curl.The cause is the size of the answer. Claude Code reads at most 4 MiB of a plugin's
$.http.fetchanswer. Platform's overview answer is about 4.2 MB. The Board compresses it, so the host's size check oncontent-lengthpasses, but the host then stops reading the decompressed body at 4 MiB without an error. The cut removes the end of the only ndjson line, the pane's reader keeps that half line in its buffer and finds noExit, and the pane reports that the Board sent no answer.goals.items: every item's recordfleet.completed: all finished Fleet workBoth parts grow with every finished task, so the pane would stay broken.
How?
work-board.overviewnow returns only what its readers show: the three goal lists, and Fleet's in-flight items and areas. The schema omitsgoals.itemsand the ready Fleet'scompleted, so the answer stays small however much finished work the board keeps.work-board.goalsandwork-board.fleetItemsstill return the full lists for the browser.The plugin now checks that an answer ends with a newline before it decodes it. An answer cut off mid-message reports "The Work Board's answer to … breaks off mid-message after N characters. Claude Code reads at most 4 MiB of an answer." and no longer reports that the Board sent no answer.
The Board's socket story kit now reads each plugin answer as the host does, up to 4 MiB. The new stories drive the shipped plugin client against a real Board: one has nine finished tasks with long notes, the other has goals larger than the limit. Without this change, the first story fails with the exact message from the pane.
Decisions
board_overviewtool read the overview, and both already removed these parts. A separate glance query would give the overview job a second path.Callouts
RpcServerHTTP protocol, served through@shivaedev/server, so the fix goes to Platform and not to this repository. The plugin always sends the newline.work-board.fleetItemsalso grows with finished work. The plugin'sitemtool reads it, and on Platform it is now 1.5 MB. When it passes 4 MiB, that tool reports the new broken-off error.