You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Incognito browser visits persist in normal project history #29430
Incognito browser address-bar visits are saved in a project's normal Recently used history and survive quitting/relaunching the desktop client. Settings say Incognito data is cleared when the app closes.
Reproduction on upstream ac8dce0 (the affected source is unchanged on current main edc37c9):
Open a project's browser in Incognito and enter a unique local HTTP URL.
Open a Default tab and enter a separate regular control URL.
Open another empty Default tab and inspect Recently used.
Quit/relaunch Electron with the same isolated server home and Electron user-data profile, and inspect Recently used again.
Observed: both Incognito and regular URLs appear in normal Recently used and persisted t3code:browser-history:v1, including after native process restart. Expected: only the regular URL enters normal project history.
Verified in real dev Electron with native bridge, non-headless WebContents guest and CDP webview target; no mock bridge or streamed-browser substitution. Before and after restart, the baseline has both synthetic URLs and the focused fix retains only regular. The restart checks verify a new browser identity, unchanged app origin, and a retained localStorage sentinel. All four pre/post results pass.
The same persistent-history boundary also accepts an Incognito page's title for a same-URL regular entry. Four fail-before store regression rows cover visit queue exclusion and title filtering with either settle timing. Native card-click and title-update interactions were not manually exercised; the native reproduction above covers address-bar/history/restart behavior.
Scope is one obvious persistent-history privacy defect, restoring established Incognito behavior. No new setting/workflow, cleanup of old entries without profile provenance, other URL metadata cleanup, or cookie/session lifetime changes.
Reported and implemented with GPT-6.1 Sol (xhigh) in the Codex harness through T3 Code.
Activity