[Bug]: Please reopen tracking: #27210 and #27234 closed, Gitea PRs still disappear with gt #33656

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#

Please reopen the original issue or discussion, or identify an active place where this unresolved failure can be followed. GitHub issue #27210 was converted and locked, and discussion #27234 was then closed as a duplicate. The duplicate comment points to a GitCafe record that exists in Backlog but also has its conversation locked and no PR linked. My November 4 report and subsequent requests from other users have received no later maintainer reply in the discussion. This report asks for that tracking path to be revived.

The original runtime report used T3 desktop 0.1.6 on Windows, Gitea 28.3.0, and gt 1.0.0 with tea uninstalled. I have not reproduced it on the current desktop release. The historical case is included below to explain why reopening tracking matters.

Historical steps:

1. Open a project whose remote is a self-hosted Gitea instance.
2. Replace tea with gt, following tea's official replacement notice, and authenticate with gt.
3. Restart T3 Code and open Pull requests.

Expected behavior#

Please reopen the original issue or discussion, or identify an active tracker where users can follow progress and contribute diagnostics.

T3 can use the current official Gitea CLI, or explains that the integration requires an authenticated fj or legacy tea installation on the T3 server machine.

Actual behavior#

The project's Gitea PRs disappear from Pull requests without an actionable error, as described in my November 4 report. This is the previously reported behavior, not a fresh runtime reproduction.

Checked November 9, 2026 at 6:44 p.m. America/Chicago (November 10, 00:44 UTC):

• Published T3 0.1.8 source still restricts the CLI to fj and tea. The same restriction remains in the checked nightly, v0.1.9-nightly.20261109.4443, and main at bbdc7dca320ee4fbc7131498aaffef2fa1eb3d41. This is source inspection, not a new runtime reproduction.
• Issue #27210 was converted into discussion #27234. The discussion was closed as a duplicate of the record on GitCafe, not the GitHub issue URL. The GitCafe record exists in Backlog, with its conversation locked and no PR linked. No maintainer reply after my November 4 discussion comment was found.
• Issue #29453 tracks silent omission of unreadable hosts. Its proposed fix, PR #29481, remains open and unmerged. It does not add gt support, and its scope explicitly excludes some unsupported-host states, so it may not expose this exact failure.
• Upstream gt 1.2.0 is now available. Its Windows settings-read fix is separate from T3's missing CLI integration.

A simple executable rename is insufficient: the migration guide changes authentication commands, flags, output, and configuration. T3 documents fj or tea 0.16+ as its supported integration paths; fj has not been tested against this particular deployment during this follow-up.

Please reopen #27210 or #27234, or point us to the active tracker that should receive further diagnostics. The GitCafe backlog record means a tracking record exists; the unresolved question is where users can follow progress and contribute while both GitHub paths are closed and that record is locked.

Impact#

Minor bug or occasional failure

Version or commit#

Historical runtime: desktop 0.1.6. Published 0.1.8 and main bbdc7dca320ee4fbc7131498aaffef2fa1eb3d41 checked in source, 2026-11-10 00:44 UTC.

Environment#

Historical report: Windows 11, T3 desktop 0.1.6, self-hosted Gitea 28.3.0, gt 1.0.0, tea not installed. Current runtime not re-tested.

Logs or stack traces#

ProcessSpawnError: NotFound: ChildProcess.spawn (tea login list --output json)
  Error: spawn tea ENOENT
WARN pull request sync skipped
  reason: "Change requests cannot be browsed for this project's host yet."

Screenshots, recordings, or supporting files#

No response

Workaround#

T3 currently documents fj or legacy tea 0.16+ on the server. Reinstall tea alongside gt and authenticate with tea login add. fj was not tested against this deployment during this follow-up.