Skip to content

[Bug]: After upgrade to Mac OS 26.6.2 T3 Code crashes periodically #8221

New issue
New issue
Closed as not planned
Closed as not planned
[Bug]: After upgrade to Mac OS 26.6.2 T3 Code crashes periodically#8221
Labels
bugSomething is broken or behaving incorrectly.needs more infoInitial triage showed no bug. Awaiting more infoneeds-triageIssue needs maintainer review and initial categorization.

Description

@roc-ops
roc-ops
opened on Aug 25, 2026

Before submitting

  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.

Area

Not sure

Steps to reproduce

  1. opened the App started working on my project, spun up several agents, got a message that T3 Code crashed (though the app was still open, and al timers still running, but chat was not responsive) Took about 10 mins to crash each time
  2. Seems to be tied to number of subagents, 1-2 seems fine, but 4-5 broke every time

Expected behavior

T3 Code should not crash

Actual behavior

T3 Code crashes
Been using T3 Code for about 2 weeks, these are the first crashes I experienced, and they were right after upgrading to 26.6.2

Impact

Major degradation or frequent failure

Version or commit

No response

Environment

macOs 26.6.2 Latest stable T3 Code

Logs or stack traces



Screenshots, recordings, or supporting files


No response


Workaround


Have not found one, switched back to Claude Code in the terminal to try and remedy.
Activity
  1. roc-ops
    added 
    bugSomething is broken or behaving incorrectly.
     
    needs-triageIssue needs maintainer review and initial categorization.
     on Aug 25, 2026
  2. christhomas commented on Oct 20, 2026 
    @christhomas
    christhomas
    on Oct 20, 2026
    I've also started to get lots of crashes periodically on the desktop and my iphone app is always quitting half way through writing a sentence soemtimes. It's started to happen in the last week. The desktop app window doesn't crash, it's something in the background that t3code uses as, I guess the worker threads. Those crash and I wake up sometimes and find 10 little windows on my desktop saying it crashed and I can ignore/reopen/report
  3. juliusmarminge
    added 
    needs more infoInitial triage showed no bug. Awaiting more info
     and removed 
    needs more infoInitial triage showed no bug. Awaiting more info
     on Oct 22, 2026
  4. juliusmarminge commented on Oct 27, 2026 
    @juliusmarminge
    juliusmarminge
    on Oct 27, 2026 – with GitCafe Production
    Member
    I tried to reproduce this on current main (4914cdd) by running the T3 server with several agents spawning subagents at once:
    

      

    • One Claude Sonnet thread that launches 5 parallel subagents, each running a ~4 minute shell loop and editing files.
      • 

    • The same thread at the same time as a second Claude thread with 5 more subagents (10 concurrent), running for about 7 minutes.
      • 

    • A Codex thread and a Claude thread with 5 subagents each (10 concurrent), each subagent running a ~12 minute loop. Both parents went idle while their subagents kept working in the background.
      • 

    

    The server stayed up for all three runs, with no restarts and no errors in its log. Memory held between 410 and 520 MB, and every subagent finished and reported back.
    

    From your description (the window stays open, timers keep running, chat stops responding) and @christhomas's (several "quit unexpectedly" windows with Ignore / Reopen / Report), a background process inside T3 Code is crashing natively, not the window. To find out which process and why, could you attach:
    

      

    1. The T3 Code version: T3 Code → About T3 Code.
      2. 

    2. One of the macOS crash reports. Open Console.app → Crash Reports, or ~/Library/Logs/DiagnosticReports/, and find the entries from the crash time (names starting with T3 Code or Electron). The Process, Exception Type, Termination Reason lines and the crashed thread's backtrace are enough. Clicking Report… in the crash dialog shows the same text.
      3. 

    3. ~/.t3/userdata/logs/server.trace.ndjson (and .1 if present) from a session that crashed, or just the lines from a few minutes before the crash.
      4. 

    4. Which providers the subagents were running on (Claude, Codex, …), and roughly how much memory the Mac has.
      5. 

    

  5. juliusmarminge
    added 
    needs more infoInitial triage showed no bug. Awaiting more info
     on Oct 27, 2026
  6. github-actions commented on Nov 4, 2026 
    @github-actions
    github-actionsBot
    on Nov 4, 2026 – with GitHub Actions
    Contributor
    Closing: no reply in 7 days after we asked for more information. Comment with the missing details and we will reopen.
  7. github-actions
    closed this as not plannedon Nov 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Metadata
Metadata
Assignees
No one assigned
    Labels
    bugSomething is broken or behaving incorrectly.needs more infoInitial triage showed no bug. Awaiting more infoneeds-triageIssue needs maintainer review and initial categorization.
    Type
    No type
    Projects
    No projects
      Milestone
      No milestone
      Relationships
      None yet
      Development
      No branches or pull requests
      Issue actions