Skip to content

The Claude Code pane reads a Board with much finished work again - #11

Merged
marvin-bitterlich merged 1 commit into
mainfrom
pane-rpc-answer
Nov 7, 2026
Merged

marvin-bitterlich merged 1 commit into
mainfrom
pane-rpc-answer

Conversation

@marvin-bitterlich

Copy link
Copy Markdown
Contributor

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.fetch answer. Platform's overview answer is about 4.2 MB. The Board compresses it, so the host's size check on content-length passes, 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 no Exit, and the pane reports that the Board sent no answer.

Overview part Size on Platform Read by the pane or the overview tools
goals.items: every item's record 2.6 MB no
fleet.completed: all finished Fleet work 1.5 MB no
everything else about 45 KB yes

Both parts grow with every finished task, so the pane would stay broken.

How?

work-board.overview now returns only what its readers show: the three goal lists, and Fleet's in-flight items and areas. The schema omits goals.items and the ready Fleet's completed, so the answer stays small however much finished work the board keeps. work-board.goals and work-board.fleetItems still 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

  • The overview gets smaller, and the plugin gets no new query. Only the plugin and the Board's MCP board_overview tool read the overview, and both already removed these parts. A separate glance query would give the overview job a second path.

Callouts

  • An unterminated request still gets an empty 200. The Board's RPC route keeps a request line without a final newline in its ndjson buffer and answers with an empty body. That reader is Effect's RpcServer HTTP protocol, served through @shivaedev/server, so the fix goes to Platform and not to this repository. The plugin always sends the newline.
  • work-board.fleetItems also grows with finished work. The plugin's item tool reads it, and on Platform it is now 1.5 MB. When it passes 4 MiB, that tool reports the new broken-off error.

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.
@marvin-bitterlich
marvin-bitterlich added this pull request to the merge queue Nov 7, 2026
Merged via the queue into main with commit a4a5016 Nov 7, 2026
16 checks passed
@marvin-bitterlich
marvin-bitterlich deleted the pane-rpc-answer branch November 7, 2026 00:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant