[Bug] Remote Control authentication redirect loop on Android after kimi.com → kimi.ai migration

What version of Kimi Code is running?

0.43.1

Which open platform/subscription were you using?

managed:kimi-code

Which model were you using?

DeepSeek V4.1 Flash

What platform is your computer?

Microsoft Windows NT 10.0.19045.0 True

What issue are you seeing?

Kimi Code Remote Control works correctly on the Windows host, but the Remote Control authorization flow fails on Android Chrome.

I start Kimi using:

kimi web --remote-control

The generated code-rc.kimi.com Remote Control page works correctly when opened on my desktop and shows my local Kimi Web sessions.

On Android Chrome, however, the Remote Control URL displays "Sign in to Kimi Code". After signing in, the authentication flow redirects through kimi.com and reaches the migration page saying "Kimi has been rebranded as Kimi.ai". It then redirects to kimi.ai instead of returning to code-rc.kimi.com.

When I open the Remote Control URL again, it still says:

"This Remote Control session requires authorization."

The issue also reproduces in Chrome Incognito.

What steps can reproduce the bug?

1. On Windows, run: kimi web --remote-control
2. Confirm that Remote Control connects successfully.
3. Open the generated code-rc.kimi.com Remote Control URL on Android Chrome.
4. The page displays "Sign in to Kimi Code".
5. Press "Sign in".
6. Authenticate with the same Kimi account used by Kimi Code.
7. The authentication flow redirects through kimi.com/code/auth.
8. After authentication, the Kimi migration page appears saying "Kimi has been rebranded as Kimi.ai".
9. The flow redirects to kimi.ai instead of returning to code-rc.kimi.com.
10. Open the original Remote Control URL again.
11. It still displays "This Remote Control session requires authorization."

The same behavior occurs in Chrome Incognito.

What is the expected behavior?

After authenticating with my Kimi account on Android, the authorization flow should redirect back to code-rc.kimi.com and authorize the Remote Control session.

I should then be able to see and continue the local Kimi Web sessions running on my Windows machine from Android Chrome.

Additional information

Host: Windows
Remote client: Android / Chrome
Kimi Code: 0.43.1
Authentication: managed:kimi-code

Running kimi login on the Windows host returns:

Logged in to managed:kimi-code.

Remote Control itself appears healthy. When the same code-rc.kimi.com Remote Control URL is opened from a desktop browser, it successfully displays the local Kimi Web sessions.

This therefore appears specific to the mobile authentication/authorization callback rather than the Remote Control connection itself.

Contribution

• I am willing to submit a PR for this bug fix myself (please wait for maintainer approval in this issue first)

Start at the implementation behind kimi web --remote-control and trace the authorization callback used by the generated code-rc.kimi.com URL, comparing it with the working desktop flow; the issue names no source files or tests. Verify that the Android Chrome sign-in path survives the kimi.com to kimi.ai migration and returns to the original URL with the Remote Control session authorized.