pingdotgg / pingdotgg/t3code

[Bug]: Clicking a completed-thread notification does not reveal T3 Code on Linux

Open
#12,500 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

accepted bug via-triage
Dominant language
TypeScript
Stars
23k
Forks
5.9k
Avg merge
11h 14m
Merged PRs (30d)
357

Description

Before submitting
  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.
Area

apps/desktop

Steps to reproduce
  1. On Linux, enable system notifications for completed threads.
  2. Start a turn, then switch away from or minimize T3 Code before the turn completes.
  3. Wait for the "Thread completed" system notification.
  4. Click the notification.
Expected behavior

T3 Code should reveal and focus its desktop window, then open the completed thread.

Actual behavior

Clicking the notification does not bring T3 Code back to the foreground. The user remains in the current application.

The shipped renderer click handler closes the notification, calls window.focus(), and navigates to the thread route:

notification.addEventListener("click", () => {
  notification.close();
  window.focus();
  navigate({
    to: "/$environmentId/$threadId",
    params: { environmentId, threadId },
  });
});

On Linux, renderer window.focus() does not reveal or restore the Electron BrowserWindow. Navigation may happen inside the hidden window, but the application is not returned to the foreground. The click path needs to ask the desktop main process to reveal the window before or alongside navigation.

Impact

Minor bug or occasional failure

Version or commit

v0.0.43-nightly.20260918.1895

Environment

Fedora Linux 44, kernel 7.1.13-200.fc44.x86_64, GNOME on Wayland, T3 Code desktop nightly

Logs or stack traces
No error is shown.
Workaround

Manually return to T3 Code and select the completed thread.

Contributor guide

Open the contributing guide

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.

Research direction

Start from the shipped renderer notification click handler in apps/desktop and trace how it communicates with the desktop main process. Verify the Linux notification path on Fedora/GNOME, then ensure clicking "Thread completed" reveals and focuses the BrowserWindow before or alongside navigation to the completed thread. Confirm the existing thread navigation still works and the window returns to the foreground.

Written by the indexing model from the issue text.

Assessment

Tech stack
electron, typescript
Domain
desktop
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.