Signing in with a GitHub account reaches whichever Railway account that GitHub identity is already linked to. The empty workspace you land in belongs to a separate Railway account, not the one that owns your projects. To reach your workspace, sign in with the identity that created it.

We can't merge or link accounts, or move projects between them, so nothing will be changed on either account.

Thank you. I understand that different GitHub identities can lead to different Railway accounts. I am not asking to merge accounts or move projects.

The issue is an apparent inconsistency:

1. An existing authenticated Railway CLI session can still access my original workspace and list its projects.
2. A read-only Railway API query using that session reports a linked GitHub username.
3. Signing into Railway with that exact GitHub username opens a different, empty workspace.
4. Signing in with my original GitHub account through Apple instead produces an error saying the Railway account is already linked to the username in step 2.
5. The same behavior occurs in an incognito window. Email login codes to my Apple private relay address also do not arrive.

Could a human support engineer review this discrepancy? Could the displayed GitHub username be stale or differ from the underlying GitHub identity used for authentication?

Please advise how I can securely provide the relevant account identifiers and redacted query results through an approved private channel. I will not post credentials or tokens publicly.

Please keep this issue open. Browser access to my original workspace is still unresolved. Do not unlink accounts or modify projects without my confirmation.

The GitHub account you sign in with is what decides which Railway account you reach. The username a session reports comes from the linked GitHub identity, and GitHub logins can be renamed, so that name can now belong to a different GitHub account than the one that was originally linked. That would explain landing in an empty account when you sign in as that username.

We can't change, link, or unlink the login methods on an account, and no identifiers or proof of ownership would change that. This boundary protects the account, so there's nothing you need to send us privately. Nothing on either account has been or will be changed.

There are two ways back in. The first is to recover the GitHub identity that was originally linked, working with GitHub (for example, checking whether that account's username was changed and signing in to it directly). The second is to sign in with another method already linked to the account. For email codes, check the inbox your Apple private relay forwards to, and make sure the relay address is still active in your Apple ID settings.

To clarify, I use Sign in with Apple on GitHub, then GitHub OAuth to sign into Railway. I do not use Apple directly with Railway.

The private relay address was issued for GitHub. Railway login emails may therefore be rejected by Apple's sender restrictions. Could you check whether those emails bounced and provide the delivery error?

GitHub authentication succeeds, but Railway then reports a conflicting linked GitHub account. My existing Railway CLI session still accesses the original projects.

I am not requesting an account merge or relinking. Please help diagnose the email delivery failure and OAuth identity mismatch, and identify a supported recovery route.

Using Sign in with Apple on GitHub's side doesn't change how Railway matches you. We only see the GitHub identity that comes back from GitHub OAuth, and that identity reaches whichever Railway account it is already linked to. The "already linked to a different GitHub account" error means the GitHub account you authenticate as is not the identity linked to your original Railway account. As Brody mentioned, a renamed GitHub login can leave the username a session reports now belonging to a different GitHub account.

On the email codes, we can't retrieve or share delivery records for that address from this thread, and a delivery result wouldn't change which account a sign-in reaches. Email sign-in sends a code only to the exact address registered on the Railway account you're trying to reach. Whether Apple's relay accepts mail from outside senders is a setting on Apple's side, so that's worth confirming in your Apple ID's Hide My Email settings.

The supported routes back into the original account are the same two: recover the GitHub identity that was originally linked by working with GitHub, or sign in with another method already linked to that account. We won't change, unlink, or modify anything on either account.

原帳戶僅剩 CLI 可存取、Email 又無法收信時，有哪些受支援的復原方式。

Apologies, we only correspond in English. Please open a new thread in English.