Repository navigation
[Bug]: Thread list shows no tag for a thread with a bound scheduled task (looks idle) #27243
Closed
BlackPhoenixSlo
started this conversation in
Ideas
Replies: 1 comment
|
Closing as a duplicate of #16550, which tracks the same request. Please follow along there. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Before submitting
Area
Mobile app: thread list (Threads tab)
Steps to reproduce
t3_thread_launch, then callschedule_taskwith{"type":"interval","everyMs":3600000}. The task binds to that thread by default.completed.Expected behavior
The row shows that the thread still has future work coming, for example a "Scheduled · next 01:09" tag. The
waitingrows nearby get a tag, and a thread with an enabled bound scheduled task matters just as much.Actual behavior
The row shows only the relative time ("3m"), so it looks like a finished, idle thread. It sits in the active list with nothing to tell it apart from threads that have nothing coming. Meanwhile:
list_scheduled_tasksreturns an enabled task withboundThreadIdset to this thread,nextRunAt: 2026-10-30T00:09:33ZandlastRunStatus: never.t3_thread_readreturnsstatus: completed,pendingRequestCount: 0,snoozed: false. Nothing in the thread payload refers to the bound task.Searching the repo,
nextRunAtis only used in the mobile app underfeatures/settings/(SettingsScheduledTasksRouteScreen.tsx,scheduledTaskPresentation.ts). The thread list doesn't seem to read scheduled tasks at all. On the web,ThreadAutomationsPanel.tsxshows them, but only after you open the thread. (This is inferred from a code search; I haven't traced it at runtime.)Impact
When I orchestrate from my phone, I can't see which threads are parent threads that will wake up on a schedule and which are just done. It's easy to settle or forget a thread that still has hourly checks scheduled.
Version or commit
Desktop app 0.1.2 (T3 Code Beta) on macOS, with the current iOS mobile client.
Environment
macOS 15 (Darwin 24.6) host, iPhone client, Claude provider threads.
Workaround
Open each thread, or go to Settings → Scheduled tasks and match the tasks to threads by hand.
All reactions