Login successful but MiMo Code returns 401 Invalid API Key in GitHub Codespaces

[contraburgues7-debug]

Description

Hello MiMo Code team.

I am experiencing the same authentication issue described in issue #306.

I am using MiMo Code inside GitHub Codespaces. The login process finishes with “Login successful”, and at one point the provider appears to have one credential. However, when I send any prompt, MiMo Code returns:

401 Invalid API Key

I have already:

• Logged out and logged in again.
• Generated a new authorization code.
• Confirmed the login success message.
• Checked the provider credentials.
• Tried the authentication process more than once.
• Avoided sharing or exposing the API Key.

The agent cannot execute any command or work on the repository because authentication fails immediately.

Please confirm:

1. Whether MiMo Auto/free authentication is currently working.
2. Whether this is the same credential persistence bug reported in issue MiMo Auto (free) login succeeds but auth credentials not persisted — 401 Invalid API Key on use #306.
3. Which provider should be selected for an international account.
4. Whether Token Plan China must be avoided outside China.
5. Whether there is a fix, patched version, or temporary workaround.
6. Which log file or diagnostic command you need from me.

Environment:

• GitHub Codespaces
• Linux
• MiMo Code CLI
• Repository hosted on GitHub

Please do not ask me to post my API Key publicly.

Plugins

No response

MiMoCode version

No response

Steps to reproduce

No response

Screenshot and/or share link

No response

Operating System

No response

Terminal

No response