Environment: Railway CLI v5.12.1 (Windows, npm global). Project: ea-wingman-sandbox / environment: sandbox / service: clawdbot-railway-template.

ISSUE 1 — Can't connect a newly-created private GitHub repo as a service source

• Created a new PRIVATE repo to deploy from: cloudhaveninnovate/cloudhaven-openclaw-wrapper-template, branch gw-secretref-fork.

• In the service's Settings → Source, I staged a source change to that repo. The deploy failed with:

  No GitHub installation found for repo: cloudhaveninnovate/cloudhaven-openclaw-wrapper-template

• The Railway GitHub App apparently didn't have access to the newly-created private repo, and the path to install/configure the GitHub App for that repo was not discoverable from the Railway UI (no obvious "configure GitHub App access" link from the error or the source settings).

• Workaround: I deployed via railway up (CLI local upload) instead, which worked fine.

• Request: a clear in-UI flow (ideally a direct link from that error) to grant the Railway GitHub App access to a newly-created private repo when connecting it as a source.

ISSUE 2 — CLI OAuth token won't refresh; frequent re-login required

• railway commands repeatedly returned:

  Warning: failed to refresh OAuth token: Token refresh failed: invalid_grant

  Unauthorized. Please run railway login again.

• This required re-running railway login several times within a single working session.

• It recurred right after upgrading the CLI from v4.42.0 to v5.12.1: immediately after the upgrade railway whoami worked, then minutes later the refresh failed again.

• Platform: Windows. CLI installed via npm (-g @railway/cli).

• Request: investigate why the refresh token isn't persisting / refreshing (possibly not migrated across the v4→v5 upgrade).

Both are reproducible on my account. Happy to provide deployment IDs or more detail.