fix(mimocode): scan ~/.local/share/mimocode, not /micode

[Javis603]

Summary

MiMo Code usage is never detected: the scanner looks in ~/.local/share/micode/, but MiMo Code stores its SQLite session db under ~/.local/share/mimocode/. Pointing the scanner at mimocode fixes detection. The client id stays micode — only the data directory changes.

Root cause

MiMo Code (XiaomiMiMo/MiMo-Code) resolves all of its XDG base dirs from a single app name:

// packages/shared/src/global.ts
const APP = "mimocode"
// ...
data: path.join(xdgData!, APP),   // -> ~/.local/share/mimocode

So sessions live at ~/.local/share/mimocode/mimocode.db (and config/state/cache under ~/.config/mimocode, ~/.local/state/mimocode). On Windows the same layout appears under %USERPROFILE%\.local\share\mimocode\.

The MiMo Code scanner added in #710 assumed ~/.local/share/micode/mimocode.db. Note this is internally inconsistent: the directory is micode but the filename matcher is mimocode.db. The string micode never appears anywhere in MiMo-Code's history (git log -S '"micode"' --all is empty) — it has been mimocode since the V0.1.0 open-source release on 2026-06-10. So no backward-compat fallback to micode is needed.

Evidence

The shipped tokscale 4.0.4 scans ~/.local/share/micode/ — which does not exist — so it finds nothing:

$ tokscale --json --client micode --group-by client,model --no-spinner
{"groupBy":"client,model","entries":[],"totalMessages":0,"totalCost":0.0, ...}

Built from this branch, it scans the real ~/.local/share/mimocode/ directory (no symlink, no env override) and finds the sessions. Filtered to the genuine native MiMo provider (mimo):

$ ./target/release/tokscale --json --client micode --group-by client,provider,model --no-spinner
{"client":"micode","provider":"mimo","model":"mimo-auto","input":116588,"output":5893,"messageCount":21,"cost":0.11}

Note: MiMo Code imports Claude Code sessions into its db

MiMo Code automatically imports Claude Code sessions (~/.claude/projects) into mimocode.db on first run — its claude-import service (CLI mimocode session import-claude; README: "Import from Claude Code"). The observed log shows service=claude-import scanned=113 imported=113 ... resynced=4.

So mimocode.db can hold sessions whose tokens are already attributed to the claude client, and scanning it will double-count them under micode. This PR only corrects the scan path; whether to exclude or dedup imported sessions is a separate decision, out of scope here.

Changes

• clients.rs — MiMoCode.relative: "micode" → "mimocode"
• scanner.rs — scan dir {xdg_data}/micode → {xdg_data}/mimocode (+ comment)
• sessions/micode.rs — doc-comment path
• lib.rs — the one test that seeds a fixture at .local/share/micode moves to .local/share/mimocode so it matches the scan path
• README.md / README.ja.md / README.ko.md / README.zh-cn.md — the MiMo Code data-dir paths (clients table, platform-paths table, MiMo Code section)

Unchanged: the client id micode, the mimocode.db / mimocode-<channel>.db filename matcher, the parser, and every CLI/TUI/frontend id.

Verification

• cargo fmt --all -- --check — clean
• cargo clippy --locked --workspace --all-features -- -D warnings — clean
• cargo test --workspace --all-features — 1950 passed, 0 failed (includes the updated micode path-fixture test)

Follow-up (intentionally not in this PR)

MiMo Code also honors MIMOCODE_HOME to relocate all four base dirs ($MIMOCODE_HOME/data). Honoring it could be a separate enhancement; this PR keeps the change minimal and focused on the default XDG path.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
tokscale	Ignored	Preview	Jun 27, 2026 11:59pm

[cubic-dev-ai]

1 issue found across 8 files

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>

[junhoyeo]

Thanks @Javis603 — excellent fix and an exemplary writeup. The root-cause evidence (the git log -S "micode" history check, before/after CLI output, and the honest scoped-out note about MiMo Code importing Claude Code sessions into mimocode.db) made this easy to verify. MiMo Code usage was silently undetected before this, so it is a real correctness fix.

I pushed one maintainer commit (26c5749b) addressing cubic's P2: the scanner now derives the data dir from ClientId::MiMoCode metadata instead of duplicating the path, so it stays in sync with clients.rs. fmt + clippy clean, mimocode detection test passing. 🚀