Environment
- Surface: Windows ChatGPT Desktop
- App version: 26.928.31416
- Affected feature and model, if relevant: dot subagents, automated task management, and browser permissions; model not confirmed
Bug
New subagents could not be created because of a thread limit. Five completed subagents and one pending_init subagent were listed, but the assistant had no available tool to delete or archive them. It was unclear whether completed tasks still counted towards the limit.
Deleting an automated task only disabled it (is_enabled=false). The assistant initially reported it as removed, then clarified that permanent deletion was not confirmed.
Facebook actions also remained inconsistently blocked after renewed authorisation: one page read succeeded, while subsequent actions were denied. The effective permission scope was unclear.
Expected: clear task-limit accounting, cleanup and recovery controls, accurate deletion status, and actionable permission-denial explanations.
Reproduction
- Use dot for several delegated tasks and let some finish.
- Ask it to create another subagent for an independent website review.
- After the limit error, ask it to delete or replace completed subagents.
- Separately, ask it to delete an automated task and verify whether it was deleted or only disabled.
- For the permission issue, authorise a previously denied Facebook action and check whether the intended access is restored.
These describe the observed sequence; the exact conditions needed to reproduce it are not yet isolated.
Diagnostics
Exact error: “agent thread limit reached”
Other observed states: pending_init; is_enabled=false after a deletion request
When it happened: 1 October 2026, approximately 11:05–11:25 pm AEST (UTC+10). Facebook permission issues occurred earlier that day.
How often: repeated subagent-creation failures and Facebook permission denials; one automated-task deletion attempt resulted in disabling only.