[Bug]: Android Browser Preview stalls on agent-controlled tabs while Windows is locked

Offen
#39,069 2 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
42/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
android, react-native, typescript

Rechercherichtung

Start by tracing remote Browser Preview across apps/desktop and apps/mobile, comparing how agent-controlled tabs and manually opened tabs provide frames while Windows is locked. Read the related work in #34935, #27092, and #27735 for capture and fallback behavior. Reproduce the Win+L steps with Android and inspect host logs; done means the agent-controlled preview connects while the Windows session is locked.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Before submitting
  • I searched existing issues. #23139 describes a similar symptom when a Windows window covers T3 Code. The trigger here is locking the Windows session with Win+L while T3 Code is in the foreground.
  • I included the steps and observations needed to reproduce the failure.
Area

apps/desktop and apps/mobile, remote Browser Preview

Steps to reproduce
  1. On a Windows laptop, have a T3 Code agent open a browser tab and retain control of it.
  2. Press Win+L to lock Windows.
  3. In the native Android app, open the same thread and tap the globe icon to open Browser Preview.
  4. Unlock Windows and check the same preview again.
  5. For comparison, repeat the locked-host check with a browser tab opened manually in the T3 Code desktop app.
Expected behavior

The Android app can display and interact with the preview while the Windows host is awake and its session is locked.

Actual behavior

With the agent-opened and agent-controlled tab, Android stays on “Connecting to browser” while Windows is locked. Unlocking makes the preview appear immediately. A tab I opened manually in the desktop app was accessible from Android while Windows was still locked.

Impact

Major degradation. Android Browser Preview stalls for the agent-controlled tab while the host is locked.

Version or commit

T3 Code Nightly 0.1.11-nightly.20261119.4918, recorded in the Windows host logs. Android app 2.3.0.

Environment

Windows 11 laptop hosting T3 Code and the native T3 Code Android app as the remote viewer.

Workaround

Unlocking Windows restores the agent-controlled preview. Manually opened tabs were accessible while the host was locked.

Related issues and PRs
  • #23139 tracks the covered-window case. #34935 changes capture-time throttling and describes a minimized Linux/Xvfb reproduction. Its effect on Windows Win+L with Android remains unverified.
  • #27092 covers screen locking on macOS and limits its rendering and capture changes to that platform.
  • #27735 proposes a headless fallback for a desktop tab that cannot produce frames and describes a minimized Linux reproduction.
Vorherrschende Sprache
TypeScript
Sterne
24.8k
Forks
6.4k
Ø Merge
4 Std. 29 Min.
Gemergte PRs (30 T.)
488

Entwicklungsumgebung

In Codespaces öffnen

Startet den Dev-Container des Projekts im Browser, mit Ihrem eigenen GitHub-Konto.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus pingdotgg/t3code

Alle Issues in pingdotgg/t3code

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.