Repository navigation
The Session header's child seats never render, so the subagent catalog is unreachable #803
Description
What happens
The subagent catalog never appears in the Session header. ui-subagent registers its count dropdown on conversation.session.header.actions, but that seat is never rendered, so a user who starts a subagent sees no entry point and no way to open the child conversation from the header.
Why
core/src/client/index.js claims the whole Session header as a single slot:
shadow('conversation.session.header', { priority: -10, inject: face }, HeaderPill)The native ConversationSessionHeader is the only component that renders the child seats of that slot — conversation.session.header.lineage, .actions, .utilities, .corner. HeaderPill renders one div and never calls renderSlot, so all four child seats stop being drawn. The same origin appears in sidebar.workspaces (priority -10), which hides sidebar.workspaces.directoryFlow, .session.menu.item, .session.row.action, sidebar.session.row.leading and .session.row.hover.
What I expect
FlyBot's pill should be appended to the native header instead of replacing it, so the seats the shell declares keep rendering. With the pill moved to conversation.session.header.utilities (a list seat) the native header returns, SubagentCatalogAction mounts, and the header shows the subagent count again.
Scope
Right side only, in this issue: conversation.session.header. The left sidebar has the same root cause but TeamSidebar is FlyBot's main surface, so it needs its own design and is not part of this change.
Evidence
- React fiber: the
conversation.session.headeroutlet subtree ended atHeaderPill → div.bt-head;ConversationSessionHeaderwas absent. - Among 33 rendered slot outlets,
.lineage,.actions,.utilitiesand.cornerwere none of them. - DOM:
<header>carried onlyconversation.header.leadingandconversation.session.header; native crumbs count was 0. - After moving the pill to
.utilities: all six header seats render,SubagentCatalogActionis mounted, and the header shows3 个子智能体whose dropdown lists all three child sessions with mode, token total and duration.
Activity
Birfy commentedon Oct 23, 2026
Triage:
bug | area:ui,agent-ready. Repro and root cause are already in the body; what was missing was the acceptance, so here it is.Verified on
mainfd205c40:core/src/client/index.js:881is a flatshadow('conversation.session.header', { priority: -10, inject: face }, HeaderPill), while additive seats elsewhere in the same file useid:/order:(:864-865sidebar.footer.action), which is the pattern the fix should follow. The same flat shadow exists at:861forsidebar.workspaces; that one stays out, as the body says.Expected behaviour, in checkable terms:
ConversationSessionHeaderwith its declared seats (…header.lineage,.actions,.utilities,.corner) present in the tree; the FlyBot pill is one child of.utilities, not a replacement of the slot.TeamSidebar,sidebar.workspacesand the left sidebar are untouched in this PR.Evidence the PR must attach, since a visual claim is not a test here: the same two artefacts the issue already used — the rendered DOM for the header (seat list) and, for a Session with children, the catalog opening — captured before and after on the same build.
Kill conditions (each must turn a check red): keep the interrupting
shadowat priority -10 → seats still missing; mount the pill in both places → the single-pill check fails; filter the catalog so it shows for childless Sessions → the "no children, no entry" check fails; change:861as well → out of scope.Keep the header's Session effects off the pill's seat (ThinkFlowLab#803)
fix(client): keep the Session header's seats and the pill's page effe…
Birfy commentedon Oct 23, 2026
Landed in the fork as
6f9b60c7(#28, squash). Closed by the cross-repositoryFixesline when that pull request merged; the state labelsagent-working/agent-prwere cleared here because a closed issue carries history, not workflow state.Give each Session page effect its own dependencies (ThinkFlowLab#803)