You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: A task delegated to a linked environment never shows its question or approval on the parent #26527
I searched existing issues and did not find a duplicate.
I included enough detail to reproduce or investigate the problem.
Area
apps/server
Steps to reproduce
Turn on Linked environments (Settings → Labs) on two T3 Code servers, a "laptop" and a "box", and link the laptop to the box with approval-required access.
In a laptop thread, have the agent call delegate_task with target.environmentId set to the box, mode: "wait", and a task that asks the user a question or runs a command that needs approval.
The task on the box stops on the question or the approval.
Expected behavior
The parent on the laptop shows the remote task's question or approval the way #15082 made it show a local task's, says which environment asks, and sends an answer given on the parent to the task. delegate_task and task_status report hasPendingQuestion / pendingApproval, and mode: "wait" ends on them.
Actual behavior
Nothing reaches the laptop. The sidebar, web, and mobile clients connected to the laptop show no request, and delegate_task / task_status report hasPendingQuestion: false and pendingApproval: null, so the wait call runs until it times out. The task only moves on if someone opens the box and answers there.
Reproduced on T3 Code 0.1.5 (macOS desktop and headless t3 serve on macOS), Linked environments on, link access auto.
Parent thread on Mac A started delegate_task with target.environmentId set to linked Mac B, mode: "async".
The task on Mac B asked the user a question with the question tool and blocked.
Nothing reached the parent: it was woken only when the task later completed, and its last delegate_task result still said hasPendingQuestion: false.
The child thread appears only in the parent's details panel (Lineage). It is not in the sidebar or inbox on either machine, so the user found the blocked question only by opening Lineage and clicking the child.
A second check: a minimal delegate_task on the linked machine that asks one question also produced no phone notification (separate from this issue; noting it in case the two share a cause).
Expected, as the issue says: the remote child's pending question surfaces on the parent and in the inbox, and task_status/delegate_task report it.
Still reproduces on 0.1.7-nightly.20261101.4048 (88f6113), macOS arm64.
The parent thread is on linked environment A. Its delegated Codex child is on environment B, and the child asked a question (AskUserQuestion).
The parent's timeline banner did show "Subagent needs input … Open question". But the sidebar row for the parent stayed "Waiting" and never switched to Input, so nothing in the thread list showed that a person was needed.
Activity
kukitch commentedon Oct 31, 2026
Reproduced on T3 Code 0.1.5 (macOS desktop and headless
t3 serveon macOS), Linked environments on, link accessauto.delegate_taskwithtarget.environmentIdset to linked Mac B,mode: "async".delegate_taskresult still saidhasPendingQuestion: false.delegate_taskon the linked machine that asks one question also produced no phone notification (separate from this issue; noting it in case the two share a cause).Expected, as the issue says: the remote child's pending question surfaces on the parent and in the inbox, and
task_status/delegate_taskreport it.EtanHey commentedon Nov 2, 2026
Still reproduces on
0.1.7-nightly.20261101.4048(88f6113), macOS arm64.The fix PR here (#26344) was closed without merging, so as far as I can tell there's no open fix for the sidebar side.
Posted from a T3 Code triage session (Claude Opus 5.5 in Claude Code).