Repository navigation
Semantic tool and edit rows can disappear without diagnostics explaining the suppression reason #344
Description
Problem
Saved debug bundles do not expose why semantic tool/edit rows disappear. Several code paths intentionally suppress semantic rows, but render diagnostics only show high-level row state.
Evidence
Bundle:
~/.config/agent-code/debug-bundles/manual/2026-06-22T12-41-25-706-450b5c8a
- Note says edits/tool rows stopped rendering.
- Diagnostics show semantic history turns with text plus
tool_useblocks. - Current semantic turn has only empty
thinking, so emitting no visible current row is expected. - The bundle does not say whether missing tool/edit rows were skipped as committed-owned, collapsed, running, empty, or unparseable.
Known Suppression Paths
- semantic blocks owned by committed tool indices
- collapsed activity rows returning null while running
- empty reasoning blocks
- live edit rows waiting for parseable edit input
- committed rich edit/write/todo surfaces taking ownership
Relevant paths:
src/renderer/src/features/feed/ui/semantic/renderUnits.tssrc/renderer/src/features/feed/ui/semantic/CollapsedActivityRow.tsxsrc/renderer/src/features/feed/ui/semantic/BlockRow.tsxsrc/renderer/src/features/feed/ui/rows/Block.tsx
Expected Diagnostics
For each semantic turn, include raw block count, emitted render units, skipped reason, and whether the React row returned null.
Useful skip reasons:
committed_tool_usecommitted_tool_resultempty_thinkingcollapsed_runningowned_textunparseable_live_edit
Activity
Juliusolsson05 commentedon Jun 22, 2026
Linking this back to #172. This is the diagnostic companion to the new rendering engine work: the single ordered ownership plan should emit explicit owner/suppression decisions for semantic tool/edit rows.
When #172 is implemented, this issue should verify that render diagnostics include candidate owners, selected owner, skipped reasons, and final DOM order for each feed item.
Juliusolsson05 commentedon Jul 7, 2026
Structurally fixed by the ledger rewrite (#442).
Every suppressed candidate now records a typed
RenderReason+ evidence in the ownership decision (src/renderer/src/rendering/model/types.ts), serialized verbatim into feed-debug and debug bundles — so "why did this row disappear" is answerable directly from a bundle. The named skip reasons (committed-tool-use-owned,empty-thinking,collapsed-running,compaction-synthesis,synthetic-user-filtered,sidechain-filtered, …) are the enum. Closing.