1 bug and 1 enhancement request related to `session`

What version of Kimi Code is running?

0.11.0

Which open platform/subscription were you using?

Kimi Code (OAuth)

Which model were you using?

Kimi-k2.6

What platform is your computer?

Linux 7.0.11-orbstack-00354-gde2ab3f9e944 aarch64 unknown

What issue are you seeing?

1 bug and 1 enhancement request related to session.

1. Bug: Please see picture below. I type kimi --session to choose a session. And Model shows not set, run /login or /provider. However, I have already logged in through Kimi Code (OAuth). And actually I can still use Kimi Code, so it is just a interface bug.

2. Enhancement: I can type kimi --session to choose a session. I can also type kimi to enter kimi interface then type /sessions to choose a session. Could it be shown as the same word? session or sessions? Or accept kimi --sessions to choose a session.

What steps can reproduce the bug?

1. Authenticate Kimi Code via Kimi Code (OAuth).

2. Type kimi --session to enter Session selection interface of Kimi Code.

What is the expected behavior?

No response

Additional information

No response

Reproduce the report by authenticating with Kimi Code (OAuth) and running kimi --session; compare its session-selection interface with entering kimi and using /sessions. The issue does not name files or tests, so first locate the CLI entry point and the implementations of those two session-selection paths. Done means the OAuth session display is accurate and the session command naming is consistent or accepts the requested alternative.