Still report error : Authorization error, you may need to run /login

### Describe the bug

✗ Authorization error, you may need to run /login (Request ID:
D563:31F14:D195DE:F343F3:69DDC5C8)

! Failed to connect to MCP server 'github-mcp-server'. Execute '/mcp show
github-mcp-server' to inspect or check the logs.

● GitHub MCP Server: Connected

● Signed in successfully as BH1SCW!

! Failed to connect to MCP server 'github-mcp-server'. Execute '/mcp show
github-mcp-server' to inspect or check the logs.

● MCP Servers reloaded: 0 servers connected

✗ Authorization error, you may need to run /login (Request ID:
D563:31F14:D2D435:F4B472:69DDC627)

### Affected version

1.0.22- 1.0.25

### Steps to reproduce the behavior

why I have login but still can't use it

### Expected behavior

_No response_

### Additional context

_No response_

Start by reproducing the failure on versions 1.0.22–1.0.25, then run `/mcp show github-mcp-server` and inspect the logs as the report suggests. Compare the successful `/login` and MCP reload messages with the authorization errors; done means identifying why the connected GitHub MCP server still rejects requests and documenting or fixing the authentication path.

Rédigé par le modèle d'indexation à partir du texte de l'issue.