Skip to content

[Bug]: Some requests are slow keeps appearing #1986

Description

@roamingparrot

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

  1. start the app from the dock
  2. open any thread
  3. send a prompt to claude - issue has occurred on sonnet and opus but presumably is a ui issue as responses take less than 15 seconds

Expected behavior

popup should not appear when requests are not slow, there is also no obvious way to hide to popup seemingly

Actual behavior

popup stays as long as the window remains open.

Impact

Cosmetic issue

Version or commit

main @ v0.0.17

Environment

macOS

Logs or stack traces

# t3-code v0.0.17 | macOS | server-child.log
# Repeated git fetch timeouts (same error ~13+ times in one session):

GitCommandError: Git command failed in GitCore.fetchUpstreamRefForStatus:
  git --git-dir /Users/user/code/parrotui-spotify/.git fetch --quiet --no-tags
  origin +refs/heads/main:refs/remotes/origin/main - timed out.

# Thread title generation also times out (likely a downstream effect):

TextGenerationError: Text generation failed in generateThreadTitle:
  Claude CLI request timed out.

# Additionally, codex CLI spawn fails (ENOENT — binary not found):

PlatformError: NotFound: ChildProcess.spawn (codex exec --ephemeral -s read-only
  --model gpt-5.4-mini ...) - spawn codex ENOENT

Screenshots, recordings, or supporting files

Screenshot 2026-04-13 at 15.03.12.png

Workaround

No response

Activity

  1. added
    bugSomething is broken or behaving incorrectly.
    needs-triageIssue needs maintainer review and initial categorization.
    on Apr 13, 2026
  2. AashishSinghal commented on Apr 13, 2026

    @AashishSinghal

    Facing the same for Claude and Provider turn start failed for codex

  3. oconnorjohnson commented on Apr 13, 2026

    @oconnorjohnson

    Also seeing this toast, and generally experience issues with the inability to manually clear toast, would be nice to have an escape hatch here.

  4. roamingparrot commented on Apr 13, 2026

    @roamingparrot
    Author

    it's infinitely more disruptive to my workflow that it cannot be cleared, and a full refresh of the app only works very temporarily

  5. macklinhrw commented on Apr 13, 2026

    @macklinhrw

    same issue, appears basically non-stop. tried clearing .t3, force-stopping claude/codex threads in background. after doing all this and reopening t3chat... the toast appeared again right away somehow. i almost swapped to using codex because it was so annoying, but as soon as i opened codex i realized the experience was even worse.

  6. jameswasher commented on Apr 14, 2026

    @jameswasher

    Me too. Currently only solution is to quit T3 Code.
    Image

  7. cg-ghost commented on Apr 16, 2026

    @cg-ghost
    Image

    Very annoying to have this permanent snackbar.

    1. There should be an X to close it
    2. Settings to disable it appearing altogether

    Isn't it normal for every AI call to be >15s??

  8. kendalled commented on Apr 16, 2026

    @kendalled

    @cg-ghost @oconnorjohnson we are working on a close button in issue #2023 and #2040

  9. devhe4d commented on Apr 17, 2026

    @devhe4d

    I have the same issue and its not just a toast, I can feel the TPS and general work being done is slower on T3 Code compare to CLIs both for Claude Code and Codex, not sure what is causing it

    Image
  10. roamingparrot commented on Apr 18, 2026

    @roamingparrot
    Author

    I have the same issue and its not just a toast, I can feel the TPS and general work being done is slower on T3 Code compare to CLIs both for Claude Code and Codex, not sure what is causing it
    Image

    This seems to be a separate issue, from what i can gather, most people with the same issue i am describing cap out on 2 requests waiting longer than 15 seconds and don't feel as though requests take longer. I would advise that another bug report be made regarding your concern.

  11. zayenz commented on Apr 21, 2026

    @zayenz
    Image

    Since upgrading to 0.20 (on macOS 15.6, using codex), I've seen this a lot. Related issues that started at the same time are #2115 and #2270 and lots of instances of "Capture failed".

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-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