28 KiB
spec, created, status
| spec | created | status |
|---|---|---|
| docs/specs/ui/requirements/agent-todo-list-panel.md | 2026-08-03 | draft |
Implementation Plan: Agent Todo List Panel
Overview
Add one new per-user boolean setting (showTodoListPanel) through the full
existing settings round trip (backend SQLite-backed model → DTO → service →
frontend SSR/WS mapping → Settings UI), then register a new reusable Dockview
panel (todos) that renders the agent's live todo checklist, gated at
runtime by that setting through a small conditional-sync hook modeled on the
existing PR Details pattern. Order: backend settings plumbing and frontend
settings plumbing first (independent of the panel and easiest to verify in
isolation), then the panel registration + rendering, then the visibility-sync
hook that wires the setting to the panel, then E2E coverage of the full flow.
Iteration 2: "Only pin when todo list is not empty" sub-option
Iteration 1 (Tasks 01-05) is shipped. Iteration 2 adds a second boolean
setting (showTodoListPanelOnlyWhenNotEmpty / wire
show_todo_list_panel_only_when_not_empty) that gates the automatic pin on
the active session having todo entries, plus an explicit copy pass on the
main toggle ("automatically pins ... can always be added manually"). The
sub-option is hidden (inhibited, not disabled) while the master preference is
off, and its value is preserved independently so it reappears in its saved
state. Order: backend field first, then frontend settings plumbing + UI,
then the conditional-pin sync behavior, then E2E. Spec amendment:
docs/specs/ui/requirements/agent-todo-list-panel.md (What / Data model / API surface /
Scenarios / Out of scope).
Backend
Settings model, DTO, service, store
Iteration 2 additions
apps/backend/internal/user/models/models.go: addShowTodoListPanelOnlyWhenNotEmpty bool \json:"show_todo_list_panel_only_when_not_empty"`besideShowTodoListPanel`.apps/backend/internal/user/dto/dto.go: add the field toUserSettingsDTO(bool,json:"show_todo_list_panel_only_when_not_empty"), toUpdateUserSettingsRequest(*bool,omitempty), and to the DTO-from- settings constructor besideShowTodoListPanel(~line 245).apps/backend/internal/user/service/service.go: add the field to the update-request struct (besideShowTodoListPanel, ~line 60), theif req.ShowTodoListPanelOnlyWhenNotEmpty != nil { settings.ShowTodoListPanelOnlyWhenNotEmpty = *req.ShowTodoListPanelOnlyWhenNotEmpty }merge-patch block inapplyTaskActionPreferences(after theShowTodoListPanelblock, ~line 370), and the response map entry beside"show_todo_list_panel"(~line 781).apps/backend/internal/user/controller/controller.go: pass the new*boolthrough the DTO→service conversion besideShowTodoListPanel(~line 69).apps/backend/internal/user/store/sqlite.go: add the field to the JSON column read map (beside"show_todo_list_panel", ~line 542), the fresh-user defaults (false, ~line 667), the partial-update payload struct (*bool, ~line 730), and the apply-if-present block (~line 809).apps/backend/internal/backendapp/boot_state_routes.go: add"showTodoListPanelOnlyWhenNotEmpty": settings.ShowTodoListPanelOnlyWhenNotEmptyto the boot payload besideshowTodoListPanel(~line 467).apps/backend/internal/user/store/sqlite_test.go: extend the existingTestScanUserSettingsTodoListPanelDefault/TestTodoListPanelSettingRoundTripThroughMarshalAndScancases (or add sibling cases) for the new field.apps/backend/internal/user/service/service_test.go: addTestApplyBasicSettingsTodoListPanelOnlyWhenNotEmptymirroringTestApplyBasicSettingsTodoListPanel(omission preserves, explicit value replaces, explicit false disables).
Frontend (Iteration 2)
Settings state and persistence plumbing
apps/web/lib/state/slices/settings/types.ts: addshowTodoListPanelOnlyWhenNotEmpty: booleantoUserSettingsStatebesideshowTodoListPanel(~line 230).apps/web/lib/ssr/user-settings.ts: add the default (false) tocreateDefaultUserSettings()(~line 50) and the mapping lineshowTodoListPanelOnlyWhenNotEmpty: s.show_todo_list_panel_only_when_not_empty ?? current.showTodoListPanelOnlyWhenNotEmptyinbuildBehaviorFields(~line 262). The WS handler (apps/web/lib/ws/handlers/users.ts) reusesmapUserSettingsData, so no handler edit is needed beyond the mapping.apps/web/lib/types/http-user-settings.ts: addshow_todo_list_panel_only_when_not_empty?: booleanto bothUserSettingsandUserSettingsUpdatePayloadbesideshow_todo_list_panel(~lines 70, 131).apps/web/e2e/helpers/api-client.ts: addshow_todo_list_panel_only_when_not_empty?: booleanto thegetUserSettingsresponse type (~line 918).
Settings UI
apps/web/components/settings/todo-list-panel-settings.tsx: convert the component from one boolean draft to a{ show, onlyWhenNotEmpty }draft pair:- The main toggle keeps its current
Label(accessible name "Show agent todo list panel", unchanged so existing E2E locators still match) andSwitch(id="show-todo-list-panel"). - The description paragraph under the main toggle switches to the new
explicit copy (key
settings:pinTheAgentsLiveTodoChecklistAs, updated value: "Automatically pin the agent's live todo checklist as a Todos tab in the right panel. Even when this is off, you can always add the Todos tab manually." — note: no em dash; the same key also feeds the section description ingeneral-settings.tsx, which is fine). - New sub-option row rendered only when
draft.showis true:LabelhtmlFor="todo-list-panel-only-when-not-empty"witht("settings:onlyPinWhenTodoListIsNotEmpty")("Only pin when todo list is not empty") +Switch. Hidden (unmounted) when the main toggle is off — inhibited, not disabled — so its draft value is preserved in the save payload. useSettingsSaveContributorrevision becomesJSON.stringify(draft); save sendsupdateUserSettings({ show_todo_list_panel: d.show, show_todo_list_panel_only_when_not_empty: d.onlyWhenNotEmpty })and updates both fields in the store;discardrestores both.
- The main toggle keeps its current
- i18n: update
pinTheAgentsLiveTodoChecklistAsand addonlyPinWhenTodoListIsNotEmptyinapps/web/src/locales/en/settings.json(beside the todo panel keys, ~line 476); regenerate pseudo (pnpm run i18n:pseudo); mirror both intopt-ptandzh-cn.
Conditional-pin sync
apps/web/components/task/dockview-todo-panel-sync.ts:resolveConditionalTodoPanelActiongains two params —onlyPinWhenNotEmpty: booleanandtodoListNotEmpty: boolean— and returns"none"(instead of"add") whenonlyPinWhenNotEmpty && !todoListNotEmpty, after the existing restoring/maximized guards and only when the panel is absent (the sub-option never removes an existing panel; removal stays gated solely onshowTodoListPanel).syncConditionalTodoPaneloptions gain the two params and pass them through to the decision function.useSyncTodoPanelsubscribes to the active session's todo state:state.sessionTodos.bySessionId[sessionId](live) andstate.messages.bySession[sessionId](persisted history, fetched by the always-mounted chat panel) viabuildTodoItems; computestodoListNotEmpty = (live.length ?? 0) > 0 || buildTodoItems(messages).length > 0, readslive.userSettings.showTodoListPanelOnlyWhenNotEmpty, passes both intosyncConditionalTodoPanel, and addstodoListNotEmpty+onlyPinWhenNotEmptyto the effect dependency array so the panel appears as soon as todo entries arrive.
Tests (Iteration 2)
- What: merge-patch persists and returns
show_todo_list_panel_only_when_not_emptyindependently ofshow_todo_list_panel(omission preserves, explicit replaces, explicit false disables). File:apps/backend/internal/user/service/service_test.go. How: table-driven tests mirroringTestApplyBasicSettingsTodoListPanel. - What: SQLite store round-trips the new field for a fresh user and after
a partial update. File:
apps/backend/internal/user/store/sqlite_test.go. How: extend the existing todo-panel scan/round-trip tests with the new field. - What: SSR mapping default and snake_case→camelCase mapping for the new
field. File:
apps/web/lib/ssr/user-settings.test.ts. How: extend the existing "defaults to hidden and preserves an explicit true" case (or add a sibling) forshowTodoListPanelOnlyWhenNotEmpty. - What: WS settings-sync partial update merges the new field. File:
apps/web/lib/ws/handlers/users.test.ts. How: add the field to an existinguser.settings.updatedpartial-payload case. - What:
TodoListPanelSettingsshows the sub-option only when the main toggle is on, preserves its state across main-toggle off/on, and saves both fields. File:apps/web/components/settings/todo-list-panel-settings.test.tsx. How: extend the existing component test: assert the sub-option switch is absent with main off; toggle main on → sub-option appears; toggle sub-option on; toggle main off → sub-option hidden; main on again → sub-option still checked; save →updateUserSettingscalled with both snake_case fields. - What:
resolveConditionalTodoPanelActionreturns"none"foronlyPinWhenNotEmpty && !todoListNotEmpty(absent panel),"add"when the list is non-empty, and never"remove"from the sub-option;syncConditionalTodoPanelpasses the params through. File:apps/web/components/task/dockview-todo-panel-sync.test.ts. How: extend the existingit.eachtable with the new param combinations and add asyncConditionalTodoPanelcase proving noaddPanelcall when the list is empty and the sub-option is on.
E2E Tests (Iteration 2)
-
Scenario: GIVEN the preference is off, WHEN the settings page opens, THEN no "Only pin when todo list is not empty" switch is rendered; toggling the main preference on reveals it, toggling off hides it again while a previously saved
truevalue survives a page reload. File:apps/web/e2e/tests/settings/todo-list-panel.spec.ts. What to verify: switch presence/absence viagetByRole("switch", { name: "Only pin when todo list is not empty" }), and the persisted value viaapiClient.getUserSettings(). -
Scenario: GIVEN main on + sub-option on, WHEN a task with no todo entries opens, THEN no Todos tab is auto-pinned; WHEN a task whose session already persisted todo entries opens, THEN the Todos tab is auto-pinned. File: same spec file. What to verify: reuse
createTaskWithSession(no todos) andcreateTaskWithTodos(persistede2e:planentries), asserttodosTabWrappercount 0 vs visible, viareadTodosLayoutpolling. -
apps/backend/internal/user/models/models.go: addShowTodoListPanel bool \json:"show_todo_list_panel"`to theUserSettingsstruct besideShowTranscriptAutoScrollControl`. -
apps/backend/internal/user/dto/dto.go: addShowTodoListPanel bool \json:"show_todo_list_panel"`to the response DTO, andShowTodoListPanel *bool `json:"show_todo_list_panel,omitempty"`to the update-request DTO, mirroring the existingShowTranscriptAutoScrollControl` fields. -
apps/backend/internal/user/service/service.go: add the field to the update-request struct, theif req.ShowTodoListPanel != nil { settings.ShowTodoListPanel = *req.ShowTodoListPanel }merge-patch block, and the response map entry ("show_todo_list_panel": settings.ShowTodoListPanel), mirroring the threeShowTranscriptAutoScrollControlcall sites (~lines 52-56, 286-292, 689-693). -
apps/backend/internal/user/store/sqlite.go: add the field to the JSON column read map (~461-465), the fresh-user defaults (~582-586,false), the partial-update payload struct (~630-634), and the apply-if-present block (~692-696), mirroringShowTranscriptAutoScrollControl. -
apps/backend/internal/backendapp/boot_state_routes.go: addshowTodoListPanelto the boot/hydration payload besideshowTranscriptAutoScrollControl/showAnchoredPromptBar(~459-463).
Frontend (Iteration 1)
Settings state and persistence plumbing
apps/web/lib/state/slices/settings/types.ts: addshowTodoListPanel: booleantoUserSettingsStatebesideshowTranscriptAutoScrollControl(~line 191).apps/web/lib/ssr/user-settings.ts: add the default (false) tocreateDefaultUserSettings()(~line 45) and the snake_case↔camelCase mapping lineshowTodoListPanel: s.show_todo_list_panel ?? current.showTodoListPanelin the same mapping block asshowTranscriptAutoScrollControl(~243-244).apps/web/lib/ws/handlers/users.ts: add the same field to the incoming user-settings WS-sync mapping, beside the existing boolean display-preference fields.apps/web/lib/api/domains/settings-api.ts: no new function —updateUserSettingsalready forwards an arbitrary snake_case payload object; the new settings component passes{ show_todo_list_panel: value }through the existing call.
Settings UI
- New file
apps/web/components/settings/todo-list-panel-settings.tsx:TodoListPanelSettingscomponent, copied from the single-toggleUnreadDividerSettingstemplate (apps/web/components/settings/unread-divider-settings.tsx): readsuseAppStore((s) => s.userSettings.showTodoListPanel), keeps a local draft/saved boolean, registers withuseSettingsSaveContributor(idgeneral-todo-list-panel), renders aSettingsCardwith aLabel+Switch(@kandev/ui/switch), and on save callsupdateUserSettings({ show_todo_list_panel: submitted })thensetUserSettings({ ...state, showTodoListPanel: submitted }). apps/web/components/settings/general-settings.tsx: importTodoListPanelSettingsand render it inside the existingTaskActionsSettingssection's toggle list, besideUnreadDividerSettings(~line 255), since it is the same class of single-boolean display preference.- i18n: add
todoListPanel(label, e.g. "Show agent todo list panel") and a description key (e.g.showAPersistentTodosTabInThe) toapps/web/src/locales/en/settings.jsonbeside the existingshowTranscriptAutoScrollControlentries, and mirror both keys intoapps/web/src/locales/pseudo/settings.jsonper the repo's pseudo-localization convention.
Reusable Todos panel registration
apps/web/lib/state/layout-manager/constants.ts: add"todos"toREUSABLE_PANEL_IDSandKNOWN_PANEL_IDS, and add aPANEL_REGISTRYentrytodos: { component: "todos", title: "Todos" }(default tab component —DockviewDefaultTabvia no explicittabComponent, giving it a normal close control like Files/Changes).apps/web/components/task/dockview-shared.tsx:- Add
todos: PortalSlottodockviewComponents. - Add a new
TodosContent()portal-content component (reads the active session's todo items and renders them) placed besidePlanContent()(~line 358), and acase "todos": return <TodosContent panelId={panelId} />;branch inrenderPanelbeside the"plan"case (~line 402-403). TodosContentresolves the owning session id the same wayPlanContent/ChangesContentresolve their task/session context (viauseEnvironmentSessionId/store lookup used elsewhere in this file), then calls the shared checklist renderer described below.
- Add
- Extract the checklist body currently inlined in
apps/web/components/task/chat/todo-indicator.tsx'sTodoListcomponent (and itsresolveStatus/StatusIconhelpers, already separately exported) into a shared, presentation-only component — e.g. rename/moveTodoListto export it directly, or add a thin wrapper — so bothTodoIndicator's popover and the newTodosContentpanel render identical rows without duplicating the status-icon/progress logic.TodosContentsources itsTodoDisplayItem[]from the same hookTodoIndicator's caller already uses (useSessionTodoItemsinapps/web/components/task/chat/use-chat-panel-state.ts:469-486), called with the panel's owning session id instead of the chat panel's resolved session id, and an emptymessageTodosfallback array when the panel has no local access to the chat's persisted-message data (matching the Files/Changes/Plan "show an empty state when there's no applicable content" convention fromdocs/specs/ui/requirements/task-layout-profiles.md).
Visibility-sync hook
- New file
apps/web/components/task/dockview-todo-panel-sync.ts, modeled directly onapps/web/components/task/dockview-review-panel-sync.ts, but substantially simpler: no review identity, noreviewsLoadedgating, nowasOffered/session-storage suppression.resolveConditionalTodoPanelAction({ showTodoListPanel, hasPanel }): "add" | "remove" | "none"— pure decision function:"add"when the setting is on and the live layout lackstodos;"remove"when the setting is off and the live layout has it;"none"otherwise.resolveConfiguredTodoPanelPlacement(layout: LayoutState | null): { groupId: string; tabIndex: number } | null— mirrorsresolveConfiguredReviewPanelPlacement, scanning the custom Default layout for an existingtodosentry's group/index.syncConditionalTodoPanel(api, options): void— adds an inactivetodospanel at the configured or Files/Changes-fallback group when action is"add"; removes the existingtodospanel when action is"remove".useSyncTodoPanel()— readsshowTodoListPanelfromuseAppStore, the activetaskId/sessionId/workspaceId, and the samehasApi/isRestoringLayout/centerGroupId/userDefaultLayoutDockview store fieldsuseSyncReviewPanelalready reads, then callssyncConditionalTodoPanelinside the same double-requestAnimationFramedeferred-effect patternuseSyncReviewPaneluses, withshowTodoListPaneladded to the effect's dependency array in place of reviewidentity.
apps/web/components/task/dockview-desktop-layout.tsx: import and calluseSyncTodoPanel()beside the existinguseSyncReviewPanel()call (~line 411).
Tests (Iteration 1)
- What: merge-patch persists and returns
show_todo_list_panel. File:apps/backend/internal/user/service/service_test.go. How: table-driven case alongside the existingShowTranscriptAutoScrollControlcase, asserting aPATCH-equivalent service call withShowTodoListPanel: ptr(true)updates and is reflected in the returned settings. - What: SQLite store round-trips the new field for a fresh user and after
a partial update. File:
apps/backend/internal/user/store/sqlite_test.go. How: extend the existing default-settings assertion and the existing partial-update JSON-payload test (the one already coveringshow_transcript_auto_scroll_control) withshow_todo_list_panel. - What: SSR mapping default and snake_case→camelCase mapping.
File:
apps/web/lib/ssr/user-settings.test.ts(or the existing test file coveringmapUserSettingsData/buildBehaviorFieldsif named differently — locate via the existingshowTranscriptAutoScrollControlassertion and add a sibling case). How: unit test assertingshowTodoListPaneldefaults tofalseand maps fromshow_todo_list_panel: true. - What:
TodoListPanelSettingsrenders the current value, stages a draft, and callsupdateUserSettings({ show_todo_list_panel })+setUserSettingson save. File:apps/web/components/settings/todo-list-panel-settings.test.tsx. How: component test mirroringunread-divider-settings.test.tsx's structure (mockupdateUserSettings, toggle the switch, trigger save via the settings save-provider, assert the call and store update). - What:
resolveConditionalTodoPanelActionreturns"add"/"remove"/"none"for every combination of setting value and panel presence; the deferred effect never fires renders/looks up state beforehasApi. File:apps/web/components/task/dockview-todo-panel-sync.test.ts. How: unit tests mirroringdockview-review-panel-sync.test.ts's structure for the decision function andsyncConditionalTodoPanel's add/remove calls against a mockedDockviewApi. - What:
todospanel rendersTodoIndicator-equivalent rows for a session with entries, and an empty state for a session without any. File:apps/web/components/task/dockview-shared.test.tsx(new, or added to an existing panel-content test file if one already coversPlanContent/ChangesContent). How: renderrenderPanel("todos-panel-id", "todos", {})inside the relevant store/portal test harness with seededsessionTodosstate, assert rendered rows/empty state.
E2E Tests (Iteration 1)
- Scenario: GIVEN the preference is off, WHEN a task opens, THEN no Todos
tab exists in the right panel. File:
apps/web/e2e/tests/settings/todo-list-panel.spec.ts. What to verify: right-panel tab strip has no "Todos" tab. - Scenario: GIVEN the preference is off, WHEN the user turns it on in
Settings > Generaland saves, THEN the active task's right panel gains an inactive "Todos" tab beside Files and Changes without changing the currently selected tab. File: same spec file. What to verify: tab strip gains "Todos"; previously active tab (e.g. "Files") remains active; selecting "Todos" shows the checklist or its empty state. - Scenario: GIVEN the preference is on, WHEN the user turns it off and saves, THEN the Todos tab disappears from the currently open task immediately, with no reload. File: same spec file. What to verify: tab strip no longer has "Todos" after save, without a page navigation.
- Scenario: GIVEN a custom Default layout with
todosplaced in a specific group via the Layout Editor, WHEN the preference is on and a fresh task opens, THEN the Todos tab appears in that configured group. File:apps/web/e2e/tests/settings/layout-profiles.spec.ts(extend with one case) or the newtodo-list-panel.spec.tsfile. What to verify: the Todos tab is in the user-configured group/position, not the Files/Changes fallback.
Verification Results
Iteration 1 (shipped)
All 5 tasks done. Full E2E suite for this feature
(cd apps/web && pnpm exec playwright test e2e/tests/settings/todo-list-panel.spec.ts)
passes (3/3), plus a joint run with layout-profiles.spec.ts to confirm no
regression in the two Dockview component registries this feature's fixes
touched (7/7). Re-ran backend
(go test ./internal/user/... ./internal/backendapp/...): every
internal/user/* package passes; internal/backendapp has the same 2
pre-existing failures Task 01 already documented
(TestDetectBranchRemote_ReturnsConfiguredUpstream,
TestDetectBranchRemote_NoUpstreamFallsBackToOrigin), a local GPG
commit-signing environment issue unrelated to any file this feature
touches. Frontend unit (pnpm exec vitest run, full components/task/ +
components/settings/ + settings/WS mapping tests), pnpm run typecheck,
and pnpm run i18n:check all clean. Full findings, including two product
bugs the E2E pass caught that unit tests could not (missing todos entries
in the desktop workbench's and Layout Editor's — as opposed to the Office
workbench's — separate Dockview component registries), are in Task 05's
Results section.
Iteration 2 (done)
Adversarial review loop (DeepSeek V4 Pro, sub-tasks): round 1 APPROVE
(qualified) → N1/N3 fixed (b2ae04fd), N2 deferred; round 2 APPROVE → F1
(per-field dirty) / F2 (single predicate computation) fixed (11cfe336);
round 3 APPROVE with no new findings (round-2 fixes re-verified). Loop
converged; details in task-07/task-08 Results.
All 4 tasks done. Backend
(cd apps/backend && go test ./internal/user/... ./internal/backendapp/...):
all internal/user/* packages ok; internal/backendapp ok (the two
pre-existing GPG-environment failures recorded in Task 01 did not reproduce
here). Frontend unit (cd apps/web && pnpm exec vitest run components/settings/todo-list-panel-settings.test.tsx lib/ssr/user-settings.test.ts lib/ws/handlers/users.test.ts hooks/use-ensure-user-settings.test.ts components/task/dockview-todo-panel-sync.test.ts — 101 tests total), pnpm run typecheck (with NODE_OPTIONS=--max-old-space-size=4096; bare run
crashes node on this VM), pnpm run i18n:check (all 5 gates), and
pnpm run i18n:pseudo (regenerated) all clean. E2E
(cd apps/web && pnpm e2e:raw --project=chromium tests/settings/todo-list-panel.spec.ts): 8 passed (5 v1 + 3 new). One
mid-flight regression found and fixed by the E2E pass: an unstable zustand
selector in useSyncTodoPanel (?? [] fallback) caused React error #185
(maximum update depth) on every task page; fixed to return the stable stored
array or undefined. Full findings in Task 09's Results.
Implementation Waves And Parallel Candidates
Wave 1:
Wave 2 (depends on Wave 1):
Wave 3 (depends on Wave 2):
Wave 4 (depends on Wave 3):
Wave 5 (Iteration 2, depends on Wave 4):
- Task 06 - Backend sub-setting field
- Task 07 - Frontend settings plumbing and UI
- Task 08 - Conditional pin sync
- Task 09 - E2E coverage
Execution is sequential in the primary conversation by default. Tasks 01 and 02 touch disjoint backend/frontend files and are the only parallel-safe candidates of Iteration 1; a user may explicitly authorize running them together. Iteration 2 tasks are sequential: 07 depends on 06's wire field and 08 depends on 07's frontend state plumbing.
Risks
- Iteration 2: the "not empty" predicate must use the panel content's exact
two-source fallback (live
sessionTodos.bySessionIdfirst, then persistedtodomessages viabuildTodoItems); using only the live slice would skip pinning for reopened completed sessions whose todos live in history (the exact regressiontask-05E2E "shows the checklist for a session whose todos were already persisted" covers). Subscribing tostate.messages.bySessionis safe because the desktop workbench's chat panel (useChatPanelState→useSessionMessages) is always mounted and fetches the session's messages. - Iteration 2: the sub-option must be hidden (inhibited), not rendered disabled, when the main preference is off, and both fields must always be included in the save payload so the sub-option's value survives main-off saves. A disabled-but-visible switch would fail the "inhibited" requirement.
useSyncReviewPanel's deferred double-requestAnimationFramepattern exists to avoid racing Dockview's own layout-restoration timing; the newuseSyncTodoPanelmust reuse that exact pattern rather than approximating it, or the panel can flicker or be added before the restored layout settles.- Extracting
TodoList/StatusIconfromtodo-indicator.tsxfor reuse in the new panel must not changeTodoIndicator's existing rendered output — the chat status-bar chip has its own snapshot/visual expectations. - The custom-Default placement lookup (
resolveConfiguredTodoPanelPlacement) must scan the sameuserDefaultLayoutshaperesolveConfiguredReviewPanelPlacementalready scans; a divergent lookup would silently placetodosin the wrong group for users who already configured a placement via the Layout Editor before turning the preference on.
Out of scope
- Everything listed in
docs/specs/ui/requirements/agent-todo-list-panel.md's Out of scope section (no backend todo-data changes, no removal ofTodoIndicator/TodoMessage, no content-driven auto-show by default, no closed-for-session suppression, no unseen-update badge, no mobile/tablet layout changes, no per-task override of the preference). - Iteration 2 adds no auto-removal behavior: the "Only pin when todo list is not empty" sub-option never removes an already-open Todos tab when the list empties, and never changes the master preference's removal semantics.