Submit button constantly spins, even after entire agent response has completed requiring refresh #593

Activity

1. bstar commented on Mar 10, 2026

   

   bstar

   on Mar 10, 2026

   Last edited by bstar

   Author

   More actions

   Using npx t3 not seeing the issue, seems to only happen via the AppImage (only binary I've tried)
2. MikePfunk28 commented on Mar 18, 2026

   

   MikePfunk28

   on Mar 18, 2026

   Last edited by MikePfunk28

   More actions

   I have the same issue using npx t3.

   1. use npx t3 and start t3 in the browser.
   2. assign it a task, and then when it is in the middle of the task try to type another prompt.
   3. it usually works the first few times, and then I have to refresh in order to send.

   Results:
   It does not send the text, and shows it is still working on a task, but when I refresh it is done. Something is seemingly getting stuck, and I have to refresh in order to send another prompt through, or see the result. The problem is, I am not always able to tell until I try to send another prompt and it will not send.

   Notes:
   This does not happen every single time, however, I also have a local model running, so my memory could be very high. I am using chrome with probably 40 tabs open, on windows 11 latest update for both chrome and windows.

   Windows 11 Version 25H2 Chrome Version 146.0.7680.80, node v22.17.1, bun 1.3.0, Codex Subscription

   The images are of Before, when it is spinning and I cannot send the text, and After I refresh.

   Logs:

   codex subscription status { type: 'chatgpt', planType: 'plus', sparkEnabled: false }
   [15:12:43.609] INFO (#434): codex app-server opening thread {
     threadId: '4c634d96-3e74-448d-8533-2881f1a95108',
     requestedRuntimeMode: 'full-access',
     requestedModel: 'gpt-5.4',
     requestedCwd: 'C:\\Users\\mikep\\ImagineEngine-MVP',
     resumeThreadId: null
   }
   [15:12:43.885] INFO (#436): codex app-server thread open resolved {
     threadId: '4c634d96-3e74-448d-8533-2881f1a95108',
     threadOpenMethod: 'thread/start',
     requestedResumeThreadId: null,
     resolvedThreadId: '019d025d-52e5-7ac3-9868-b3cb3c2100f0',
     requestedRuntimeMode: 'full-access'
   }
   [16:05:34.043] INFO (#159637): Error: Git command failed in GitCore.fetchUpstreamRefForStatus: git fetch --quiet --no-tags origin +refs/heads/fix/remove-hardcoded-model-selection:refs/remotes/origin/fix/remove-hardcoded-model-selection (C:\Users\mikep\ImagineEngine-MVP) - git fetch --quiet --no-tags origin +refs/heads/fix/remove-hardcoded-model-selection:refs/remotes/origin/fix/remove-hardcoded-model-selection timed out.
       at onNone (file:///C:/Users/mikep/AppData/Local/npm-cache/_npx/5ca66e5ae19a7ff4/node_modules/t3/dist/index.mjs:3356:30)
       at file:///C:/Users/mikep/AppData/Local/npm-cache/_npx/5ca66e5ae19a7ff4/node_modules/effect/dist/Option.js:206:22
       at Module.<anonymous> (file:///C:/Users/mikep/AppData/Local/npm-cache/_npx/5ca66e5ae19a7ff4/node_modules/effect/dist/Function.js:94:18)
       at Effect.fn (file:///C:/Users/mikep/AppData/Local/npm-cache/_npx/5ca66e5ae19a7ff4/node_modules/t3/dist/index.mjs:17373:9)
       at Effect.fn (definition) (file:///C:/Users/mikep/AppData/Local/npm-cache/_npx/5ca66e5ae19a7ff4/node_modules/t3/dist/index.mjs:16893:29)
   [16:05:59.781] INFO (#177018): Error: Git command failed in GitCore.fetchUpstreamRefForStatus: git fetch --quiet --no-tags origin +refs/heads/fix/remove-hardcoded-model-selection:refs/remotes/origin/fix/remove-hardcoded-model-selection (C:\Users\mikep\ImagineEngine-MVP) - git fetch --quiet --no-tags origin +refs/heads/fix/remove-hardcoded-model-selection:refs/remotes/origin/fix/remove-hardcoded-model-selection timed out.
       at onNone (file:///C:/Users/mikep/AppData/Local/npm-cache/_npx/5ca66e5ae19a7ff4/node_modules/t3/dist/index.mjs:3356:30)
       at file:///C:/Users/mikep/AppData/Local/npm-cache/_npx/5ca66e5ae19a7ff4/node_modules/effect/dist/Option.js:206:22
       at Module.<anonymous> (file:///C:/Users/mikep/AppData/Local/npm-cache/_npx/5ca66e5ae19a7ff4/node_modules/effect/dist/Function.js:94:18)
       at Effect.fn (file:///C:/Users/mikep/AppData/Local/npm-cache/_npx/5ca66e5ae19a7ff4/node_modules/t3/dist/index.mjs:17373:9)
       at Effect.fn (definition) (file:///C:/Users/mikep/AppData/Local/npm-cache/_npx/5ca66e5ae19a7ff4/node_modules/t3/dist/index.mjs:16893:29)
   

   
3. shivamhwp commented on Mar 24, 2026

   

   shivamhwp

   on Mar 24, 2026

   Collaborator

   More actions

   are you on the latest version of t3 code ?
   is it still happening @bstar ?
4. pilotmoon commented on Mar 27, 2026

   

   pilotmoon

   on Mar 27, 2026

   Last edited by pilotmoon

   More actions

   Finding a similar same issue.
   MacOS build -- T3 Code (Alpha) 0.0.14 (28afb14)
   After the current task is finished, the submit button continues to show the rotating arrow in disabled state. If I click on to a different thread and then come back, the button state updates to enabled with the static arrow and can be pressed.
5. juliusmarminge commented on Jun 9, 2026

   

   juliusmarminge

   on Jun 9, 2026

   Member

   More actions

   Resolved on main by #1700. The composer now uses the actual active-turn completion state, preventing the stale running spinner from blocking new sends after a completed turn.
6. juliusmarminge

   closed this as completedon Jun 9, 2026