Skip to content

[Bug]: Unable to remove a project with zero threads #4632

Description

@azs06

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. I have a project from like 3 months ago, first time I tried T3 Code.
  2. Recently I wanted to check the latest version, I removed the old T3 Code and downloaded the latest version from website.
  3. I wanted to remove the project, as I am not working on this anymore and it had one thread which I archived.
  4. Every time I try to remove it, I am getting an error
Orchestration command invariant failed (project.delete): Project '1868c2c0-1e38-4dc2-bc47-0c0abd66f380' is not empty and cannot be deleted without force=true.

Even though the project does not have any threads, it keeps saying this.

Image

Expected behavior

The project should be removed without any error.

Actual behavior

Getting error while trying to delete a project with no threads.

Impact

Minor bug or occasional failure

Version or commit

No response

Environment

macOS 26.5.2

Logs or stack traces

Screenshots, recordings, or supporting files

No response

Workaround

No response

Activity

  1. added
    bugSomething is broken or behaving incorrectly.
    needs-triageIssue needs maintainer review and initial categorization.
    on Jul 27, 2026
  2. t3dotgg commented on Aug 27, 2026

    @t3dotgg
    Member

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

    The reporter archived the project's only thread, then removal failed with the exact force=true invariant. Issue 2866 already tracks that same archived-only project, empty sidebar count, and unforced delete mismatch. Its comments include the same stable-version failure and hidden archived row. This is not a distinct zero-thread condition.

    I'm closing this as a duplicate as part of an automated pass on all open issues. I linked this report from issue #2866 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.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