Effort level shows/resets to "high" when a CLI session is driven from the mobile app

What happens

~/.claude/settings.json contains:

{ "effortLevel": "xhigh" }

When the same CLI session is then driven remotely from the mobile app, the app
shows the effort level as high, not xhigh. It appears to change without
the user touching it.

Running /effort xhigh (or max) inside the session reports
Set effort level to <value> (this session only), but the app afterwards still
displays high.

What I expected

The effort level from settings.json — or whatever the session was last set to —
carries over when the session is attached from the mobile app, and the app
displays that value.

Why it is hard to diagnose from the user side

It is not clear whether this is cosmetic or real:

• the mobile app displays high
• there is no way to read back the effective effort level from inside the

session, so the user cannot tell whether the model is actually running at
high or at the configured xhigh and only the label is wrong

That ambiguity is the main pain point. Even a read-only way to confirm the
effective value (e.g. /effort with no argument printing the current level)
would make this diagnosable.

Environment

• Claude Code CLI on Linux (WSL2), session attached from the mobile app
• effortLevel set in ~/.claude/settings.json, not in project settings

Question

Is effortLevel in settings.json expected to apply to remotely-attached
sessions? If it is meant to be per-client, saying so in the docs would also
resolve this.