Repository navigation
feat(task-list): number tasks 1-N in UI for voice targeting - #679
Merged
Merged
Conversation
Adds visible numeric prefix to each task row in the dashboard task list. Matches the 1-based taskIndex param the toggle_tasks tool accepts, so when the user says "expand task 3" they can see exactly which task that is. Numbers are display-order based (newest first, filtered same as renderTasks) — the same sequence the toggle_tasks handler uses. Per Chi 2026-05-14 01:26 PT: numbering makes per-task expand targets unambiguous. Does NOT include the exclusivity change from PR #678 (closed unmerged) — expand:N stays additive.
1 of 2 tasks
sonichi
added a commit
that referenced
this pull request
May 14, 2026
…-block (#680) #679 shipped numbering but it was too muted to notice visually (#6b7a90 / 14px / normal weight against the dark bg). Chi reported the span EXISTS in DOM via DevTools but doesn't see it in UI. Tweaks: #9aa8c0 (lighter slate) / 15px / 600 weight / display inline-block. Same min-width treatment, still left-aligned in the flex row.
1 of 2 tasks
sonichi
added a commit
that referenced
this pull request
May 14, 2026
…681) Earlier attempts (PR #679 numbering, #680 visibility bump) shipped a separate <span class="task-num"> as a flex item. DevTools confirmed: all 30 .task-num elements had zero width despite min-width:28px, flex-shrink:0, and content "1.". Parent was correctly flex. The flex layout was collapsing the span — likely interaction between .task-text's flex:1 (flex-basis:0) and min-content sizing on the ancestor. Adding !important wider styles didn't help — Chi reported no yellow box appeared. Sidestep entirely: prepend the index INTO .task-text's displayText. Same visual effect (`1. [Voice] ...`), one less layout puzzle. CSS rule for .task-num and the standalone span both removed.
liususan091219
pushed a commit
to liususan091219/sutando-fork
that referenced
this pull request
May 28, 2026
) Adds visible numeric prefix to each task row in the dashboard task list. Matches the 1-based taskIndex param the toggle_tasks tool accepts, so when the user says "expand task 3" they can see exactly which task that is. Numbers are display-order based (newest first, filtered same as renderTasks) — the same sequence the toggle_tasks handler uses. Per Chi 2026-05-14 01:26 PT: numbering makes per-task expand targets unambiguous. Does NOT include the exclusivity change from PR sonichi#678 (closed unmerged) — expand:N stays additive.
liususan091219
pushed a commit
to liususan091219/sutando-fork
that referenced
this pull request
May 28, 2026
…-block (sonichi#680) sonichi#679 shipped numbering but it was too muted to notice visually (#6b7a90 / 14px / normal weight against the dark bg). Chi reported the span EXISTS in DOM via DevTools but doesn't see it in UI. Tweaks: #9aa8c0 (lighter slate) / 15px / 600 weight / display inline-block. Same min-width treatment, still left-aligned in the flex row.
liususan091219
pushed a commit
to liususan091219/sutando-fork
that referenced
this pull request
May 28, 2026
…onichi#681) Earlier attempts (PR sonichi#679 numbering, sonichi#680 visibility bump) shipped a separate <span class="task-num"> as a flex item. DevTools confirmed: all 30 .task-num elements had zero width despite min-width:28px, flex-shrink:0, and content "1.". Parent was correctly flex. The flex layout was collapsing the span — likely interaction between .task-text's flex:1 (flex-basis:0) and min-content sizing on the ancestor. Adding !important wider styles didn't help — Chi reported no yellow box appeared. Sidestep entirely: prepend the index INTO .task-text's displayText. Same visual effect (`1. [Voice] ...`), one less layout puzzle. CSS rule for .task-num and the standalone span both removed.
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.
Summary
Adds visible
1./2./3.prefix to each row in the dashboard task list. Matches the 1-basedtaskIndexparamtoggle_tasksaccepts (from #674) so "expand task 3" is unambiguous to both Chi and the model.Why
Chi 2026-05-14 01:26 PT: per-task expand was hard to test because "the first task" was ambiguous from the user's POV. Numbering makes the target visible.
What this is NOT
resultyet)Test plan
1. [Voice] ...,2. [Discord] ...rows🤖 Generated with Claude Code