[Bug]: Typing a URL in the server-runtime browser address bar does not navigate (WSL) #26147

Activity

1. spsrohan commented on Nov 10, 2026

   

   spsrohan

   on Nov 10, 2026 – with ChatGPT Codex Connector

   Last edited by spsrohan

   More actions

   This still occurs in T3 Code 0.1.8 on the Windows desktop app connected to a local WSL2 server. Both the desktop client and server report 0.1.8.

   Typing a URL and pressing Enter adds it to “Recently used”, but the browser returns to the blank start page without loading it. I reproduced this with glassregister.societ.com, with an explicit https:// prefix, and with another site, google.ca.

   Floating preview is enabled. The browser worked for me previously, though I had not used it for roughly two weeks.

   This appears consistent with the regression described in #31172. I have not tested that proposed fix.

   Comment drafted with Codex.

   
2. Aries1542 commented on Nov 11, 2026

   

   Aries1542

   on Nov 11, 2026

   More actions

   Another reproduction on t3 v0.1.7: Windows desktop app with the server in WSL2 (Ubuntu 24.04). The symptom is slightly different from the original report, and it matches the cause described in #31172. The panel draws a desktop-local page, while the address bar and the agent's tools follow the server tab.

   Steps

   1. An agent opens a server-runtime tab with preview_open (target environment-port 4200), logs into the app and navigates to /users/payments/3.
      • preview_status reports owner: "agent" and visible: false, even after preview_open with open: true.
      • t3_preview_list reports runtime: "server".
   2. The user looks at the panel.

   Actual behavior

   • The address bar shows http://localhost:4200/users/payments/3. The page in the panel is the app's login screen, because it is a separate desktop-local page with no session. The agent's screenshots of the same tab show the logged-in page.
   • The user types google.com in the address bar. The panel's page does navigate to Google, but the address bar immediately reverts to http://localhost:4200/users/payments/3.
   • The server tab never sees that navigation. t3_preview_list still shows the localhost URL. In server.trace.ndjson, the only navigate spans are the agent's preview_navigate calls.

   The user and the agent therefore look at two different browsers. The URL bar shows the agent's tab, and the page shows a local one.

   Expected behavior
   The panel streams the server tab the agent is driving, and typing in the address bar navigates that tab.

   Impact
   An agent can't hand a prepared page (logged in, test data loaded) to the user in the built-in browser.

   Workaround
   Use a normal browser at the same localhost URL, or log in again inside the panel's local page and ignore the address bar.

   Comment drafted with Claude Code.
3. juliusmarminge commented on Nov 12, 2026

   

   juliusmarminge

   on Nov 12, 2026

   Member

   More actions

   This is the same problem as #35424, so I'm closing it in favour of that one. If it is different, say how and it will be reopened.
4. juliusmarminge

   closed this as duplicateon Nov 12, 2026