Skip to content

[Bug]: Stuck on User Input Tool GUI #4060

Closed as not planned
Closed as not planned

Description

@tomjn

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

When a provider goes away in the middle of a user input tool call, it's not possible to exit the UI and the session gets stuck:

Image
  • Closing the app and reopening it does not fix the problem
  • Alpha or Nightly does not fix the problem
  • Switching model does not fix the problem
  • switching to a different conversation then back does not fix the problem
  • cmd+R to reload did not help.

Expected behavior

When the provider goes away I should be able to dismiss the user input tool UI, or there should be an error. In claude code I can press escape to dismiss it.

Actual behavior

The conversation is trapped in a tiny sliver of the window while most of it is taken up by a series of questions that can never be submitted.

Impact

Blocks work completely

Version or commit

0.0.29-nightly.20260716.823 (bde0a4c)

Environment

MacOS 26

Logs or stack traces

I noticed this in the settings diagnostic page

shell.resolveCommandPathForPlatform	
CommandResolutionError: 
    at file:///Applications/T3%20Code%20(Nightly).app/Contents/Resources/app.asar/apps/server/dist/bin.mjs:15606:16
    at shell.resolveCommandPathForPlatform (Nightly)
    at shell.resolveCommandPathForPlatform (definition) (Nightly)
    at shell.resolveCommandPath (Nightly)
    at shell.resolveCommandPath (definition) (Nightly)
    at shell.isCommandAvailable (Nightly)
    at shell.isCommandAvailable (definition) (Nightly)
    at externalLauncher.resolveAvailableCommand (Nightly)
    at externalLauncher.resolveAvailableCommand (definition) (Nightly)
    at externalLauncher.buildAvailableEditors (Nightly)
    at externalLauncher.buildAvailableEditors (definition) (Nightly)

Also a trace ID: 2fcb048257abf89f1ffbbda081d2617c

Screenshots, recordings, or supporting files

Screenshot 2026-07-16 at 21.23.22.png

Workaround

None that I could find involve T3 Code

Activity

  1. added
    bugSomething is broken or behaving incorrectly.
    needs-triageIssue needs maintainer review and initial categorization.
    on Jul 16, 2026
  2. Fazalkadivar21 commented on Jul 17, 2026

    @Fazalkadivar21
    Contributor

    @tomjn Please add a descriptive title to this bug.

  3. changed the title [-][Bug]:[/-] [+][Bug]: Stuck on User Input Tool GUI[/+] on Jul 17, 2026
  4. tomjn commented on Jul 17, 2026

    @tomjn
    Author

    Noting that I launched claude code in the terminal and asked it to find the session. After resuming it asked me the questions again and it worked fine. I suspect the problem here is caused by the provider going away, but then can't be escaped from due to not being able to dismiss the user question tool GUI. I have no information to help explain why the provider went away, but dismissing the user input would have allowed me to recover the session in T3 Code or gather more data.

    This would have unblocked me:

    Image
  5. added and removed
    needs-triageIssue needs maintainer review and initial categorization.
    on Jul 20, 2026
  6. t3dotgg commented on Aug 27, 2026

    @t3dotgg
    Member

    Thanks for the detailed report. This looks like the same issue tracked in issue #5454.

    The original report describes a pending question that cannot be answered or dismissed after the provider disappears, and that survives app reopen and reload. Open issue #5454 covers the same dead-session question and restart recovery failure. The Claude teardown change prevents some new leaked requests but does not recover every already persisted card.

    I'm closing this as a duplicate as part of an automated pass on all open issues. I linked this report from issue #5454 so its extra details remain available. This does not mean the underlying bug is fixed.

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.🚧 In Progress

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions