Repository navigation
[Bug]: Session hung forever after spawning subagents #2778
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
- Open a new T3Code session with Opencode provider and "Full access" mode
- Trigger a prompt like "Spawn a subagent to read the file
~/some-other-location-outside-your-project/some-file.mdand create a summary". Note that the file must be outside of the current opened project on T3Code
Expected behavior
The sub agent should report back to the parent session without asking for any additional permissions during "Full access" mode
Actual behavior
Wait a few minutes and note that it will never complete the job or timeout after 300000ms
The parent thread gets hung after spawning an OpenCode subagent, but the real problem is that the child session is waiting on an external_directory permission prompt that never surfaces in the T3 Code UI.
In my case:
- parent session:
ses_1b3d21dc0ffeG71m1u2qNoSXlZ - child session:
ses_1b3d19f6fffeIxa5icm1pIrpgt
The parent looked idle, but OpenCode logs showed the child explorer session emitted multiplepermission.askedevents and never received a reply
Impact
Major degradation or frequent failure
Version or commit
0.0.25-nightly.20260515.295
Environment
macOS 26.5 + Opencode 1.15.7
Logs or stack traces
OpenCode log evidence:
File:
~/.local/share/opencode/log/2026-05-21T214152.log
Relevant lines:
539: permission=external_directory ... action={"permission":"external_directory","pattern":"*","action":"ask"} evaluated
540: id=per_e4c7d26b30014G4qEQzoAFEVfa ... asking
541: bus type=permission.asked publishing
and later again:
853: permission=external_directory ... action={"permission":"external_directory","pattern":"*","action":"ask"} evaluated
854: id=per_e4c81d383001nBa06Q0YSUvuij ... asking
855: bus type=permission.asked publishing
No corresponding permission.replied event was surfaced in the UI.
Eventually the session was canceled:
860-861: session.prompt ... cancel
862: error=Aborted processScreenshots, recordings, or supporting files
No response
Workaround
Add the files that the agent has to access inside the same project so it can see them
Reacted by Ishan Ratnayake, Sean McNamara, Lars van der Bijl, Sayrix, Paul Shippy and adem chaabani
Activity
docs: add review of upstream PR pingdotgg#2829 orchestration v2 provi…
imadtg commentedon Aug 26, 2026
Fresh reproduction of this failure on a current build, without a pending permission prompt.
Environment:
0.0.34-nightly.20260826.11881.18.21opencode/x-preview-f-freeObserved timeline (UTC):
03:11:56— parent turn started03:15:25— one child/subagent session was created03:19:32— child session received its final updatebusyindefinitely04:23:17remained pending behind the active turnEvidence:
/session/statusreported exactly two busy sessions: the affected parent and its child./permissionand/questionboth returned empty lists.busystatuses and one retry, but noidleorsession.error.The current OpenCode adapter ignores events whose session ID differs from the parent session before processing them. It also completes the parent turn only after receiving
session.status = idle. There appears to be no timeout or reconciliation path when a child remains busy but stops producing events.This looks like the same overall failure as #2778, but it demonstrates that the child can wedge without an outstanding permission or question request.
Recovery was possible without database writes: terminating only the dedicated
opencode serveprocess caused T3 Code to mark the turn aserror, transition the session tostopped, clear the queued pending turn, and preserve the thread history.Triage performed by Codex (GPT-5.6-SOL).
t3dotgg commentedon Oct 21, 2026
Note
🤖 Claude Opus 5.5 responding on behalf of Theo
Thanks for the report. This is fixed on main in #2829. Please test on the nightly built from main on 2026-10-21, or on the next stable release. If the problem still occurs there, please open a new issue that links to this one, with your version and steps to reproduce it.