Session titles require a Kimi account even for local/self-hosted setups — no local fallback, and it fails silently #4173

What version of Kimi Code is running?

2.1.1

Which open platform/subscription were you using?

OpenAI-compatible ("open platform") provider

Which model were you using?

No response

What platform is your computer?

No response

What issue are you seeing?

Session titles are not being generated in this local / no-subscription setup. After the first prompt, the session stays untitled, and there's no error or message explaining why (it's silent — the failure is only at debug level). It appears title generation only works when a Kimi account is signed in (it calls the hosted api.kimi.com/coding/v1/tools endpoint); a self-hosted model provider is never used and there's no config option to route titles to the local model.

What steps can reproduce the bug?

Steps to reproduce

Prereqs

• Any OpenAI-compatible local endpoint (vLLM, llama.cpp server, LM Studio, Ollama OpenAI endpoint, etc.).
• No Kimi/Moonshot account signed in.

1. Configure Kimi Code with only a local openai provider (no Kimi sign-in). Minimal config.toml:

default_model = "local/test"

[models."local/test"]
provider = "local"
model = "<your-local-model-id>"
max_context_size = 32768

[providers.local]
type = "openai"
base_url = "http://localhost:8000/v1"
api_key = "sk-dummy"

2. Start a session — either kimi in a terminal or the kimi web UI — using that config.

3. Send a first user prompt (e.g. "What is the capital of France?") and let the assistant reply.

4. Check the session title — in the web UI sidebar, or the session title after the first turn.

Expected

A short auto-generated title for the session (as it would be with a signed-in Kimi account).

Actual

No title is generated — the session stays untitled/uses the default placeholder. No error, warning, or hint is shown at any visible log level, so there's nothing to indicate why titles are missing.

What is the expected behavior?

Expected behavior

In a self-hosted, no-subscription setup (a supported configuration — any openai / open-platform provider), at least one of the following should hold:

1. Preferred: the session title is generated from the session's active/default model (the local one), so local users get auto-titles just like signed-in users — no Kimi account required.
2. Minimum: if titles genuinely require a Kimi account, the CLI should not fail silently. It should show a clear, one-time message (info/warn log or a UI hint) stating that session titles require a Kimi account, so the user knows the missing title is intentional rather than a silent failure.

The unambiguous defect either way: a local-only user gets no title and no explanation — nothing is logged at any visible level, so the situation is indistinguishable from a bug.

Additional information

No response

Contribution

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