Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] /ultrareview fails with "failed to launch the remote session" under WSL2, same setup works from Windows-native CLI

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

/ultrareview <PR#> consistently fails in Claude Code running inside WSL2 with the generic error:

Ultrareview failed to launch the remote session. Check that this is a GitHub repo and try again.

The identical command, on the identical account, with an identical repo and PR, succeeds immediately when invoked from the Windows-native Claude Code CLI. The WSL-vs-Windows CLI is the only changed variable.

Error Message

/ultrareview <PR#> consistently fails in Claude Code running inside WSL2 with the generic error:

Root Cause

/ultrareview <PR#> consistently fails in Claude Code running inside WSL2 with the generic error:

Ultrareview failed to launch the remote session. Check that this is a GitHub repo and try again.

The identical command, on the identical account, with an identical repo and PR, succeeds immediately when invoked from the Windows-native Claude Code CLI. The WSL-vs-Windows CLI is the only changed variable.

Fix Action

Workaround

Run /ultrareview from Windows-native Claude Code CLI, not from WSL. Details and a step-by-step setup template available on request.

RAW_BUFFERClick to expand / collapse

Summary

/ultrareview <PR#> consistently fails in Claude Code running inside WSL2 with the generic error:

Ultrareview failed to launch the remote session. Check that this is a GitHub repo and try again.

The identical command, on the identical account, with an identical repo and PR, succeeds immediately when invoked from the Windows-native Claude Code CLI. The WSL-vs-Windows CLI is the only changed variable.

Environment (failing)

  • OS: Ubuntu 24.04.4 LTS inside WSL2 (Linux 5.15.167.4-microsoft-standard-WSL2 on Windows host)
  • Claude Code: 2.1.114
  • gh: 2.45.0
  • git: 2.43.0
  • Plan: Max (claude.ai authed, not API-key)
  • Auth path: /web-setup (gh token sync), completed successfully (Connected as <user>)

Environment (working — same account, same repo)

  • OS: Windows 11, PowerShell
  • Claude Code: same 2.1.114

Reproduction (minimal)

  1. In WSL Claude Code, with a public GitHub repo + an open non-draft PR from a feature branch to main:
  2. Run /ultrareview <PR#>
  3. Confirmation dialog appears showing "Free ultrareview 1 of 3" and correct PR metadata
  4. Press Enter to confirm
  5. Immediately errors with Ultrareview failed to launch the remote session. Check that this is a GitHub repo and try again.

Redo identical steps from Windows-native Claude Code CLI on the same account: launches successfully on first attempt.

What I've ruled out

  • Repo visibility / private vs public (tested both)
  • PR draft state (tested both)
  • Bundle vs PR mode (PR mode hits this; bundle mode hits the separate unfixed #49458)
  • /web-setup status (re-ran, reports Connected as <user>)
  • gh token scopes (includes workflow)
  • API overload (waited for Anthropic status to be fully green, retried — same failure)
  • Default branch / merge-base / branch topology (verified on GitHub — default branch main, PR MERGEABLE, merge-base resolves cleanly locally)
  • Cloud environment provisioning (visible in claude.ai/code web UI; repo and branches render correctly in the branch picker)

The message "Check that this is a GitHub repo" suggests the launch-handoff is failing at a repo-identification step that succeeds in the Windows CLI path with the identical remote URL.

Workaround

Run /ultrareview from Windows-native Claude Code CLI, not from WSL. Details and a step-by-step setup template available on request.

extent analysis

TL;DR

The most likely fix is to investigate and resolve the discrepancy in how Claude Code interacts with GitHub repositories when run from WSL2 versus the Windows-native CLI.

Guidance

  • Verify that the gh token and its scopes are correctly configured and identical in both WSL2 and Windows environments to ensure consistent authentication.
  • Check the repository URL and its configuration in Claude Code to ensure it is correctly identified as a GitHub repository in both environments.
  • Compare the output of git remote -v and gh repo view commands in both WSL2 and Windows environments to identify any differences in repository configuration or authentication.
  • Consider setting up a debug log or verbose mode in Claude Code to gather more information about the launch-handoff process and where it fails in the WSL2 environment.

Example

No specific code snippet is provided as the issue seems to be related to environment and configuration rather than code.

Notes

The issue might be related to how WSL2 handles environment variables, authentication, or network requests differently than the Windows-native CLI. Further investigation into these areas may be necessary to identify the root cause.

Recommendation

Apply workaround: Run /ultrareview from Windows-native Claude Code CLI until the root cause of the WSL2 issue is identified and resolved, as it provides a reliable alternative for launching ultrareview sessions.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#callback error#memory management#API rate limit#retriever error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [BUG] /ultrareview fails with "failed to launch the remote session" under WSL2, same setup works from Windows-native CLI