pingdotgg / pingdotgg/t3code

[Bug]: Active turn Tasks list disappears after an update-triggered relaunch

Open
#8,091 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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. Start a multi-step request that remains in flight long enough to show the attached Tasks tab above the composer.
  2. Expand the tab and confirm that the task list shows completed, current, and pending steps.
  3. While the turn is still running, accept an application update and let T3 Code relaunch.
  4. Reopen the same thread and wait for its provider session to reconnect.
  5. Observe that the turn continues, but the Tasks tab and task list do not reappear.
Expected behavior

Once T3 Code reconnects to the active thread, the composer should restore the Tasks tab with the latest progress for that turn. The task list should continue updating until the turn settles.

Actual behavior

The thread and provider session reconnect, and the turn continues in the background. The Tasks tab does not return, so the composer no longer shows the current, completed, or pending steps for the active turn.

Impact

Major degradation or frequent failure

Version or commit

Not provided.

Environment

T3 Code desktop app. Observed when an application update relaunches the app during an active multi-step turn. Provider and model were not specified.

Logs or stack traces
No error was observed.
Screenshots, recordings, or supporting files

No response

Workaround

Avoid relaunching T3 Code while a multi-step turn is in flight. No way to restore the Tasks tab after relaunch is known.

Additional context

The thread and active turn recover successfully, so the lost state is limited to task-progress visibility. The restored Tasks tab should remain tied to the resumed active turn and disappear normally when that turn settles or the user dismisses it.

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 in apps/desktop by reproducing the update-triggered relaunch during an active multi-step turn, then trace how the resumed thread and provider session restore task progress. Identify the state or UI path that restores the active turn and verify the Tasks tab returns with completed, current, and pending steps, continues updating, and disappears when the turn settles.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.