[BUG] No "View task" button displayed under the "Roo wants to create a new subtask"

[mdziekon]

Problem (one or two sentences)

In Session view, Parent task's view, some subtasks do not have the "View task" button, even though on the Session's list view, all Parent task's have access to the subtasks' list. The problem usually affect the entire session, but does not affect all sessions I have in the history (even pre v3.44.0 created ones).

Context (who is affected and when)

Users using Orchestrator mode, where subtasks are getting created.

Reproduction steps

1. Start a new session
2. Roo creates some subtasks and works on them
3. Pause the subtask's progress
4. Go back to parent task

Screenshots of the bug (broken parent task)

Session's list view

(all subtasks present)

Parent task's view

(bottom of an already completed subtask, missing "View task" button)

Screenshots of a session without this problem

(bottom of an already completed subtask, "View task" button present)

Expected result

All subtasks (completed or not yet completed) have "View task" buttons

Actual result

None of the subtasks have the button present

Variations tried (optional)

No response

App Version

3.44.0

API Provider (optional)

None

Model Used (optional)

No response

Roo Code Task Links (optional)

No response

Relevant logs or errors (optional)

[roomote]

I've analyzed this issue and here's my proposed implementation plan:

Root Cause Analysis

The "View task" button (internally called "Go to subtask") is displayed in ChatRow.tsx based on whether currentTaskItem.childIds contains a corresponding child task ID for each newTask message. The issue is that when viewing a parent task from history, the webview's currentTaskItem may not be properly synchronized with the latest taskHistory data.

Looking at the code flow:

1. In showTaskWithId() (ClineProvider.ts line 1710-1718), when a user clicks on a task from history:

   • createTaskWithHistoryItem(historyItem) is called
   • Only a chatButtonClicked action is posted to the webview
   • No explicit postStateToWebview() call is made

2. The webview's currentTaskItem is derived from the state message in ExtensionStateContext.tsx, but if a full state update is not sent after switching tasks, currentTaskItem may not be updated.

3. While taskHistoryItemUpdated messages can update currentTaskItem, this only works if prevState.currentTaskItem?.id === item.id. If currentTaskItem is stale or points to a different task, the update is skipped.

Proposed Fix

Modify showTaskWithId() in src/core/webview/ClineProvider.ts to explicitly call postStateToWebview() after createTaskWithHistoryItem():

async showTaskWithId(id: string) {
    if (id !== this.getCurrentTask()?.taskId) {
        const { historyItem } = await this.getTaskWithId(id)
        await this.createTaskWithHistoryItem(historyItem)
    }
    // Add this line to ensure currentTaskItem is synchronized
    await this.postStateToWebview()
    await this.postMessageToWebview({ type: "action", action: "chatButtonClicked" })
}

This ensures that when viewing any task from history, the webview receives a full state update with the correct currentTaskItem (including childIds), which will make the "View task" buttons appear correctly.

Why This Fixes the Issue

• The Session's list view works because it directly reads from taskHistory which has the correct childIds
• The parent task's chat view doesn't show buttons because currentTaskItem in the webview state isn't updated when switching tasks
• Adding postStateToWebview() ensures the webview gets the latest currentTaskItem with childIds populated

Please mention @roomote in a comment saying that you approve this plan, and I'll proceed with the implementation.