Repository navigation
The pane's Areas section shows only busy lanes and waits for a busy Fleet - #9
Merged
Merged
Conversation
…leet Fleet's daemon.fleetItems lists only the areas that work holds, queues or reserves, instead of every repository folder. The Work Board pane shows those areas with held ones first and says when no area is busy. Board waits up to 20 seconds for each Fleet read, and keeps its whole Fleet view within 25 seconds so it answers inside Claude Code's 30-second plugin fetch. A Fleet that does not answer in time is named as such, and the pane calls a Board that the host stopped waiting for busy instead of stopped.
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 beside his Claude sessions to see goals, Fleet work and areas. Two parts of it did not tell the truth.
The Areas section listed about 60 "areas" for Platform. These included
.pnpm-store,.worktrees,.work,.claudeand every package, and almost all were "free". It looked as if every folder was an area, and the few busy lanes were hard to find. The section must show at a glance which lanes are busy and what waits on them.The pane also said that Fleet on port 3457 "didn't answer as expected" while Fleet was healthy and only busy. The Board gave Fleet 5 seconds per read. A busy Fleet often needs more time than that.
How?
Areas. The list came from Fleet. Fleet passed every repository folder that the Board's
areaFoldersfound to its area lanes, so each folder became an idle lane. Nowdaemon.fleetItemslists only the areas that work holds, queues or reserves. The plugin also drops free entries (from an older Fleet), puts held areas first, and says "No area is held or queued." when no lane is busy. TheareaFoldersandrepositoryRootexports on the Board'sboardintegration object had no other user, so this change removes them.Timeouts. I measured against a copy of Platform's Board and Fleet, on other ports and another database. The copy's Fleet had a busy queue and the Board files changed at the same time:
daemon.fleetItemsdaemon.briefProblemsThe Board now waits up to 20 seconds for each Fleet read. The Fleet view makes two reads, and Claude Code waits only 30 seconds for each plugin request. So the two reads share one 25-second budget, and the Board always answers in time. A Fleet that does not answer within that time is reported as "didn't answer within 20 seconds". The old "didn't answer as expected" message now shows only for a bad answer.
On the plugin side, Claude Code stops waiting for a plugin request after 30 seconds. The pane reported that case as "the Work Board isn't running". Now it says that the Board is busy, and the next refresh asks again.
Decisions
git check-ignoreon each Board scan would cost too much.Callouts
src/claude-code.d.tsdocuments no typed timeout error to use instead.