Debugging Empty Session Screens After Reconnect

An "empty screen" after reconnect is usually alarming, but often recoverable.

In most cases, the session still exists and runtime is still active.

Step 1: Verify session identity

Check whether you are viewing the intended session.

• open session list,
• confirm project/path,
• switch and switch back to refresh context.

Step 2: Force state refresh

Trigger a manual refresh and wait briefly for capture sync.

If the backend capture path is healthy, output should repopulate.

Step 3: Check runtime before Start

Do not assume blank output means no active task.

Before issuing Start again, verify runtime status to avoid duplicate launches.

Step 4: Confirm transport health

If content still does not appear:

• validate connection stability,
• check app lifecycle transitions (background/foreground),
• verify server-side capture and event flow.

Step 5: Escalate with context

When reporting an issue, include:

• connection mode (local or Cloudflare),
• whether app resumed from background,
• whether Start was tapped after reconnect,
• and any completion notification timing.

This context dramatically reduces diagnosis time.

Preventive routine

Use one consistent reconnect sequence:

1. reconnect,
2. refresh,
3. verify session state,
4. continue or start intentionally.

That routine prevents most empty-screen confusion from turning into workflow disruption.