Prompt/thread link landing page leaves the browser tab open after handing off to the desktop app, even with "Remember my choice"

Open Beginner friendly
  • Is something wrong?
#33,634 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
83/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript
Domain
desktop, web-dev

Research direction

Start with apps/web/src/components/promptLinks/HostedPromptLinkLanding.tsx, especially lines 130–134, and trace the remembered-app handoff effect. Check how the landing page handles the desktop deep link and tab state after the handoff. Done means remembered links open in the desktop app without leaving an unusable landing page or stale tab.

Written by the indexing model from the issue text.

Description

via-triage
What happened

I clicked a T3 Code link in Chrome, picked "Open in desktop app" with "Remember my choice" checked, and the desktop app opened the link. The Chrome tab stayed open on the landing page. Every later link leaves another stale tab.

Diagnosis

apps/web/src/components/promptLinks/HostedPromptLinkLanding.tsx:130-134: once the opener is remembered as "app", the effect sets window.location.href = deepLink and stops there. It never tries window.close() (Chromium allows it for a single-history-entry tab opened from a link), and it does not replace the page with an "Opened in T3 Code, you can close this tab" state. The file is unchanged since v0.1.8.

Steps to reproduce
  1. Have T3 Code Desktop installed and running.
  2. In Chrome, open a T3 Code prompt or thread link that lands on the hosted page.
  3. Check "Remember my choice" and click "Open in desktop app". Allow the t3code:// handler.
  4. Open another link. The app opens it automatically, but the tab stays open on the landing page.
Version

T3 Code Desktop 0.1.8 (AppImage).

Environment

Ubuntu 26.04.1 LTS, kernel 7.0.0, KDE Plasma / KWin 6.6.6, Wayland (--ozone-platform=wayland), Google Chrome 156.0.8078.79.

Evidence
Source reference above. The desktop trace shows `DesktopWebLinks.receive` for every click, so the handoff itself works.
Related issues

#11865, #9745 (deep link routing, closed).

Fix applied or workaround

Close the tab by hand.

Filed by

Claude Opus 5.5 (claude-opus-5-5) via Claude Code, using the T3 Code triage playbook. Evidence collected read-only on the affected laptop.

Dominant language
TypeScript
Stars
24.8k
Forks
6.4k
Avg merge
13h 9m
Merged PRs (30d)
187

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from pingdotgg/t3code

All issues in pingdotgg/t3code

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.