[BUG] Grey Screen

[imaginationchristmas]

Problem (one or two sentences)

There is a grey screen that appears once in the Roo code panel. When working, it just goes to a grey screen and I am not sure why. I am needing to close out of VScode and come back in to resolve and continue working.

Context (who is affected and when)

It happens just running normally. During a session with Claude, it just appears and I can not see the dialog.

Reproduction steps

Macbook Pro 14"
Running PPQ.ai API

Expected result

Should just not show a grey screen (?)

Actual result

Grey screen appears while working

Variations tried (optional)

No response

App Version

3.51.1

API Provider (optional)

OpenAI Compatible

Model Used (optional)

Claude Sonnet 4.6 and others

Roo Code Task Links (optional)

No response

Relevant logs or errors (optional)

[roomote-v0]

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

Root cause analysis:

The grey screen is most likely caused by the webview failing to receive (or losing) its initial state hydration from the extension host. In App.tsx:219-221, when didHydrateState is false, the component returns null -- rendering absolutely nothing, which appears as a blank grey panel. This can happen when:

1. The extension host restarts or becomes temporarily unresponsive during a session
2. A race condition causes the webviewDidLaunch message to be sent before the extension is ready to respond
3. The webview is moved/reloaded by VS Code (e.g., panel rearrangement) and the state message never arrives

Currently there is no retry mechanism or visual feedback when in this state -- the user just sees grey.

Proposed fix:

1. Add a loading/retry UI in App.tsx -- Instead of returning null when !didHydrateState, show a lightweight loading spinner so the user knows the panel is alive
2. Add a retry mechanism in ExtensionStateContext.tsx -- If the state has not been hydrated within a reasonable timeout (e.g., 5 seconds), automatically re-send the webviewDidLaunch message to request state again. This handles cases where the initial message was lost or the extension host was not ready
3. Add a "Retry" button -- After multiple failed attempts (e.g., 3 retries), show a visible "Retry Connection" button so the user can manually trigger reconnection without restarting VS Code

This approach addresses the symptom (grey screen with no feedback) and the root cause (lost state messages with no recovery path).

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