Repository navigation
[Bug]: Completed remote dispatches stay visible below collapsed "Previous agents" #26883
Description
Before submitting
- Searched open and closed reports. Related reports and the difference in scope are explained below.
- Included the observed behaviour, reproduction sequence, source evidence and verification limits.
Area
apps/web — desktop thread details / Lineage panel.
Steps to reproduce
- From a parent thread, dispatch a task locally and another task to a linked environment.
- Let both tasks complete, then open the parent's Lineage panel.
- Collapse Previous agents.
- Compare the completed local agent with the completed remote dispatch.
This sequence describes the user-observed workflow. A screenshot of an existing multi-environment run establishes the visible symptom; I did not launch a fresh minimal UI reproduction.
Expected behavior
Completed remote dispatches should participate in the collapsible completion history, consistently with completed local agents. Collapsing Previous agents should hide those completed rows too.
Actual behavior
Completed local agents are grouped inside the collapsed Previous agents section. Completed remote dispatches remain visible in a separate, unlabelled list immediately below that section, showing a destination and Done.
The observed panel had this layout:
Lineage · 1 running
[running local agent]
Previous agents 15 >
[completed remote dispatch] on [environment] · Done
[completed remote dispatch] on [environment] · Done
...
The remote rows look visually associated with the history heading while remaining outside its collapse control and count. Long remote runs therefore leave a growing list of completed dispatches visible even with completion history collapsed.
Source evidence
At 6d82a22e9df93f1dd14afa89d820b7dd1b624eef:
- Lines 450–463 partition local relationship rows by settled status and create the collapsed Previous agents group.
- Lines 465–469 select remote dispatches by the presence of
remoteChild, without a status filter. - Lines 859–873 render those remote rows separately after the local groups. That list has no collapse control and is passed
hiddenCount={0}.
This source structure supports the screenshot's local/remote grouping difference. It is not proof that the installed frontend bundle exactly matches this commit.
Impact
Minor bug or occasional failure. Completion history cannot be collapsed consistently, and the section's scope is unclear. No task loss, incorrect completion status or provider failure is established.
Version or commit
Observed on 29 October 2026. The connected local server reports 0.1.4-nightly.20261029.3853. Desktop client build was not independently identified. Source inspection is pinned above.
Environment
Linux x64 local server, desktop Lineage UI, Codex parent with local and linked-environment dispatches.
Related reports
- iPhone app lists cross-machine delegated tasks as top-level threads; desktop nests them under their parent #26854 concerned mobile thread-list nesting and counts. Its closing comment verifies the mobile navigation fix. Its body also mentioned desktop drawer presentation, but that desktop symptom was not resolved by the closing explanation. This issue isolates the desktop completion-history grouping problem.
- [Bug]: Thread details panel folds the subagents a thread just ran into "Previous agents", so they look gone #26411 asks for recent completed local subagents to remain visible instead of immediately folding into history. This report concerns remote dispatches bypassing that history group altogether, not the recency policy for local agents.
Screenshots and verification limits
The user supplied the screenshot described above. The original is withheld because it contains private task titles; no private project names, environment labels or transcript content are included here.
No fresh browser replay, frontend-bundle inspection, patch or regression test was performed. No installed application changes were made.
Workaround
No verified collapse control exists for these remote rows in the inspected component. Closing the details panel hides the entire panel, including active work.
Investigated with Codex (gpt-6.1-sol) in T3 Code.
Activity
Furizou commentedon Oct 30, 2026
Seeing the same thing on a long-running parent thread that dispatches most Mac-side work to a linked environment (~58 remote dispatches in one day). The completed/failed/stopped remote rows keep stacking up outside Previous agents, so the panel stays cluttered even with history collapsed.
What I tried on the parent side, none of which moves a remote row into the collapsed group:
t3_thread_organize settle);t3_thread_organize archivewith the targetenvironmentId) — the archived thread is gone from that machine's thread list, but its row is still in the parent's Lineage;task_statuson the remote taskId, which per its description marks the result delivered).Failed and stopped remote rows behave the same as Done ones. That fits the source evidence above: remote rows are selected by the presence of
remoteChildwith no status filter.ebrardushullovcii commentedon Oct 30, 2026
Same here on Windows 11, desktop nightly 0.1.6-nightly.20261030.3917.
Lineage shows "1 running", then "Previous agents" collapsed with a count of 4. Below it, seven remote agent rows stay visible: five Done, one Running, then one more Done. The one agent still working is mixed in with the finished ones, so it's hard to spot.
In another thread, the running agents sit above "Previous agents" and the finished ones stay hidden while that group is collapsed. Remote agents should follow the same grouping. PR #26576 looks like it does this.
No screenshots because they show private task details.
guryanov-a commentedon Nov 1, 2026
Same here, with failed rows: a thread that continued work from another machine shows 7 "on · Failed" rows under a collapsed "Previous agents (9)". The long suffix cuts the agent names to one letter. I'd like failed remote agents folded too, as #26576 does; the "N failed" badge on the collapsed group is enough to show that something failed. Windows 11, T3 Code Desktop 0.1.6 (stable).
pitijk commentedon Nov 6, 2026
Confirming the same visible symptom on macOS, observed on 6 November 2026.
The supplied desktop screenshot shows:
All three completed remote rows remain visible below the collapsed history group. This makes it unclear why these completed tasks are still displayed separately while 66 previous agents are hidden. The screenshot does not establish that the completed tasks are still executing; this confirmation concerns completion-history grouping only.
Environment: T3 Code Nightly desktop on macOS 26.6.2. The installed app's
CFBundleShortVersionString, read during this investigation, is0.1.7-nightly.20261104.4151. The screenshot itself does not show a version; the remote server version was not checked.Evidence/limits: this is a user-observed existing long-running thread with linked-environment tasks, not a newly executed minimal reproduction. The original screenshot is withheld because it includes private task and machine names. No restart, settle/archive workaround, source-level diagnosis, or patch verification was performed for this confirmation.
Investigated with Codex (gpt-6.1-sol) in T3 Code.
mellismas commentedon Nov 6, 2026
Same on Windows 11, T3 Code Nightly, observed 2026-11-06. A parent thread that dispatches build and review work to a linked Windows machine shows "Lineage · 1 running", then "Previous agents 50" collapsed, then 7 remote rows below it, each "on · Done", and the one running remote agent is the last row in that list. With many dispatches the running one ends up at the bottom, and you have to know to scroll the panel to find it. Expected: remote rows follow the same grouping as local agents, with running ones above "Previous agents" and finished ones folded into it (with #29485's status-first sort applied).
Screenshot (machine names redacted): the remote rows (red) sit below the local agents' "Show 12 more" fold instead of inside it, and the one running agent (yellow) is the last row.
juliusmarminge commentedon Nov 9, 2026
Thanks for the detailed report! #29285, merged as 6dcaf6c, moves finished remote agents into Previous agents and keeps running ones in the active group.