Skip to content

[Bug]: Auto-generated session titles are always Chinese, even for English input (CLI - interactive TUI) #602

Open

Description

@natechadwick-intsof

Severity: Medium (cosmetic; affects every session; no data loss)
Component: MiniMax Code CLI (TUI) — session title generation
Found: 2026-11-14
Region: Global (en) — not region-specific, see "Not a region issue" below


Product or interface

CLI - interactive TUI

Version

$ mcode --version
0.7.7

Runtime: pi-agent, Node v26.13.1. Release directory:
~/.minimax-code/releases/0.7.7.

Platform

Linux

OS version and architecture

Omarchy (Linux 7.2.15-1-omarchy, x86_64)

Issue area

UI / UX

Desktop log upload ID

N/A — CLI report.


Summary

The auto-generated session title is written in Chinese even when the user's message is
entirely in English, or contains no natural language at all. The title generator is a
separate model call whose own prompt instructs it to mirror the input language, and it
does not do so — it defaults to Chinese.

This is visible in the TUI status bar, which renders the session title:

~/workspaces/sap.house/sap.house-app │ ◇ 分析 003-family-chores 规格一致性 │ ⎇ main │ Full access │ ✦ M3 · Thinking On │ Context 63% left
                                     └── session title (Chinese) ──────────┘

Every other status-bar segment is English. Only the title is affected.


Steps to reproduce

Two independent cases, both with ASCII-only input.

Case A — no natural language at all

  1. Start a session in a repository.
  2. Send the single command /speckit-analyze (16 characters, ASCII only).
  3. Observe the generated title in the status bar.

Case B — plain English question

  1. Start a session.
  2. Send: Wich model is more costeffective for coding with my currrent plan? M3 or M3.1-Flash?
  3. Observe the generated title.

CLI specifics for reproduction:

  • Permission mode: bypassPermissions (default config.yaml)
  • Provider: MiniMax OAuth / managed login (minimaxModelSource: token_plan), model
    minimax/MiniMax-M3, variant thinking
  • Command: mcode (interactive TUI), then the first user message above
  • Account region: en (Global), buildEnv: prod; LANG=en_US.UTF-8

Expected and actual behavior

Expected: the generated title uses the same language as the user's message, per the
generator's own instruction. English input → English title; Chinese input → Chinese title.

Actual: the title is Chinese in every observed case, including both English inputs
above. The generator violates rule 2 of its own system prompt.

Case Input Actual title
A /speckit-analyze 分析 003-family-chores 规格一致性
B Wich model is more costeffective for coding with my currrent plan? M3 or M3.1-Flash? 比较 M3 与 M3.1-Flash 编程性价比

Root cause

1. The title call receives no locale

assets/agents/desktop-task/session-title/system.md is loaded and invoked as its own
model call. The call site passes only three arguments:

this.options.model.summarize({
  session: r,
  systemPrompt: i,      // desktop-task/session-title/system.md
  userPrompt: a7s(n),
  maxTokens: 1000,
  ...
})

There is no region and no locale argument. The runtime's en/cn value never reaches
this prompt, so the generator cannot know the user's preferred language except by guessing
from the message.

2. The prompt's own rule is not followed

desktop-task/session-title/system.md, rule 2:

"Use the same natural language as the user's message and never translate it because these
instructions are in English. English input must produce English, Japanese input must produce
Japanese, Spanish input must produce Spanish, and Chinese input must produce Chinese. For
mixed-language input, use the main language."

The generator violates this rule in both reproduced cases.

3. The prompt's examples bias the model toward Chinese

Within the same file, the examples are Chinese-first — four Chinese examples appear before
the English, Japanese, and Spanish ones:

- “给设置页加上深色模式” → “添加设置页深色模式”
- “登录时出现 500,帮我修一下” → “修复登录 500 错误”
- “比较两种 session title prompt” → “比较 session title prompt”
- “foo_bar 是在哪里创建的?” → “定位 foo_bar 创建位置”
- “what's 2+2” → “Calculate 2+2”
- “Fix the redirect loop after password reset” → “Fix password reset redirect loop”

Rule 5 also leads with the Chinese length target before the English one:

"Chinese titles are usually 6-20 Chinese characters, English titles are usually 2-6 words…"

With no locale input and Chinese-first examples, the model anchors on Chinese.

4. The sibling task does it correctly — the asymmetry

The adjacent archive-title task in the same directory ships per-language prompt variants
and receives an explicit locale:

assets/agents/desktop-task/archive-title/system-en.md   → English prompt
assets/agents/desktop-task/archive-title/system-zh.md   → Chinese prompt

and selects between them at runtime:

locale.split("-")[0].toLowerCase() === "zh" ? <zh prompt> : <en prompt>

The session-title task has neither the locale argument nor the language-specific variants —
only the single system.md that has to infer the language.


Redacted error summary

Not an error return — a behavior mismatch. Evidence from the local session store
(~/.minimax/v2/sqlite/runtime-state.sqlite, table local_runtime_sessions) before the
manual rename:

session  mvs_2f5a612d25e0444ca2f10c21bd352a8f
first user message : /speckit-analyze
CJK chars in message : 0
title              : 分析 003-family-chores 规格一致性
extra_data_json    : {"titleSource":"auto","titleReviewState":"completed",...}

session  mvs_4d46fa6415674305a5a0b692ed642216
first user message : Wich model is more costeffective for coding with my currrent plan? M3 or M3.1-Flash?
CJK chars in message : 0
title              : 比较 M3 与 M3.1-Flash 编程性价比
extra_data_json    : {"titleSource":"auto",...}

Both rows carried "titleSource":"auto", confirming the titles were runtime-generated rather
than user-set.

Not a region, locale, or account issue:

~/.minimax/preferences/mcode-region.json                      -> {"regions":{"prod":"en"}}
~/.minimax/auth/prod/en/mcode-public/auth-state.json          -> region: "en", buildEnv: "prod", status: "authenticated"
~/.minimax/config.yaml                                       -> baseURL: https://agent.minimax.io/mavis/api/v1/llm/v1
LANG                                                          -> en_US.UTF-8

config.yaml has no locale/language/title-language key; the complete key set is:

permissionMode, defaultModel, defaultModelVariant, defaultLightModel, provider, asr,
sseErrorPush, beta, nexus, thinking, memory, review, worktreeRefreshBeforeCreate, agents,
dataContribution, askUser, promptSuggestion, quotaAutoResume, nextStepBox, bunny,
pluginRecommendation, subagent

Screenshots

None attached. The status-bar line above is transcribed verbatim from the terminal.


Suggested fix

Apply the locale routing that archive-title already has:

  1. Pass the session's locale into the session-title task, as archive-title does.
  2. Ship desktop-task/session-title/system-en.md and system-zh.md variants and select
    between them on the locale, instead of relying on one prompt to infer the language.
  3. Keep the language-mirroring rule for mixed-language input, but make the default
    language explicit in the prompt rather than implied by example ordering.
  4. Reorder the examples in any single-language prompt so the target language comes first
    (or split the prompt entirely, per point 2).

A regression test would be: given an English user message, submit_session_title returns an
ASCII-only title; given a Chinese message, a CJK title.


Workaround

Rename the session manually once the turn is idle:

/rename

or Sessions → select session → rename in the sidebar. A manual title is stored with
titleSource: "manual", which prevents the auto-title and title-review passes from
replacing it. (Note: /rename currently requires an idle turn — see issue #427,
"Allow /rename while a turn is running".)


Before submitting

  • I have searched existing issues.
  • I have included my version and removed sensitive information (local home paths are
    written as ~/…; no credentials, tokens, account identifiers, or project content are
    included).

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions