[UX] Multi-tab mode isolation — follow-up issues from PR #909

[easonLiangWorldedtech]

[UX] Multi-tab mode isolation — follow-up issues from PR #909

Summary

PR #909 implemented per-view state isolation for parallel Roo Code tabs, allowing each tab to maintain its own mode, apiConfiguration, and profile selection. However, several UX gaps were identified during the review process that affect the user experience in multi-tab scenarios.

This issue tracks all follow-up improvements as sub-issues below.

---

Sub-Issues

🔴 High Priority

• [UX] SettingsView shows stale mode/apiConfig in multi-tab mode #914 [UX] SettingsView shows stale mode/apiConfig in multi-tab mode — cachedState not synced with view-local state changes
• [BUG] Concurrent task history updates from parallel tabs may cause lost entries #920 [BUG] Concurrent task history updates from parallel tabs may cause lost entries — cross-instance race condition

🟡 Medium Priority

• [UX] Flash of incorrect mode/apiConfig when opening new editor tab #915 [UX] Flash of incorrect mode/apiConfig when opening new editor tab — async loadViewState() causes flicker
• [UX] Add visual indicator for per-view mode isolation #916 [UX] Add visual indicator for per-view mode isolation — users can't tell which tabs use different modes
• [UX] Add save indicator for per-view API configuration changes #917 [UX] Add save indicator for per-view API configuration changes — no "unsaved" badge when view-local state differs from global
• [BUG] Parent-child task delegation across parallel tabs may lose state #921 [BUG] Parent-child task delegation across parallel tabs may lose state — atomicReadAndUpdate doesn't cover cross-tab scenario

🟢 Low Priority

• [UX] Wire SettingsView Save button to syncViewStateToGlobal #918 [UX] Wire SettingsView Save button to syncViewStateToGlobal — manual sync command for power users
• [UX] Add telemetry/tooltip for view-local state persistence limitation #919 [UX] Add telemetry/tooltip for view-local state persistence limitation — explain session-only behavior after extension reload

---

Related PR

• PR fix(webview): isolate parallel provider view state #909: fix(webview): isolate parallel provider view state — fix(webview): isolate parallel provider view state #909
• Issue [BUG] Multi-tab mode/model settings get overwritten by latest task #908: Original bug report for multi-tab mode overwrite issue (closed by PR fix(webview): isolate parallel provider view state #909)

---

Implementation Notes

All sub-issues should:

1. Reference the specific code locations identified in PR fix(webview): isolate parallel provider view state #909 review comments
2. Include test coverage for parallel mode scenarios
3. Maintain backward compatibility with single-tab usage
4. Consider performance impact (especially for Issue [UX] Flash of incorrect mode/apiConfig when opening new editor tab #915 which affects tab open speed)

[easonLiangWorldedtech]

Try to add sub-issues, but it looks like I don't have the permission.